Is There a Problem with Let's Encrypt?

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: sdd.regulatoryintelligence.com

I ran this command: Used Let's Debug to see status of HTTP-01

It produced this output:

InternalProblem
WARNING
An internal error occurred while checking the domain
An unknown issue occurred when performing a test authorization against the Let's Encrypt staging service: acme: parsing error body: invalid character '<' looking for beginning of value -

405 Not Allowed

405 Not Allowed


nginx

StatusNotOperational
WARNING
The current status as reported by the Let's Encrypt status page is Service Disruption as at 2024-05-31 19:23:10.783 +0000 UTC. Depending on the reported problem, this may affect certificate issuance. For more information, please visit the status page.

My web server is (include version): Apache 2.4

The operating system my web server runs on is (include version): CentOS 7.9

My hosting provider, if applicable, is: Rackspace

I can login to a root shell on my machine (yes or no, or I don't know): Yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): Plesk 18.0.61

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

Please see

My monitoring tools can confirm that staging (Let's Encrypts test system) has been mostly down for a few hours now. Production had a small temporary hiccup, but is apparently all OK now.

6 Likes
4 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.