Timeout at EC2, seems like the port 443 is closed. But it shoud be open


#1

On Amazon EC2 this isn’t working:

$ sudo certbot certonly --standalone -d staging.my_domain123.com  --email admin@my_domain123.com 

debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for staging.my_domain123.com
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. staging.my_domain123.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://staging.my_domain123.com/.well-known/acme-challenge/WiPPjIaTOrcMXRVCePqwdAp5bTrDkN_-pl8QOq9ph0A: Timeout during connect (likely firewall problem)

IMPORTANT NOTES:
 - The following errors were reported by the server:

   Domain: staging.my_domain123.com
   Type:   connection
   Detail: Fetching
   http://staging.my_domain123.com/.well-known/acme-challenge/WiPPjIaTOrcMXRVCePqwdAp5bTrDkN_-pl8QOq9ph0A:
   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.

, although the port 443 is open


#2

The HTTP challenge always starts at port 80. You can redirect it to port 443 if you want, but your server will need to respond on port 80 first.


#3

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