Renewal Gone Wrong - can't access site

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:
sudo /opt/bitnami/letsencrypt/lego --email="" --path="/opt/bitnami/letsencrypt" renew

It produced this output:
Ran fine but can't access site anymore

My web server is (include version):
Google Cloud Bitnami WordPress

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

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I 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):

What do you mean by "can't access site anymore"? What error do you get? Timeout? Certificate errors?

May be a dumb question, but did you restart the bitnami services after renewing the certificate?

504 time out and the certificate gets an error about the name not matching the input.

Yes I did restart the server thanks.

Strange as I copy and paste the same ssh commands every 60 days!

Hi @nativeneil

checking your domain via - there is a https timeout (10 seconds).

Checking with my browser - there is the 504:

Gateway Timeout

The gateway did not receive a timely response from the upstream server or application.

But: The certificate is valid, with 4 domain names, valid 2021-03-30.

So certificate creation and installation had worked.

504 is only an internal server error, your proxy logic doesn't work -> fix that.


D:\temp>download -h
SSL-Zertifikat is valide
Error (1): Timeout für Vorgang überschritten

60061,61 milliseconds
60,06 seconds

1 Like

Thanks @JuergenAuer - any tips on where to get started with proxy logic?
Everything worked ok yesterday before I updated the certificates.

1 Like

Solved - something was eating up hard dive space. Cleared cache and works fine now


Happy to read you have found the problem :+1:

Such 5** errors are normally individual local problems.


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