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: madisonmycologicalsociety.com
I ran this command: certbot renew --dry-run
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /etc/letsencrypt/renewal/madisonmycologicalsociety.com.conf
Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for madisonmycologicalsociety.com
http-01 challenge for www.madisonmycologicalsociety.com
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (madisonmycologicalsociety.com) from /etc/letsencrypt/renewal/madisonmycologicalsociety.com.conf produced an unexpected error: Failed authorization procedure. madisonmycologicalsociety.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://madisonmycologicalsociety.com/.well-known/acme-challenge/SlQu6j6nTa3XRX3IGq4RZJR1HlF-sKDdh8bY3OIp00M: Connection refused, www.madisonmycologicalsociety.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://www.madisonmycologicalsociety.com/.well-known/acme-challenge/W6kuG2NgCT4hot-zp0p_KdLhchuT2hlLu0u-QlwUddc: Connection refused. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/madisonmycologicalsociety.com/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates below have not been saved.)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/madisonmycologicalsociety.com/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)
1 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: madisonmycologicalsociety.com
Type: connection
Detail: Fetching
https://madisonmycologicalsociety.com/.well-known/acme-challenge/SlQu6j6nTa3XRX3IGq4RZJR1HlF-sKDdh8bY3OIp00M:
Connection refusedDomain: www.madisonmycologicalsociety.com
Type: connection
Detail: Fetching
https://www.madisonmycologicalsociety.com/.well-known/acme-challenge/W6kuG2NgCT4hot-zp0p_KdLhchuT2hlLu0u-QlwUddc:
Connection refusedTo fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you’re using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
My web server is (include version): OpenLiteSpeed 1.4.46
The operating system my web server runs on is (include version): Ubuntu 18.04.2 LTS
My hosting provider, if applicable, is: Digital Ocean
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): nope!
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot 0.31.0
I’m not sure exactly what the problem is and I’m also relatively new to this stuff. We have a google domain and were using google’s DNS servers for our A and AAAA records, but I think when I issued our original certificate it was on Digital Ocean’s name servers, so I switched it back to try and renew the certs. Still getting the connection refused errors… I tried renewing by ssh-ing from my phone as well (using a different internet service) and also received the same errors… any help would be greatly appreciated.