The recommended URL in our docs is wrong. The wrong one was introduced in r1820464. Supposedly as a fix to PR 35622. The proposed patch in the PR 35622 however carries the correct URL. Not sure how that happened. It should be changed in the docs.
However: The *really* correct URL, however, is *always* the one that Let's Encrypt says it is. Next week, our documentation can be outdated by LE changing its Terms of Service. That is why mod_md gives a WARNING with the error message provided by Let's Encrypt itself: "Provided agreement URL [XXX] does not match current agreement URL [YYY]. And that is why our documentation states: "In case of Let's Encrypt, their current Terms of Service are [here]. Those terms might (and probably will) change over time. So, the certificate renewal might require you to update this agreement URL." What the admin needs to do is change, in his servers config: MDCertificateAgreement XXX to MDCertificateAgreement YYY and reload. > Not sure this can voted as a -1 for 2.4.32 ? It certainly can. The more relevant question is: should it? And if you say yes, then you'd have to provide technical arguments for it and weigh the pros and cons. You had that explained sufficiently on your last -1 vote, I think. So, what will it be, Steffen? How do you think we should treat this error in the docs? Cheers, Stefan > Am 11.03.2018 um 14:22 schrieb Steffen <i...@apachelounge.com>: > > > Have reports from users that have issues with mod_md : > > [md:warn] [pid 7232:tid 2416] (22)Invalid argument: acme problem > urn:acme:error:malformed: Provided agreement URL > [https://letsencrypt.org/documents/2017.11.15-LE-SA-v1.2.pdf] does not match > current agreement URL > [https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf] > > Should be fixed ! > Not sure this can voted as a -1 for 2.4.32 ? > > New users follow: > https://www.apachelounge.com/viewtopic.php?t=7786 > > On 1-3-2018 16:01, Steffen wrote: >> Noticed now: >> >> In the doc 2.4: >> >> https://letsencrypt.org/documents/2017.11.15-LE-SA-v1.2.pdf >> >> In the Git/Wiki we have: >> >> https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf >> >> Cannot test if both work with mod_md. (Both links are pointing to the same >> pdf). >> >> >> On 20-2-2018 14:01, Stefan Eissing wrote: >>> elukey did fix the agreements in trunk. Now merged into 2.4.x in r1824871. >>> Thanks for checking. >>> >>> >>>> Am 20.02.2018 um 13:42 schrieb Steffen <i...@apachelounge.com> >>>> : >>>> >>>> >>>> In the mod_md 2.4 (not in trunk) documentation >>>> https://httpd.apache.org/docs/2.4/mod/mod_md.html >>>> >>>> >>>> >>>> I see three times: >>>> >>>> MDCertificateAgreement >>>> https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf >>>> >>>> >>>> This errors if not an existing account. >>>> >>>> It should be now (should be nice we have it in 2.4.31) : >>>> >>>> MDCertificateAgreement >>>> https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf >>>> >>>> >>>> >>>> As long as the CA reports that the account has an agreement in mod_md, no >>>> further checking is done. Existing accounts need no changes with >>>> this new agreement. >>>> >>>> >>>> I can see that the Wiki docu is newer: >>>> https://github.com/icing/mod_md/wiki >>>> . >>>> >>>> >>>> Cannot check if the rest of mod_md docu is up to date and in line with >>>> trunk ? >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >> >
