For anyone else still having issues, it looks like the package was updated November 16th.
On Sat, Nov 18, 2017, at 20:39, WebDawg wrote: > Did you report this as a bug? > > On Thu, Nov 16, 2017 at 4:36 AM, Brian Candler <[email protected]> > wrote: > > Trying to use the acme package with pfsense 2.4.1 and the LetsEncrypt > > staging server > > > > Certificate enrolment failed, although all the output was in green. > > > > /tmp/acme/<cert>/acme_issuecert.log shows HTTP 400 errors, with the > > following response: > > > > [Thu Nov 16 10:28:19 UTC 2017] > > response='{"type":"urn:acme:error:malformed","detail":"Provided agreement > > URL [https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf] does > > not match current agreement URL > > [https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf]","status": > > 400}' > > > > I couldn't see how to change this in the GUI, so I had to edit > > /usr/local/pkg/acme/acme.sh > > > > I presume the package needs updating? > > > > Thanks, > > > > Brian. > > _______________________________________________ > > pfSense mailing list > > https://lists.pfsense.org/mailman/listinfo/list > > Support the project with Gold! https://pfsense.org/gold > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold > _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
