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
Trying to install Ajenti admin Question Question
Proftpd Error 530 on ubuntu: Incorrect login Question Question

Question

Network not working after taking droplet snapshot

Posted July 15, 2020 1.7k views
UbuntuLAMP Stack

Hello DigitalOcean,

I have an issue with my droplet. It is currently using Ubuntu 18.10 and I wanted to update to Ubuntu 18.04 LTS, so I decided to shut it down and take a snapshot. When I took the snapshot, I booted the droplet, but unfortunately after restarting. I can’t log in with SSH Key. Apache is running but I can’t access the IP via the browser too (it results in connection timed out). It shows on the droplet status that it is running but the web page is not working.
I decided to restore the snapshot to the droplet but it won’t work.

Please help me find out what is going wrong, my website is off since soon 48hours, I contacted DO still no response.

Thanks,
Franz

Add a comment
rigledev
By:
rigledev

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
Trying to install Ajenti admin Question Question
Proftpd Error 530 on ubuntu: Incorrect login Question Question
Add a comment
1 comment
  • ahzudirect July 30, 2020
    Reply Report

    I had the same problem. I am running Azuracast in Docker and I have a few radio stations. After taking a snapshot of the server, I could not visit the admin panel after reboot. I would like to no more about this issue to avoid making this mistake in the future.

    When attempting to connect to the web interface I get (The site cannot be reached) and I am a beginner with Docker commands and snapshots. I fix the issue I am attempting the to roll back to a 10-day old backup and hopefully, it will restore the server. If anyone knows what else I can do please give me some feedback. Thanks

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
3 answers
rigledev July 16, 2020

After 3 days of struggle, I finally solved it.
It is similar to this issue https://www.digitalocean.com/community/questions/no-internet-connection-after-droplet-reboot from @lukasea17033bb7e7ecf80fc21

Thanks,
Franz

Reply Report
KFSys July 16, 2020

Hi @rigledev,

You can use your droplet’s console. The console can be found in your Control Panel –> Droplet’s settings —> Access –> Launch Console.

From there you can try typing in 

service network restart

To see if it would start if it would give you an error.

Once you have the error, you should be able to resolve it with a quick search. If the error is not something you have access to fix, it would be best to see the response of DigitalOcean’s support. Having said that, please do try to restart your network from your console.

Regards,
KFSys

Reply Report
  • rigledev July 16, 2020

    Hello @KFSys, thanks for the reply.

    Yesterday, I managed to update my droplet from Ubuntu 18.10 -> Ubuntu 18.04 LTS. I used the rescue mode -> chroot into the system.

    When I boot my droplet with the hard disk I have no network, but in rescue mode, it works fine.

    When I tried 

    service network restart

    It fails and throws 

    Failed to restart network.service: Unit network service not found

    If I try to ping google I get

    ping:google.com: Temporary failure in name resolution

    Thanks,
    Franz

    Reply Report
  • rigledev July 16, 2020

    Hello @KFSys,

    I suspect there is an issue with my /etc/resolv.conf

    If I run this in my normal Hard disk boot

    cat /etc/resolv.conf

    I get

    cat: /etc/resolv.conf: No such file or directory

    If I run it when booting from Recovery ISO

    cat /etc/resolv.conf

    I get

    # cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "systemd-resolve --status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53

    Thanks & Best regards,
    Franz

    Reply Report
    • KFSys July 20, 2020

      Hi @rigledev,

      In your resolv.conf you need to at least have

      nameserver 127.0.0.53

      Just like you have one in your rescue mode. Try placing it on your normal Hard disk boot.

      Unfortunately, updates from one Ubuntu OS version to another almost every time cause such errors. I’m afraid there might be other issues caused by this upgrade.

      Regards,
      KFSys

      Reply Report
      • rigledev July 20, 2020

        Hello @KFSys,

        Thanks for the reply, I successfully managed to make it work again, my cloud-init was incomplete.

        I finally decided to take a snapshot of the droplet then create a new one. The new droplet was created with a Lamp Stack Image from scratch, as I wanted to upgrade it. I manually installed and moved the data that I had in the previous one and I deleted it.

        Thanks,

        Best regards,
        Franz

        Reply Report
  • NearlyNormal January 5, 2021

    On Fedora 33, issuing service network restart shows me: 

    Failed to restart network.service: Unit network.service not found
    Reply Report
NearlyNormal January 5, 2021

Same issue on Fedora 33. While taking snapshot, this happened.

My /etc/resolv.conf: 

nameserver 127.0.0.53
options edns0 trust-ad
nameserver 8.8.8.8
nameserver 8.8.4.4

What’s the solution for this? Rebooting the droplet doesn’t help.

Reply Report

Related

Looking for something else?

Ask a new question Search for more help