subject:"\[pfSense\] acme package\: wrong agreement URL"

Re: [pfSense] acme package: wrong agreement URL

2017-11-24 Thread Dave Warren

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 > wrote: > > Trying to use the acme package with

Re: [pfSense] acme package: wrong agreement URL

2017-11-18 Thread WebDawg

Did you report this as a bug? On Thu, Nov 16, 2017 at 4:36 AM, Brian Candler 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. > >

[pfSense] acme package: wrong agreement URL

2017-11-16 Thread Brian Candler

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//acme_issuecert.log shows HTTP 400 errors, with the following response: [Thu Nov 16 10:28:19 UTC 2017]