Question
Can't externally access anything on my droplet
I can access from the web console and all services/ports are running and open. I can’t access synergygaming.net and cannot connect to the mumble or teamspeak servers either. Does not work with the ip either 198.199.98.152 .
I also cannot connect via ssh.
Everything was fine this morning around 3 am. I noticed the droplet was started about 8 am and since then I cannot connect to anything
Any help would be appreciated.
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.
×
Did you recently upgrade per this? - https://www.digitalocean.com/community/tutorials/how-to-manually-initiate-droplet-upgrade-to-latest-digitalocean-cloud
I just upgraded per that document today. Upon power-on, my droplet worked for ~2 hours before I lost connectivity to my droplet too. I’m curious if it is related. I currently have an open support ticket, but no response yet.
I did not do an upgrade.
My droplet appears to have come back up on its own. How about yours?
It was never actually down. I can access it from the web console, but not from any external sources. Its still currently broken.
Now it’s back.
Had the same problem here. Magically resolved itself, except that it left my slave database out of sync and refusing to restart. SFO1 data center.
Same problem here. VNC access via the control panel only. No network connectivity in or out of the droplet.
Didn’t upgrade on my own, but there was a power on event about 9 hours ago.
You guys had this issue 4 years ago…
It’s 2018, I’m having this issue 2 days in a row. Never had anything like this before.
Yesterday had this issue, exactly as you described, server got back an hour later.
2 hours ago it happened again, server still has no networking in or out.
Opened support ticket yesterday, but they just today answered with generic reply like “right now, we saw your droplet online, are you still having this issue?”. I was about to close the ticket and it happened again.
Any clue why this happened?
The same happened to me 3 times in a row. I tried to setup a fresh droplet with plesk on it (preconfigured, from the marketplace.
After a while each time the droplet was only reachable from the web console anymore. FRA1. What’s going on?
This has been going on all day for me. Granted, I’m new, but it’s not a complicated docker droplet with nginx delivering on port 443 and port 80. From within the docker droplet i can access localhost:80 (which is forwarded through the docker network to nginx) and get the generic 301 permanently moved redirect response. I checked netstat output and im definitely exposing 80 and 443. I thought maybe I messed up my dns records, nope the A records are definitely correct. I have tried to hit the droplet through its ip address directly and it doesn’t work on port 80 or 443. I can connect to the droplet with ssh though. So this is strange.