The letsencrypt staging server is down?


#1

I just run my test project acme.sh

But I always get the following:

{
  "type": "http-01",
  "status": "pending",
  "uri": "https://acme-staging.api.letsencrypt.org/acme/challenge/4dBGBP766EhoLqrbLCq4G4ZTyz8knK-OJe5Iyvp2kxY/9549590",
  "token": "tIcrU-mxyL1yJePbIYUrLjuCVRCs_0UftBqnUiHsD7U"

The production server is ok.


#2

I’ve got same problem yesterday, but I’m not sure if it wasn’t some kind of certbot bug - no authorization files in webroot was created (webroot plugin). Before I realized, certbot managed to create over a hundred pending authz, and now I’m getting “There were too many requests of a given type :: Error creating new authz :: Too many currently pending authorizations.” error. Is there any way to cancel/invalidate those authz, or validate them manually by creating authorization files in webroot directory?


#3

It would theoretically be possible, yes, but you’d have to manually build some ACME requests and send them to the server. Probably not worth the hassle.

The pending authz rate limit is per account, so creating/using a new ACME account would let you bypass those limits. If you don’t have any existing certificates, you could probably just delete /etc/letsencrypt (or move it out of the way) to start from scratch. Otherwise, the certbot register subcommand together with --account should allow you to switch to a new account (consult certbot --help all for more details on usage).


#4

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