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.
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.
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.