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: vovim.hopto.org
I ran this command: certbot -c /etc/letsencrypt/cli.ini renew --standalone --preferred-challenges http-01
It produced this output: bash-4.4# certbot -c /etc/letsencrypt/cli.ini renew --standalone --preferred-challenges http-01
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /etc/letsencrypt/renewal/vovim.hopto.org.conf
Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator standalone, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for vovim.hopto.org
Waiting for verification…
Challenge failed for domain vovim.hopto.org
http-01 challenge for vovim.hopto.org
Cleaning up challenges
Attempting to renew cert (vovim.hopto.org) from /etc/letsencrypt/renewal/vovim.hopto.org.conf produced an unexpected error: Some challenges have failed… Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/vovim.hopto.org/fullchain.pem (failure)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/vovim.hopto.org/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: vovim.hopto.org
Type: connection
Detail: Fetching
http://vovim.hopto.org/.well-known/acme-challenge/_sAifYraHXKuJVQ0aV8LdHOyyz6_mTlOmDRMHMfRH_A:
Timeout during connect (likely firewall problem)
To 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.
bash-4.4# ls -l /var/log/letsencrypt/letsencrypt.log
-rw-r–r-- 1 root root 28737 Oct 22 11:30 /var/log/letsencrypt/letsencrypt.log
My web server is (include version):Apache (httpd-2.4.29-x86_64-2)
The operating system my web server runs on is (include version): Linux Slackware 14.2
My hosting provider, if applicable, is: none
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): certbot 0.39.0
The debug log is at https://pastebin.com/wE4kT3j8
I am trying to renew my certificate that was due for renewal on 21st October. As that date has now passed do I need to get a new certificate ?
Thanks.