Related

Join the DigitalOcean Community Community

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
 Join Now
Is it possible to use the DO hostname on the private network instead of the Private IP? Question Question
Gateway host unreachable from Ubuntu box Question Question

Question

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

Posted May 25, 2018 3.6k views
UbuntuNetworking

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

Add a comment
srinivaspadala
By:
srinivaspadala

Related

Join the DigitalOcean Community Community

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
 Join Now
Is it possible to use the DO hostname on the private network instead of the Private IP? Question Question
Gateway host unreachable from Ubuntu box Question Question
Add a comment
1 comment

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.

×
Submit an Answer
1 answer
ryanpq May 25, 2018

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

Reply Report
  • srinivaspadala May 25, 2018

    Thank you for the response. We power off and power on the droplet which fixes the issue for now. But It was our running application server and caused this issue after high memory utilisation. I believe interfaces were configured properly and don’t see any errors related to that in system logs. I was not able to ping out from the droplet as well. DNS also didn’t work.

    Reply Report

Related

Looking for something else?

Ask a new question Search for more help