502 bad gateway after installing certbot

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: thewebofinteriors.com

I ran this command: After installing certbot.

It produced this output: 502 bad gateway

My web server is (include version): NGINX

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

My hosting provider, if applicable, is:

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

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

Hi @Brian55

checking your domain you have a new certificate - https://check-your-website.server-daten.de/?q=thewebofinteriors.com

Issuer not before not after Domain names LE-Duplicate next LE
Let's Encrypt Authority X3 2019-11-15 2020-02-13 thewebofinteriors.com, www.thewebofinteriors.com - 2 entries duplicate nr. 1

And you use it:

Domainname Http-Status redirect Sec. G
http://thewebofinteriors.com/ 301 https://thewebofinteriors.com/
Html is minified: 109,46 % 0.076 A
http://www.thewebofinteriors.com/ 301 https://www.thewebofinteriors.com/
Html is minified: 109,46 % 0.077 A
https://thewebofinteriors.com/ 502 Html is minified: 110,29 % 2.720 S
Bad Gateway
https://www.thewebofinteriors.com/ 502 Html is minified: 110,29 % 2.437 S
Bad Gateway

There is no certificate error visible, all of your connections are ok:

The "Bad Gateway" is an internal problem of your application you have to fix. But I don't see a certificate problem.

Thanks for that. I wondered if you had come across this before and could maybe narrow down where to start looking. As the the site is just a one page test and was working fine until the installation.

Please: You have a Gateway. That’s not a simple setup, that’s a complex setup.

So you should know what to do how to fix that.

Your backend doesn’t work, your frontend works.

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