Droplet is not able to reach over IP/hostname and can't ssh

We observed the high memory issues on our droplet through monitoring and while checking we are not able to ssh from ssh client but able to ssh from digitalocean web console. We restarted the services to make memory usage back to normal and still droplet is not reachable ( reboot the system as well due to system restart required message). On observing further we see that DNS is resolving the hostnames and not able to ping our droplet with IP or hostname. We see DNS related messages on journalctl -xe

Can you please help us in resolving the issue


Firewalls are allowed and did firewall reload as well

Submit an 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.

The web console doesn’t require networking within the droplet since it’s a service provided by the hypervisor. Your droplet sees the console as it’s local keyboard and display.

I would recommend checking to ensure your network settings in /etc/network/interfaces is configured properly and test to see if you can ping out from the droplet. If you can make outbound connections then I would recommend turning off your firewall to reconfigure it. Turning it off, if it is the issue, should immediately start allowing inbound connections