Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
lets do a flow based analysis
run below command
if it says COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME nginx 7428 root 23u IPv4 76877969 0t0 TCP *:https (LISTEN) nginx 26768 www-data 23u IPv4 76877969 0t0 TCP *:https (LISTEN)
than you should look at number 3
if it doesnt show anything look for your config file where you define the hosting to be residing inside sites-enabled directory not the sites-available
telnet localhost 443 if it worked and you get the response. than curl -vvvvvv https://localhost/
if it still didnot worked than you can contact superdevop.com to have a look for free. if its small glitch we do it for free.
I would recheck to see for sure if you do not have any firewalls running. If you do, check to see if 443 is opened. If I remember correctly, my VPS came with a firewall that I had to opened specific ports to, so please recheck this.
Your server block seems to be ok. It could be an issue with the keys, which I’d suggest regenerating. It could also be that the keys themselves are in a folder with permissions issues.
I use my keys from LetsEncrypt, which look like the below.
ssl_certificate /etc/letsencrypt/live/mydomain.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/mydomain.com/privkey.pem;
Sorry, this one has me a little stumped too.