Can you run a route trace to an external address and post the output? That should give both you and anyone looking at this a little more idea of where the error lies.
traceroute -4 $remote sitename$
Once you’ve done this, netstat should give you further information on what’s happening.
arp -a
? (10.0.0.1) at on eth0
? (192.168.0.54) at 00:17:88:22:03:01 [ether] on eth0
? (192.168.0.57) at 00:f7:6f:d9:11:8c [ether] on eth0
? (192.168.0.55) at 9c:3d:cf:f8:42:7e [ether] on eth0
? (192.168.0.68) at f0:db:f8:c3:bf:5a [ether] on eth0
? (192.168.0.62) at 00:04:20:f8:4e:2f [ether] on eth0
? (192.168.0.69) at 08:66:98:c1:35:7d [ether] on eth0
? (192.168.0.1) at 1c:5f:2b:ca:4a:2c [ether] on eth0
? (192.168.0.52) at 9c:3d:cf:f8:5c:c8 [ether] on eth0
? (192.168.0.172) at 70:ee:50:00:b1:ea [ether] on eth0
? (192.168.0.50) at c8:ff:77:d4:ef:cd [ether] on eth0
? (192.168.0.53) at 70:70:0d:7c:c7:12 [ether] on eth0
odroid@odroid:~$ ping google.fr
PING google.fr (209.85.202.94) 56(84) bytes of data.
From 192.168.0.61 icmp_seq=1 Destination Host Unreachable
From 192.168.0.61 icmp_seq=2 Destination Host Unreachable
From 192.168.0.61 icmp_seq=3 Destination Host Unreachable
From 192.168.0.61 icmp_seq=4 Destination Host Unreachable
From 192.168.0.61 icmp_seq=5 Destination Host Unreachable
sudo apt-get -o Dpkg::Options::="--force-confmiss" install --reinstall procps
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 6 not upgraded.
Need to get 208 kB of archives.
After this operation, 0 B of additional disk space will be used.
Err:1 Index of /ubuntu-ports xenial-updates/main armhf procps armhf 2:3.3.10-4ubuntu2.3
Cannot initiate the connection to ports.ubuntu.com:80 (2001:67c:1360:8001::22). - connect (101: Network is unreachable) [IP: 2001:67c:1360:8001::22 80]
E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/pool/main/p/procps/procps_3.3.10-4ubuntu2.3_armhf.deb Cannot initiate the connection to ports.ubuntu.com:80 (2001:67c:1360:8001::22). - connect (101: Network is unreachable) [IP: 2001:67c:1360:8001::22 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Looking at that output, you at least have dns functional, so it’s resolving external addresses, but it can’t reach them.
I don’t have enough experience with VPNs to weigh in on that front, given you mentioned it was working and then failed, I would next look at any services that are running as part of that VPN and whether restarting them restores access. If it does, review whether there are specific ports opened as part of that vpn that aren’t active when the service has stopped. Sorry I can’t offer any more.
That would make sense. If there is specific documentation on your VPN provider’s site related to configuration for Linux, it would be worth pursuing. Journalctl may hold some clues!