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.
When it comes to ufw, I often recommend a full reset to ensure the firewall is properly configured to meet the specific needs of what I’m using the server for. In some cases, it’s often best to specify the ports versus using the shortcodes.
I posted a quick guide on how to reset ufw, which may be helpful for future use.
https://www.digitalocean.com/community/questions/how-to-reset-the-firewall-on-ubuntu
Found two problems. In setting up my certificate I had started a new serverblock for my website but not completed it. I was working with the default serverblock to work out the firewall problems. Both server blocks (which now had my domain name in them) were in the sites-enabled folder and that screwed up the firewall.
The second problem was the snakeoil snippet pointing which pointed to a certificate that was truly snakeoil. Deleting that snippet and pointing to the correct certificate and key fixed the problem.
Hello,
Can you try explicitly allowing Nginx HTTPS as well with this command:
ufw allow 'Nginx HTTP'
Then after that run this command to verify your change:
ufw status
Hope that this helps! Bobby