Let’s Encrypt new auth status 400

We fix the error Error: Error: Let’s Encrypt new auth status 400, which appears in Vesta when renewing the certificate from Let’s Encrypt.

Below we will analyze 2 errors. They usually follow each other. First the Error appears: Error: Let’s Encrypt new auth status 400… Trying to figure out what was wrong, after several repeated attempts, another Error: Let’s Encrypt new auth status 429

Error: Let’s Encrypt new auth status 429

Certificate request limit exceeded. You need to stop trying to get a certificate until you are completely blocked. Correct all errors and try to get the certificate again in a couple of hours / half a day.

Error: Let’s Encrypt new auth status 400

For some reason Let’s Encrypt cannot access the site to issue the certificate. One of the reasons is that the site is set to forward all incoming connections to https. And the certificate is issued only for http.

In this case, look for the place where the forwarding is set. It could be site config file, file .httaccess or site settings in nginx

Option two. Remove site from Vesta control panel. You only need to delete the site (the directory will be deleted). The database will remain (unless deleted separately).

Then create a website and start updating the certificate. Everything should pass successfully.

To avoid spending a day deploying your site, just move all your files a couple of levels higher. And then place them again inside the created site directory. This procedure should not take more than 10 minutes.

Similar Posts

Leave a Reply