ACME pkg v1.0
-
ACME pkg v1.0 is out now for pfSense Plus 25.07, 24.11, and CE 2.8.0.
Bug fixes/changes:
-
Synchronized with upstream acme.sh version 3.1.2 (master branch)
-
Various upstream bug fixes for DNS providers
-
Removed deprecated OCSP stapling options
https://redmine.pfsense.org/issues/16195 -
Fixed a bug with nsupdate and challenge aliases
https://redmine.pfsense.org/issues/15061 -
Added initial support for custom ACME servers
Add servers on the General Settings tab.
Note: This feature has undergone basic testing, however, there is no way to know if it will work against any custom ACME server, and there is no way for the package to know which validation methods are supported by an ACME server.
Use at own risk. Test before deployment.
Existing Provider Changes:
-
Gandi LiveDNS has deprecated API keys and now uses a Personal Access
Token (PAT). Configure the new PAT option to ensure future updates
work. -
Active24 changed from a single Token to an API Key + API Secret and
must be reconfigured before use. -
Selectel API version v1 is deprecated, but still available as a new
option, along with new API v2 options. Must be reconfigured before
use.
New DNS Providers:
- Beget.com
- EdgeCenter.ru
- FreeMyIP.com
- HE.net DDNS
- Mijn.host
- OpenProvider via REST API
- Spaceship
- Technitium
- ZoneEdit
Note: The change from 0.9 to 1.0 does not reflect any particular significant change in the package, but it has been stable for so long that keeping its version number below zero no longer made sense.
-
-
J jimp pinned this topic
-
@jimp Just updated acme package to v1, and did a renew of certs even though they were not do for a while. All went fine, using dns-cloudflare
On 25.07 of pfsense+
-
Same pfSense here, upgrade to acme to "1.0" and hit the renew button.
I'm using the "nsupdate" method. The cert was renewed just fine. -
I tried to update ACME on a 2.8.0 pfsense, actually stuck and broken the installation, can't get to pfsense Webgui or SSH.
I'll get back with more info.