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: www.righthandbuyer.com
I ran this command: ./letsencrypt-auto --renew. This didn't work at all. I searched and found several people saying Ubuntu 14.04 is no longer supported for certbot. I had done a manual cert prior, so it's possible this was the problem to begin with. I then tried AcmeShell (GitHub - acmesh-official/acme.sh: A pure Unix shell script implementing ACME client protocol), which was recommended as a pure shell script that can be used with Let's Encrypt.
It produced this output: This produced a timeout error, and I wasn't able to parse the info that I received back when I tried to get more verbose information. It looked like it wasn't connecting at all.
I then tried rolling my Digital Ocean files back to earlier this morning's version to get things working again, but the site would not connect, as I have the site set to only connect via https, and the SSL cert is no longer working.
My web server is (include version): Ubuntu 14.04.
The operating system my web server runs on is (include version): Nginx.
My hosting provider, if applicable, is: Digital Ocean VPS.
I can login to a root shell on my machine (yes or no, or I don't know): Yes, and am having no trouble even after the issue.
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): Apparently no Certbot, just manual version.