Dry run fails when I try it one an aws hosted node

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: nuudle.getone.io

I ran this command:sudo certbot renew --webroot --cert-name nuudle.getone.io --webroot-path /var/www/nuudle --dry-run

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

Processing /etc/letsencrypt/renewal/nuudle.getone.io.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 nuudle.getone.io
Using the webroot path /var/www/nuudle for all unmatched domains.
Waiting for verification…
Challenge failed for domain nuudle.getone.io
http-01 challenge for nuudle.getone.io
Cleaning up challenges
Attempting to renew cert (nuudle.getone.io) from /etc/letsencrypt/renewal/nuudle.getone.io.conf produced an unexpected error: Some challenges have failed… Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/nuudle.getone.io/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/nuudle.getone.io/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)


  • The following errors were reported by the server:

    Domain: nuudle.getone.io
    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): Apache/2.4.18

The operating system my web server runs on is (include version): Ubuntu 16.04.2 LTS

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): Yes

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot 1.3.0

Note: I have opened necessary ports via console before issuing this command.

Hi @karun

it’s not possible to check your file - timeout.

Your AWS has a firewall you have to open.

See your error:

Timeout during connect (likely firewall problem)

Hi @JuergenAuer
I am curious. Is this a new Firewall enforcement by AWS now? I never had this issue before. I will check.

Hi @JuergenAuer,
Everything is good. I am able to renew it now. I did not set any AWS Firewall stuff.

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