Question
New droplet cannot ping default gateway
- Posted on June 2, 2024
- DigitalOcean DropletsNetworking
Asked by bryanpkc
I have just created a new droplet from a snapshot of another droplet running Ubuntu 16.04, with the intention to upgrade the new droplet while keeping the old one running. The new droplet started up fine, and I can ssh into it, but outbound connections from the droplet are completely blocked, and I cannot even ping the default gateway, even after disabling ufw. The IP address, gateway address, and the network mask have been confirmed to be correct (i.e. matching the values shown in the control panel). route -n and ip -br a output look correct. What else should I try?
Addendum: Clearly not all outbound packets are dropped, as my SSH connections are working. Also, a HTTP server running on the droplet is able to respond to access requests.
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.
Featured on Community
Get our biweekly newsletter
Sign up for Infrastructure as a Newsletter.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Become a contributor
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Heya, bryanpkc
My initial approach will be to ensure that the network configuration files, such as
/etc/network/interfacesor Netplan configuration files (if applicable), are correctly set up. For Ubuntu 16.04, the network interfaces file should be checked:Make sure the configuration matches what is provided in the control panel.
You can also check the system logs for any relevant error messages:
Hope that this helps!
I might be wrong but this could be due to the difference in how Ubuntu handles network from Ubuntu 16 to whatever new version you have now.
Hey @bryanpkc,
What I could suggest here as a first step is going over the steps listed in this troubleshooting doc:
There are troubleshooting steps for Ubuntu 16 as well.
If you are still seeing this issue, I could suggest trying to re-create the Droplet to see if this helps.
Also, both the re-creation and the troubleshooting doc do not help, it might be best to reach out to the DigitalOcean support team and provide them with as much information as possible:
Hope that helps!
- Bobby.