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.

By Rayjunqueira
Well, I have a droplet running within DigitalOcean, and then I decided to create an A domain within DigitalOcean with my application’s IP. Inside my droplet, through Nginx, I configured my server with the IP and my port directing it to the domain link.
Although inside my droplet I’m able to call my API through the domain link with a status 200 OK using a curl command, outside the droplet (browser, Postman, PC terminal) when I call the API using curl, it never recognizes it.
So, I gave up trying to run directly with the DigitalOcean domain and started using another registration service, calling my DigitalOcean domain by ‘ns1.digitalocean.com,’ ‘ns2.digitalocean.com.’… However, to my surprise, the registration service says that the search with ns1.digitalocean.com was refused. So, would this be a DNS issue? I can’t understand why my domain on DigitalOcean never works.
PS: Requesting my API by IP and port works normally, but when it comes to the domain this never happens.
petercorrea
Chatree Kunjai
e6317acc26184445891017fc7a2d90
a18c8eb1471849c38a67f0898471e8
Sanjeev Mansotra
mhmmd-ysf
Michael Sampino
Seymen Pek
Danny Aung
colinbester
JUST JELLY
FloatingBlueGreenSquid