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: voigtstr.com
I ran this command: sudo certbot renew --dry-run
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /etc/letsencrypt/renewal/minecraft.voigtstr.com.conf
Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for minecraft.voigtstr.com
Waiting for verification...
Challenge failed for domain minecraft.voigtstr.com
http-01 challenge for minecraft.voigtstr.com
Cleaning up challenges
Attempting to renew cert (minecraft.voigtstr.com) from /etc/letsencrypt/renewal/minecraft.voigtstr.com.conf produced an unexpected error: Some challenges have failed.. Skipping.
Processing /etc/letsencrypt/renewal/music.voigtstr.com.conf
Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for music.voigtstr.com
Waiting for verification...
Challenge failed for domain music.voigtstr.com
http-01 challenge for music.voigtstr.com
Cleaning up challenges
Attempting to renew cert (music.voigtstr.com) from /etc/letsencrypt/renewal/music.voigtstr.com.conf produced an unexpected error: Some challenges have failed.. Skipping.
Processing /etc/letsencrypt/renewal/voigtstr.com.conf
Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for voigtstr.com
http-01 challenge for www.voigtstr.com
Waiting for verification...
Challenge failed for domain voigtstr.com
Challenge failed for domain www.voigtstr.com
http-01 challenge for voigtstr.com
http-01 challenge for www.voigtstr.com
Cleaning up challenges
Attempting to renew cert (voigtstr.com) from /etc/letsencrypt/renewal/voigtstr.com.conf produced an unexpected error: Some challenges have failed.. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/minecraft.voigtstr.com/fullchain.pem (failure)
/etc/letsencrypt/live/music.voigtstr.com/fullchain.pem (failure)
/etc/letsencrypt/live/voigtstr.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/minecraft.voigtstr.com/fullchain.pem (failure)
/etc/letsencrypt/live/music.voigtstr.com/fullchain.pem (failure)
/etc/letsencrypt/live/voigtstr.com/fullchain.pem (failure)
** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates above have not been saved.)
3 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: minecraft.voigtstr.com
Type: connection
Detail: Fetching
http://minecraft.voigtstr.com/.well-known/acme-challenge/6DyXMRsfiGLE71-CGfMec7LXCugBLcYAD_EzY5JBfl0:
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. -
The following errors were reported by the server:
Domain: music.voigtstr.com
Type: connection
Detail: Fetching
http://music.voigtstr.com/.well-known/acme-challenge/oyhrnFULPJul7zcxL6jTHLyWiKv8BSBh20QDNoe71TE:
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. -
The following errors were reported by the server:
Domain: voigtstr.com
Type: connection
Detail: Fetching
http://voigtstr.com/.well-known/acme-challenge/3EIVpOR-2C_elNq4g1CMaWKHujRCHoODqdvcjCqgjMA:
Timeout during connect (likely firewall problem)Domain: www.voigtstr.com
Type: connection
Detail: Fetching
http://www.voigtstr.com/.well-known/acme-challenge/vl-mmrcb4He7-DwvHvu-_DzT6N-MO-BT9hHFPVXmud8:
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.
My web server is (include version):
Server version: Apache/2.4.41 (Ubuntu)
Server built: 2022-01-05T14:49:56
The operating system my web server runs on is (include version):
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.3 LTS
Release: 20.04
Codename: focal
My hosting provider, if applicable, is: self hosted
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.40.0
A bit of background. I had the system working fine when I was on a static IP. We have since moved house and I'm now now on dynamic IP but have a dedicated IP through PUREVPN which is connected through PPTP. I've opened ports 80,465,587,443,143,993 so far on PUREVPN's portal and in my Asus router (although if data is coming through the PPTP tunnel then I probably just need the vpn ports open?)
What do I need to run next in terms of troubleshooting?
Cheers,
Simon