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: bcfurries.com, gryphonic.com, critter.net
I ran this command: /usr/local/bin/certbot renew
It produced this output:
: 2/{1}root@cornix:~# /usr/local/bin/certbot renew --dry-run
Saving debug log to /var/log/letsencrypt/letsencrypt.log
-------------------------------------------------------------------------------
Processing /usr/local/etc/letsencrypt/renewal/bcfurries.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 bcfurries.com
http-01 challenge for www.bcfurries.com
Waiting for verification...
Cleaning up challenges
Attempting to renew cert (bcfurries.com) from /usr/local/etc/letsencrypt/renewal/bcfurries.com.conf produced an unexpected error: Failed authorization procedure. www.bcfurries.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://www.bcfurries.com/.well-known/acme-challenge/PbZ_VPfj8uazTJS_lXCS6tPoBDpb2Eh-8PnYWd745nE: Timeout. Skipping.
-------------------------------------------------------------------------------
Processing /usr/local/etc/letsencrypt/renewal/gryphonic.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 gryphonic.com
http-01 challenge for www.gryphonic.com
Waiting for verification...
Cleaning up challenges
Attempting to renew cert (gryphonic.com) from /usr/local/etc/letsencrypt/renewal/gryphonic.com.conf produced an unexpected error: Failed authorization procedure. gryphonic.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://gryphonic.com/.well-known/acme-challenge/k0AhZgtlkugQ5EHEhLtWt36_YOFPv-p8Cj5fXaLj_GA: Timeout. Skipping.
-------------------------------------------------------------------------------
Processing /usr/local/etc/letsencrypt/renewal/critter.net.conf
-------------------------------------------------------------------------------
Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for critter.net
http-01 challenge for mail.critter.net
http-01 challenge for secure.critter.net
http-01 challenge for smtp.critter.net
Waiting for verification...
Cleaning up challenges
Attempting to renew cert (critter.net) from /usr/local/etc/letsencrypt/renewal/critter.net.conf produced an unexpected error: Failed authorization procedure. mail.critter.net (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://mail.critter.net/.well-known/acme-challenge/cdSQu377XepTUUNX4YOQamWSx10ueVKh1Dei87ggYVA: Timeout, critter.net (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://critter.net/.well-known/acme-challenge/qfFLsxU6mURArjiyIb8fycbKVJCDUi0zE4g9QAa9Yk4: Timeout, secure.critter.net (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://secure.critter.net/.well-known/acme-challenge/yHI07aa9higIM-F3m5FNbW-aN4U1No-zgecqo4Cah_I: Timeout, smtp.critter.net (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://smtp.critter.net/.well-known/acme-challenge/Jq6plrnIAF--fryEuWCUETqRhS7CgoKhHUxhsegHcow: Timeout. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/usr/local/etc/letsencrypt/live/bcfurries.com/fullchain.pem (failure)
/usr/local/etc/letsencrypt/live/gryphonic.com/fullchain.pem (failure)
/usr/local/etc/letsencrypt/live/critter.net/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:
/usr/local/etc/letsencrypt/live/bcfurries.com/fullchain.pem (failure)
/usr/local/etc/letsencrypt/live/gryphonic.com/fullchain.pem (failure)
/usr/local/etc/letsencrypt/live/critter.net/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: gryphonic.com
Type: connection
Detail: Fetching
http://gryphonic.com/.well-known/acme-challenge/k0AhZgtlkugQ5EHEhLtWt36_YOFPv-p8Cj5fXaLj_GA:
Timeout
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: mail.critter.net
Type: connection
Detail: Fetching
http://mail.critter.net/.well-known/acme-challenge/cdSQu377XepTUUNX4YOQamWSx10ueVKh1Dei87ggYVA:
Timeout
Domain: critter.net
Type: connection
Detail: Fetching
http://critter.net/.well-known/acme-challenge/qfFLsxU6mURArjiyIb8fycbKVJCDUi0zE4g9QAa9Yk4:
Timeout
Domain: secure.critter.net
Type: connection
Detail: Fetching
http://secure.critter.net/.well-known/acme-challenge/yHI07aa9higIM-F3m5FNbW-aN4U1No-zgecqo4Cah_I:
Timeout
Domain: smtp.critter.net
Type: connection
Detail: Fetching
http://smtp.critter.net/.well-known/acme-challenge/Jq6plrnIAF--fryEuWCUETqRhS7CgoKhHUxhsegHcow:
Timeout
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: www.bcfurries.com
Type: connection
Detail: Fetching
http://www.bcfurries.com/.well-known/acme-challenge/PbZ_VPfj8uazTJS_lXCS6tPoBDpb2Eh-8PnYWd745nE:
Timeout
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): Apache 2.4.29
The operating system my web server runs on is (include version): FreeBSD 10.3-p24
My hosting provider, if applicable, is: hetzner
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
Additionally, I have verified that I can make HTTP connections to each of the virtual domains mentioned above. Using the URL specified, I get a 404 which is expected as the certbot client is not running to create the appropriate file(s)/director(y|ies) when I test with my browser.