Multiple errors (IPv6 and simply error)
rodolfo-viana opened this issue · 11 comments
(Before posting this issue I read through closed and open issues to check if any reply would help me. No answer was helpful.)
I have been using ProtonVPN command-line tool for Linux for some weeks with no problem, but a couple of days ago I failed to connect. Since then I have been getting either
[!] Error connecting to VPN.
[!] There are issues in managing IPv6 in the system. Please test the system for the root cause.
Not being able to manage IPv6 by protonvpn-cli may leak the system's IPv6 address.
or the generic line
[!] Error connecting to VPN.
I checked IPv6 and it seems fine. I uninstalled and reinstalled ProtonVPN and the issue persists. I get this error when I choose Y and when I choose N when asked to decrease privilege...
So I am not sure what is going on. Can you guys help me please?
Here is my ifconfig output:
enp2s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 3c:2c:30:bc:52:65 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Loopback Local)
RX packets 3608 bytes 304173 (304.1 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3608 bytes 304173 (304.1 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlo1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.18 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 2804:14c:108:9992:49a6:d9da:9274:97c4 prefixlen 64 scopeid 0x0<global>
inet6 2804:14c:108:9992:6c6f:7f61:6109:5f83 prefixlen 64 scopeid 0x0<global>
ether 1c:1b:b5:99:3c:1b txqueuelen 1000 (Ethernet)
RX packets 40871 bytes 38623106 (38.6 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 27299 bytes 4910881 (4.9 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
And here is a connection log file:
connection_logs.txt
Please, post the output of apt list resolvconf and cat /etc/resolv.conf
Hi @xilopaint.
apt list -a resolvconf (a because it seems there is one additional version) returns:
Listing... Done
resolvconf/bionic-updates,bionic-updates,now 1.79ubuntu10.18.04.3 all [installed]
resolvconf/bionic,bionic 1.79ubuntu10 all
cat /etc/resolv.conf returns:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
search spo.virtua.com.br
Is this info helpful?
There's a weird info in your logs:
resolvconf: Error: Command not recognized
Usage: resolvconf (-d IFACE|-a IFACE|-u|--enable-updates|--disable-updates|--updates-are-enabled)
It sounds like a problem with DNS management. But I have the same resolvconf version and it works fine for me. Have you tried to connect with openvpn directly using the config files?
I just wrote a line in my .bashrc to connect when I ran my terminal. Something like echo "protonvpn-cli -c". And it would ask for my password, show the screen to select the server etc. It worked for some time and then suddenly just stopped working.
And nothing else.
I'm asking if you already tried to connect with a config file:
sudo openvpn <config_file.ovpn>
No, I did not. I just followed through this guide.
Please, download a config file and try sudo openvpn config <config_file.ovpn>
EDIT: Sorry, the right command is sudo openvpn <config_file.ovpn>
You can find a guide in the Option B on this page.
Hey @rodolfo-viana, have you tried the command in the above post?
I did try but got no successful response. So I decided to start activating it via Network Manager.
I did try but got no successful response. So I decided to start activating it via Network Manager.
It turns out I might have found the root cause of your issue. Your DNS resolver is systemd-resolved and your system might be lacking /sbin/resolvconf what prevents /etc/resolv.conf from being updated by /etc/openvpn/update-resolv-conf. That's explained here.
You can confirm this by running cat /sbin/resolvconf. If the file does not exist that's your problem. Is your system by any chance Ubuntu 18.04?
@rodolfo-viana could you close the issue if no longer interested in debugging it?