Certificate error returned and the certificate cannot be renewed

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: unlabelbrand.net

I ran this command: sudo certbot renew

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log

Processing /etc/letsencrypt/renewal/unlabelbrand.net.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 unlabelbrand.net
Waiting for verification...
Challenge failed for domain unlabelbrand.net
http-01 challenge for unlabelbrand.net
Cleaning up challenges
Attempting to renew cert (unlabelbrand.net) from /etc/letsencrypt/renewal/unlabelbrand.net.conf produced an unexpected error: Some challenges have failed.. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/unlabelbrand.net/fullchain.pem (failure)

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/unlabelbrand.net/fullchain.pem (failure)

1 renew failure(s), 0 parse failure(s)


  • The following errors were reported by the server:

    Domain: unlabelbrand.net
    Type: connection
    Detail: Fetching
    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): AWS EC2 (c6g.12xlarge)

The operating system my web server runs on is (include version): AWS Amazon Linux 2

My hosting provider, if applicable, is: AWS

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

No firewall has been configured on the server. Please help me work out how the certificate can be renewed and automatically renewed in future.


Welcome to the Let's Encrypt Community :slightly_smiling_face:

Though it most likely has nothing to do with the issue at hand, your certbot version is rather ancient and should probably be updated.

It appears that you previously managed to get a certificate for unlabelbrand.net that is missing www.unlabelbrand.net. Has anything about your setup changed since then?


Please have port 80 open, this is required for the http-01 challenge.

See also:



Did you get a closed response? I (and Let's Debug) just got a timeout.


@griffin Didn't test it myself, but firewalls or routers can give different responses, timeouts when packets are dropped, closed if a firewall or router is configured to send such an ICMP response. In any case, port 80 needs to be open :wink:


I wasn't judging or anything. I was genuinely curious. A "closed" response is an affirmation of a closed port while no response is a possibility of a closed port. I got mixed results:

1 Like

Thank you! Once I added CIDR to the inbound rule for port 80 and rebooted Apache, the certificate error was resolved!


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.