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 you setup your domain, did you use DigitalOcean’s name servers? If so, was the domain also setup through the dashboard under Networking? If you’ve not added your domain yet, and set it to point to the Droplet IP, that may very well be the issue.
If you’re able to provide the domain name, we can check for any potential issues in the zone file.
The issue I’m seeing is that when I access simplytldr.com, I’m redirected to the domain with the www instantly.
Normally, that’s not an issue itself, but what is an issue is that you don’t have a valid CNAME for www, so when I’m redirected, www.simplytldr.com results in failed resolution.
So you would need to add a CNAME to your DNS that points www to simplytldr.com, like so:
CNAME www simplytldr.com
From the DigitalOcean Dashboard => Networking => simplytldr.com
Hostname => www
Is An Alias of => simplytldr.com
You can leave TTL at its default setting.
Now, as long as NGINX is setup to respond to both variations, that should resolve the issue. You’d want to check server_name to make sure it looks something like:
server_name simplytldr.com www.simplytldr.com;
EasyEngine may do a slightly different setup, but it looks like it’s redirecting all traffic on the main domain (simplytldr.com) to www.simplytldr.com and since that entry is missing, it won’t resolve.