ACME - Issue with corrupted cert
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
I can see the certificate but i dont have the option to delete the cert
Updated by Jim Pingle 2 months ago
- 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.
Updated by Juan Francisco Rodriguez Garcia 2 months ago
- File Captura de pantalla 2023-03-30 a las 0.27.06.png Captura de pantalla 2023-03-30 a las 0.27.06.png added
Hi Jim .
My bad, I said HAProxy by mistake, I am using ACME for this, attached screenshot
Updated by Kevin Dorff 2 months ago
- File hszsyKiBdC.png hszsyKiBdC.png added
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.
Updated by Juan Francisco Rodriguez Garcia about 2 months ago
- File PHP_errors (1).log.zip PHP_errors (1).log.zip added
Attached PHP error log
Updated by Juan Francisco Rodriguez Garcia 12 days ago
Problem continues after update to 23.05