Hi, I’m having trouble trying to get a new certificate using letsencrypt-nosudo. When it hits the “Requesting signature” step, it errors out with {"type":"urn:acme:error:serverInternal","detail":"Error creating new cert","status":500}. It does correctly issue and verify challenges for all of my dom…

Yep, I’m hitting the limit too.

Haven’t tried yet, will save my tries for the next test)

Hi @nit , all, Sorry for the troubles. We rolled out some production changes that caused an increase in latency, which in turn resulted in an increase in 500s due to timeouts. We’ve rolled back those changes for now. The relevant certificates are stored in our database and logs. In the instance of c…

So for now everything should work properly?

Works not for me, I wanted to expand my SANs, so I run with certonly and all SANs. It seems when I choose expanding and replacing the old cert there is used a new privkey. When I download the cert from crt.sh and try to bind it in apache there is an startup error because privkey doesnt matches with …

If the bug has truly been fixed, would it be possible for you to temporarily increase the request limit so that those who ran into the bug without the original keys could retry without waiting for up to 7 days which could potentially be past the certificate’s expiration date? Why has this bug n…

Thanks, I was able to retrieve a valid (key, cert) couple. I just will have to wait 7 days for issuing hostnames-n-z.crans.org with the SAN for the other half of our domains, hopefully without any issue.

Update on this topic: We found the issue that caused CT logging not to be retried right away for some certs and are working on a fix. We also have a committed fix for what we think was the core issue causing 500s. This should go out with Thursday's release, at which time we'll try again. [image] …

I try to generate the certificate using crans.fr which is a DNAME of crans.org and it works. So this issue is solved to me. Thanks for the quick solving !

Just wanted to let you guys know: getting cert is working again, with 10 more names added (38 in total now).

Server 500 but certificate still issued

Server

Topic		Replies	Views
Consistent 500's for new-cert (failing CAA for one domain) Issuance Tech	16	4932	September 18, 2017
Certificate error with large SAN cert Server	18	5861	November 10, 2017
Client receives "Error creating new cert" message from server Help	10	6348	December 5, 2015
Unable to get new certs, "error creating new cert" 500 error Help	29	7230	April 10, 2018
Getting Error when trying to get a new certificate Help	31	5560	February 16, 2024

Server 500 but certificate still issued

Related topics