Timed out issue

Hi. let’s Encrypt.
I faced problem. I searched its own. but I couldn’t resolved.

First, I’m using Amazon AWS (EC2). site url is lishacast.com, server is nginx.
Security group inbound settings : http://i.imgur.com/Pp7IN8z.jpg (Outbound rule is All traffic.)
And I’ve completed the installation letsencrypt to ssh. : http://i.imgur.com/nr4SWGb.jpg
However, I can’t access my site. The error message is ERR_CONNECTION_TIMED_OUT.

I’m not sure I know what to do now.

Your site can be reached via https://, but not http://. You’ll need an inbound rule allowing HTTP to get rid of that timeout.

As for your cert, it seems your nginx is still using a self-signed certificate. You’ll want to change your server block that listens on port 443 by pointing ssl_certificate to /etc/letsencrypt/live/lishacast.com/fullchain.pem and ssl_certificate_key to /etc/letsencrypt/live/lishacast.com/privkey.pem. Take a look at the Mozilla SSL config generator for a more complete example config.

1 Like

Hi pfg. Thanks for your help! I modified ssl_certificate and ssl_certificate_key as you said.
But I seem to found another reason. It is Rate Limits. I think one day more than 5 certificates.
My other sites. SSL is working correctly. https://blog.banghoney.com
I didn’t know limit, so have too many attempts. :sob:
How do I solve this problem? Thank you very much. :slight_smile:

crt.sh shows that you have successfully issued multiple certificates for lishacast.com today. Simply pointing your web server to one of those certificates should be sufficient.

If you deleted those files, or don’t have access to them anymore for some other reason, you’ll have to wait 7 days before you’ll be able to issue additional certificates for that domain. There’s no way to bypass or reset the rate limits.

1 Like

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