SSL certificate renewed but website can't be reached

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. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

It produced this output: this site can't be reached, refused to connect ERR_CONNECTION_REFUSED

My web server is (include version):

The operating system my web server runs on is (include version): macOS Big Sure 11.4

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): don't know

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

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

1 Like

Hi @sucz,

How do you administer this web site? What interface does AWS give you that you use to set it up, install certificates, change the site content, or anything else?


Hi @schoen I use amazon lightsail to connect to an instance to renew my certificate. I change site content through wordpress. Not sure if I'm answering your question...

1 Like

What does that interface look like when you're renewing your certificate? And how did WordPress get installed and set up on your site?

1 Like

How did Wordpress get installed? Through amazon lightsail...?

1 Like

Welcome to the Let's Encrypt Community, Susan :slightly_smiling_face:

I'm seeing a Bitnami stack running WordPress 5.3.2-3 with Ubuntu 16.04.6 LTS (Xenial Xerus) (GNU/Linux 4.4.0-1113-aws x86_64) on AWS.

This is the official Bitnami documentation for using Let's Encrypt certificates with AWS (recommended):

This is Amazon Lightsail's bncert tutorial (alternatively recommended for improved understanding):

This is Amazon Lightsail's certbot tutorial (not recommended, but good for expanded knowledge):


Thank you. I have been using the Amazon tutorial and it always renews the certificate (even in this case) but I still don't have access to my site. Could the message I'm getting "site can't be reached" be something other than an SSL issue?

1 Like

It could be many things, including a firewall. I suspect though that it's a Bitnami misconfiguration resulting from trying to use certbot instead of bncert.

Bitnami stacks are great when they work. Unfortunately they tend to be brittle when they don't work.

The most expedient solution I can recommend is to create a similar topic in the Bitnami Community with a link to the topic you've created here. The Bitnami people are far more experienced at debugging their stacks than we are.

1 Like

ok, thanks very much.

1 Like

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