Since yesterday I cannot connect to my droplet via ssh. The connection simply times out. Also not possible to ping.
The firewall is disabled.
I can still login through the console.
What could be the issue here? Extremely bizzare

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.

×
1 answer

Hello, @JanWithVan

Could you please make sure that you’re able to connect/ping external hosts from the droplet? You can try to ping any external server/domain and see if everything is okay with the networking of your droplet.

You can also double check your emails if you’ve received any email from our support team as well. Sometimes in case of an emergency the networking of your droplet might be temporary disabled in order to prevent further issues.

Let me know how it goes.

Regards,
Alex

  • Hey Alex,

    Thanks for the speedy answer.
    It seems I cannot ping anything or even run apt-get in the droplet. How can i resolve this? Some config must have changed and there is a networking problem probably

    • Hey, @JanWithVan

      You can also check the steps I’ve listed in this question here:

      https://www.digitalocean.com/community/questions/i-think-my-droplet-is-unable-to-connect-with-the-internet?answer=60065

      What happens when you execute ifconfig -a can you see the eth0 interface listed? If this one is not present then we will need to sort this out.

      I know that sometimes some packages can be uninstalled somehow on reboot and there are cases where cloud-init is one of them. You can check if the package is present and currently installed on your droplet as well.

      A similar issue was reported here as well: https://www.digitalocean.com/community/questions/no-internet-connection-after-droplet-reboot

      You can check the answer posted from lukasea17033bb7e7ecf80fc21 and see the suggested steps if needed.

      1. Create the /etc/udev/rules.d/70-persistent-net.rules file
      2. Reboot tje server
      3. Set the network interface using the information from the /etc/netplan/50-cloud-init.yaml file
      4. Set the routing
      5. Configure the dns resolver conf file (you can skip this if your resolv conf is still present, I know you’ve mentioned that you’ve already copied this from a working droplet)
      6. You can run apt update and apt upgrade
      7. Install cloud-init if it’s missing and ufw and landscape:

      sudo apt install cloud-init

      sudo apt install ufw

      sudo apt install landscape-common

      Also have you tried to power off the droplet and then start it again instead of just rebooting it? You can perform this action from the control panel.

      Let me know how it goes.

      Regards,
      Alex

      • Hey Alex,

        The solution doesn’t work for me.
        eth0 appears to be properly configured and the files you told me to create are there - however the network still appears to be unavailable.
        I think I accidentally uninstalled some packets yesterday (I was troubleshooting ssl certificate problems) but dont know what to do now as I dont know where the problem is coming from
        Any ideas?
        Regards,
        Jan

      • Okay it seems that some packages responsible for networking are not there.
        You cannot install any packages without access to the network
        Any way short of recreating the droplet (a loooong time to do that - i dont have a backup)to solve this bs?

        • Hey, @JanWithVan

          What happens if you try to install the removed packages? Are you simply getting some “network unreachable” errors or similar? Which are the missing packages?

          If you have a snapshot of your droplet you can use it to restore the droplet from it. The other way will be to spin a new droplet and start from scratch if you don’t have backups.

          Regards,
          Alex

Submit an Answer