Autocert Failure Error

[leaozinho]

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: knowyourcops.com

I ran this command: sudo certbot renew --dry-run

It produced this output: Attempting to renew cert (knowyourcops.com) from /etc/letsencrypt/renewal/knowyourcops.com.conf produced an unexpected error: HTTPSConnectionPool(host='acme-staging-v02.api.letsencrypt.org', port=443): Max retries exceeded with url: /directory (Caused by SSLError(SSLError("bad handshake: SysCallError(104, 'ECONNRESET')"))). Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/knowyourcops.com/fullchain.pem (failure)

My web server is (include version): Node.js v14.15.4

The operating system my web server runs on is (include version): Ubuntu 20.04 (LTS) x64

My hosting provider, if applicable, is: DigitalOceans

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): No

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

[griffin]

Welcome to the Let's Encrypt Community

Heads Up! Staging Under Maintenance!

…

[leaozinho]

hi! thanks ah - so this maintenance is the most likely cause of my error?

[griffin]

I guarantee it!

[jillian]

@leaozinho

I ran this command: sudo certbot renew --dry-run

The --dry-run flag in Certbot attempts to obtain a cert from the Let's Encrypt Staging environment. It's an excellent way to test that your server is correctly configured and will pass validation/obtain a certificate before attempting issuance in production. So, if you have any problems obtaining a cert with the --dry-run flag it's likely you will have the same issue when attempting issuance in prod. In this case, we are having maintenance in our Staging environment and the error you received is a result of that. When the maintenance period ends, you can try again and see if you are able to obtain a cert.

You can see all the past, ongoing, and upcoming maintenances at https://letsencrypt.status.io. It's also possible to subscribe for updates!