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. https://crt.sh/?q=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: www.corauratum.com
I ran this command: auto renew
It produced this output: usual timeout during connect
My web server is (include version): Nginx 1.15.12
The operating system my web server runs on is (include version): Ubuntu 16.04.6 LTS
My hosting provider, if applicable, is: Linode
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.31.0
After running for a while now (almost a year?), I’ve started getting the timeout errors that many people are reporting. NOTE: my situation is a little different because I have two domains with two different IP’s, so if you do the usual scan for the IP, you’ll get the one for the main domain and not the one that has the certificate. As I said, everything has been working just fine until the latest auto-renew job ran. Since this is having so much trouble, I would like to switch to using the DNS plugin for Linode. Given that this is an existing certificate, do I just install the plugin and then add it to certbot? Your instructions are for a new installation and I just want to verify the steps I need to switch the challenge method.