How Do I Troubleshoot Connection Issues to My DigitalOcean Droplet?

Start with the Basics

Connection issues usually fall into three categories: you cannot SSH in, your website does not load, or DNS does not resolve. Work through each layer systematically instead of guessing.

Problem 1 — Cannot SSH

Check if the Droplet is running. In the control panel, verify the status is green (active), not off or locked.

Verify the IP. Make sure you are connecting to the current IP — it changes if you destroy and recreate the Droplet.

Test port 22 reachability:

nc -zv YOUR_DROPLET_IP 22
# or: telnet YOUR_DROPLET_IP 22

If the connection times out, the issue is network-level:

• Cloud Firewall: check that port 22 is allowed for your IP under Networking → Firewalls
• UFW on the Droplet: use the web console (Access → Launch Console) to run sudo ufw status
• SSH service down: in the console, run sudo systemctl status sshd and sudo systemctl start sshd

Permission denied? Your SSH key may not be installed. Use the DigitalOcean web console to access the server and check /root/.ssh/authorized_keys.

Problem 2 — Website Not Loading

curl -I http://YOUR_DROPLET_IP

• Connection refused: the web server is not running — sudo systemctl status nginx and restart it
• Timeout: firewall blocking ports 80/443 — check Cloud Firewall and UFW rules
• 502 Bad Gateway: Nginx is running but your app (Node.js, PHP-FPM) is down — check pm2 status or systemctl status php8.3-fpm

Problem 3 — DNS Not Resolving

dig yourdomain.com +short
nslookup yourdomain.com

If these return nothing or the wrong IP, the problem is DNS — not your server. Check A records at your DNS provider and wait for propagation.

Use the Recovery Console

When SSH is completely broken, use Access → Launch Recovery Console or Launch Droplet Console in the control panel. This gives you terminal access through the browser, bypassing SSH and firewalls.

Check DigitalOcean Status

Visit status.digitalocean.com to rule out platform-wide outages in your region before deep-diving into your config.

Diagnostic Checklist

• Droplet powered on?
• Correct IP address?
• Cloud Firewall allows your traffic?
• Service running inside the Droplet?
• DNS pointing to the right IP?

Most connection issues are firewall rules or stopped services — both fixable in under five minutes once you identify the layer.