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.
Hello,
If you ping your domain name and you get the IP of your Droplet, this means that your DNS is set up correctly.
I believe that the problem must be with the Nginx configuration.
You could try to do the following:
sudo netstat -plant | grep 80
Feel free to share the output here.
sudo nginx -t
Status OK then try restarting Nginx to make sure that the latest changes that you’ve made are in place:systemctl restart nginx
I would guess that it could be the listen directive that might be causing the problem for you. Can you, as a test, try to change it from:
listen xx.xxx.xx.xxx:80 default deferred;
To:
listen 80 default deferred;
Basically that way if you run netstat again it would show you that nginx listens on 0.0.0.0:80 which means that it will accept connections from any IP and you should be able to access the service remotely.
Let me know how it goes! Regards, Bobby