Suddenly 502 bad gateway on Certificate after working well for long time

[MMSN]

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. crt.sh | 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: http://supershot.click/

I ran this command:

It produced this output: 502 bad gateway

My web server is (include version): nginx/1.18.0 (Ubuntu)

The operating system my web server runs on is (include version): Ubuntu 20.04.6 LTS (GNU/Linux 5.15.0-1030-aws x86_64)

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

[_az]

What makes you think the problem is related to your SSL certificate? SSL/HTTPS appears to be working just fine on your server.

I would guess that the 502 has some unrelated cause.

[webprofusion]

@MMSN

502 bad gateway

This normally means your web server is configured to pull it's content from something else (reverse proxy), like another application server on the same machine or a different machine. If that other service stops running then your nginx can't proxy that information anymore.