ACME / Let's Encrypt - ""Registration key is already in use" and malformed
-
Im getting two errors when trying to make the cert.
First ""Registration key is already in use" and then "
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": 400As well.
Is the package broken?
-
That has been fixed for weeks. Update your ACME package, and if you don't see an update for the ACME package, update your firewall to the latest version and then it should pick up the update along the way.
-
Im seeing version 0.1.16 No updates for it.
-
Im seeing version 0.1.16
That's old.
"ACME" is package that has very regularly updates - checkout this forum https://forum.pfsense.org/index.php?board=15.0
See image for the latest version I have today - using of course, the latest pfSense version.No updates for it.
https://github.com/pfsense/FreeBSD-ports/commits/devel/security/pfSense-pkg-acme ….
Your pfSense doesn't locate packages anymore ? Updates ? What is your pfSense version ?
-
Im seeing version 0.1.16 No updates for it.
Update pfSense then, because if you don't see 0.1.30 then you are not on a current version of pfSense.
-
Updated and still nothing….
Getting this at the end of the log
v[Thu Mar 15 21:52:25 CET 2018] original='{
"type": "urn:acme:error:malformed",
"detail": "Unable to update challenge :: The challenge is not pending.",
"status": 400
}' -
That is a completely different error. That is the kind of error you get if you use DNS-Manual and tried to renew without clicking 'issue' first.
-
I'm using webroot ftp….tried to upload using SFTP worked.....I can reach the acme challenge via http....
The challenge is stored and generated correctly.
