Hi guys. First of all thank you in advance for any help.
Since 3 days ago, I am unable to access any of my instances except through ssh. I have 4 VM.Standard.A1.Flex of 1CPU/6GB instances in my account and I found all crashed on 20/02 morning. On each of them I have some Docker containers which are all working, and also from inside to outside, each instance has connectivity. I've searched a lot, done a lot of tests this days, even asked ChatGPT… :-D but none of this give to me any clue of what is happening.
Here are some tests:
ubuntu@instance-3:~$ ping -c 4 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=121 time=0.726 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=121 time=0.746 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=121 time=0.736 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=121 time=0.733 ms
ubuntu@instance-3:~$ nslookup google.com
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: google.com
Address: 142.250.184.174
Name: google.com
Address: 2a00:1450:4003:80c::200e
ubuntu@instance-3:~$ dig google.com
; <<>> DiG 9.18.30-0ubuntu0.24.04.2-Ubuntu <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60972
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 89 IN A 142.250.184.174
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Sat Feb 22 22:27:49 CET 2025
;; MSG SIZE rcvd: 55
ubuntu@instance-3:~$ systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
Active: active (running) since Sat 2025-02-22 20:53:58 CET; 1h 34min ago
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Main PID: 697 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 7005)
Memory: 6.3M (peak: 6.6M)
CPU: 227ms
CGroup: /system.slice/systemd-resolved.service
└─697 /usr/lib/systemd/systemd-resolved
Feb 22 20:53:59 instance-3 systemd[1]: Starting systemd-resolved.service - Network Name Resolution...
Feb 22 20:53:59 instance-3 systemd-resolved[697]: Positive Trust Anchors:
Feb 22 20:53:59 instance-3 systemd-resolved[697]: . IN DS 2[…]6 8 2 e06[…]
Feb 22 20:53:59 instance-3 systemd-resolved[697]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.>
Feb 22 20:53:58 instance-3 systemd-resolved[697]: Using system hostname 'instance-3'.
Feb 22 20:53:58 instance-3 systemd[1]: Started systemd-resolved.service - Network Name Resolution.
130 ubuntu@instance-3:~$ ip route show
default via 10.0.1.1 dev enp0s6 proto dhcp src 10.0.1.64 metric 100
default via 10.0.1.1 dev enp0s6 proto dhcp src 10.0.1.64 metric 1002 mtu 9000
10.0.1.0/24 dev enp0s6 proto dhcp scope link src 10.0.1.64 metric 1002 mtu 9000
10.0.1.1 dev enp0s6 proto dhcp scope link src 10.0.1.64 metric 100
169.254.0.0/16 dev enp0s6 proto dhcp scope link src 10.0.1.64 metric 100
169.254.0.0/16 dev enp0s6 proto dhcp scope link src 10.0.1.64 metric 1002 mtu 9000
169.254.169.254 dev enp0s6 proto dhcp scope link src 10.0.1.64 metric 100
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
From inside all seems ok, however, none of them can be accessed from outside…
ubuntu@testing:~$ nc -zv 143.xx.xx.183 80
nc: connect to 143.xx.xx.183 port 80 (tcp) failed: No route to host
ubuntu@testing:~$ nc -zv 143.xx.xx.183 443
nc: connect to 143.xx.xx.183 port 443 (tcp) failed: No route to host
On this instance I've even deleted all containers and uninstalled Docker completely, delete Docker user/group, etc., updated the Ubuntu version to 24.04 (which worked without any struggle) and reinstalled Docker from scratch but nothing changed. Now I am completely stuck… ;-(
Can anyone enlighten me what can I do to solve the issue?