Featured AI Products
Compute
Build, deploy, and scale cloud compute resources
Containers and Images
Safely store and manage containers and backups
Managed Databases
Fully managed resources running popular database engines
Management and Dev Tools
Control infrastructure and gather insights
Networking
Secure and control traffic to apps
Security
Help protect your account and resources with these security features
Storage
Store and access any amount of data reliably in the cloud
Browse all products
AI/ML
CMS
Data and IoT
Developer Tools
Gaming and Media
Hosting
Security and Networking
Startups and SMBs
Web and App Platforms
See all solutions
Community
Documentation
Developer Tools
Get Involved
Utilities and Help
Become a Partner
Marketplace
Pricing

- Community
- DigitalOcean
- Community
- DigitalOcean

Issue with Droplet connecting to GODaddy Domain name

Posted on March 19, 2025

Currently have a droplet set up as a Rserver with R and Rshiny installed to run a small shiny app. This works perfectly with the IPv4 address and I am currently using nginx as the http web server.

I have a custom domain and have configured the name servers within my domain purchaser to use the digitalocean ones. The name servers were completely propogated with the dnschecker, but im still experiencing ERR_CONNECTION_REFUSED during domain connection and not sure why.

I have checked countless answers to this question, theres no firewall so dont think its a port problem?

Any advice would be very helpful.

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.

Bobby

March 20, 2025

Hey there 👋

If the IP works but the domain shows ERR_CONNECTION_REFUSED, it’s likely an Nginx config issue, not DNS.

Make sure you’ve added a proper server block for your domain in Nginx, something like:

server {
    server_name yourdomain.com;
    root /path/to/your/app;
    ...
}

Also, make sure Nginx has been reloaded after changes:

sudo systemctl reload nginx

You can double-check if Nginx is listening with:

sudo netstat -tulnp | grep nginx

If you’d like, feel free to share your Nginx config here, happy to take a quick look.

- Bobby

alexdo

March 31, 2025

Heya,

You can confirm your domain resolves to your Droplet’s IP:

dig yourdomain.com +short

It should return the correct IPv4 address. If not, the issue is DNS-related (even if propagation “seems” done).

Regard

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

View all products

Start building today

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.