Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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.
I just had a rather enlightened colleague of mine solve this for me. Running $ifconfig or $ip addr, he saw how inet6 can be found but not inet (IPv4). On a hunch he opened network interfaces and commented out all IPv6 related lines as follows:
$ sudo nano /etc/network/interfaces
# This file describes the network interfaces available on your
# system and how to activate them. For more information, see
# interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
#iface eth0 inet6 static
# address ****:****:****:****:****:****:****:****
# netmask 64
# gateway ****:****:****:****:****:****:****:****
# autoconf 0
# dns-nameservers ****:****:****::**** ****:****:****::8888 8.8.8.8
iface eth0 inet static
address ***.***.***.**
netmask ***.***.***.*
gateway ***.***.***.*
up ip addr add 10.20.0.5/16 dev eth0
Running ifconfig we can now see there are now two inet6 and one inet. I don’t claim to know what happened here, but this new inet now allows me to ping my droplet! Websites are now up, and I can ssh into the droplet to backup as needed.
eth0 Link encap:Ethernet HWaddr 04:01:35:48:9e:01
inet addr:***.***.***.* Bcast:***.***.***.*** Mask::***.***.***.***
inet6 addr: ****:****:***:**::***:****/64 Scope:Global
inet6 addr: ****::***:****:****:****/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:44118 errors:0 dropped:0 overruns:0 frame:0
TX packets:51888 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:9519589 (9.5 MB) TX bytes:156384397 (156.3 MB)
This was a little scary for a while there! Happy to at least have this to work from.
Hello there,
It is important to backup your droplet by taking snapshot or create a copy of the system files before going for a system update/upgrade. It seems like somehow the IPv6 configuration was affected and thus caused the issue for you.
You can always examine the default network interface for any syntax errors or misconfigurations.
We also have an article on how to diagnose issues with the network configuration.
https://docs.digitalocean.com/support/check-your-droplets-network-configuration/
Regards