Join 1M+ other developers and:
- Get help and share knowledge in Q&A
- Subscribe to topics of interest
- Get courses & tools that help you grow as a developer or small business owner
Cannot connect to droplet after reboot or idle for too long (Console & SSH)
I’ve been having issues when it comes to rebooting my droplet. At first this happened in-between a SSH session while it was idle, but since then it’s been happening consistently every time I reboot my droplet.
When I reboot my droplet after installing some programs or changing an important config (usually Nginx or another program that can’t work without restarting the server anyway), and then there’s no internet.
Can’t connect inside the droplet through the console or outside using the domain, nor can I ping to it from my server.
What I’ve had to do is:
Take of snapshot of malfunctioning droplet
Make a new droplet from scratch
Change the domain DNS records, Nginx config, etc to fit the new droplet
And then it works again. But sadly I can’t really do this forever because eventually billing is going to bite me in my behind.
No idea what’s causing this because Nginx logs don’t give any errors besides the conflicting server name errors, which was solved by removing another domain name I was using for the site.
Firewall isn’t blocking anything because when I’ve connected through other devices or asked other people to connect it still won’t go through.
I know currently there is maintenance for Spaces in SFO2 where my droplet region is but I do not use Spaces, so I am not sure if that is affecting anything in my case.
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.×