Bug #14199
closed
ACME - Issue with corrupted cert
Added by Juan Francisco Rodriguez Garcia about 2 years ago.
Updated almost 2 years ago.
Affected Plus Version:
23.01
Affected Architecture:
All
Description
Hi team
After creating a new cert in HAProxy i got an timeout on the webui interface then receive this error:
PHP ERROR: Type: 1, File: /usr/local/www/acme/acme_certificates.php, Line: 261, Message: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/acme/acme_certificates.php:261
Stack trace:
#0 {main}
I can see the certificate but i dont have the option to delete the cert
thanks
Files
Attaching the Acme section of my config.xml backup which had this issue after upgrading to the new release on Feb 17 2023
- Assignee set to Jim Pingle
The attached configuration snippet isn't a valid configuration for ACME. I'm not sure how it ended up in that state, but the domain list is empty so it couldn't have been doing anything useful. Input validation prevents me from even attempting to create an entry such as that, so I'm not sure what happened there.
The other errors appear to be from invalid certificate data as well.
And the original description here mentions HAProxy, not ACME. HAProxy doesn't have anything to do with ACME directly, though there are ways to hook them together they aren't done by default.
Hi Jim .
My bad, I said HAProxy by mistake, I am using ACME for this, attached screenshot
I'm running pfSense+ 23.01 on a Netgate 2100.
This morning I was removing HAProxy (I've migrated to Nginx Proxy Manager (NPM) on another machine). Since NPM is now handling the wildcard cert, I wanted to remove it from pfSense's ACME configuration.
I deleted it and am now left with the error outlined above. See attached.
Problem continues after update to 23.05
- Status changed from New to In Progress
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
- Status changed from Feedback to Resolved
Also available in: Atom
PDF