search

ProtonVPN / protonvpn-cli

Legacy protonvpn-cli: ProtonVPN Command-Line Tool for Linux and macOS. This has been superseded by https://github.com/ProtonVPN/protonvpn-cli-ng
Other
601 stars 96 forks source link

Two flavors of ipv6 error #77

Closed acwhite3 closed 6 years ago

acwhite3 commented 6 years ago

I've been using protonvpn on Linux Ubuntu 16.04 LTS successfully for sometime now including yesterday. After reboot today I am receiving the following two flavors of ipv6 error messages and am unable to connect:

[!] Error connecting to VPN. [!] There are issues in managing ipv6 in the system. Please test the system for the root cause. Not able to manage ipv6 by protonvpn-cli might cause issues in leaking the system’s ipv6 address.

And

Failed to query password: Timer expired Connecting... [!] Error connecting to VPN. [!] This is an error in enabling ipv6 on the machine. Please enable it manually.

Updated sysctl to reenable ipv6 but that doesn't solve the problem just returns a generic can't connect message.

acwhite3 commented 6 years ago

What is the process for reverting the changes?

mazen160 commented 6 years ago

Hi @acwhite3

If you're unable to connect with openvpn manually, then the problem appears to be from your VPN plan or machine.

Here is the previous version before April 21st: https://raw.githubusercontent.com/ProtonVPN/protonvpn-cli/bc5754b18bb3e8d030918ed66116b7ae4c451778/protonvpn-cli.sh

the latest update only introduced an update for shasum usage, nothing that should affect the VPN connection.

The mesage you show might indicate that some servers you choose might be unaccessible in the meantime, you can try other servers and it should work normally while the state of the unaccessible server is recovered.

xilopaint commented 6 years ago

Here is the previous version before April 21st: https://raw.githubusercontent.com/ProtonVPN/protonvpn-cli/bc5754b18bb3e8d030918ed66116b7ae4c451778/protonvpn-cli.sh

He asked for the version prior the last two commits.

xilopaint commented 6 years ago

@acwhite3 here is the version prior the last two commits:

https://raw.githubusercontent.com/ProtonVPN/protonvpn-cli/e27c42485ac495148df3dc1c5e349a3ffcdad49c/protonvpn-cli.sh

ace4dude commented 6 years ago

@xilopaint 

@acwhite3 here is the version prior the last two commits:

https://raw.githubusercontent.com/ProtonVPN/protonvpn-cli/e27c42485ac495148df3dc1c5e349a3ffcdad49c/protonvpn-cli.sh

Now this is the version that works!

alancwoo commented 6 years ago

Just a note from my end as I haven't used protonvpn for some time due to the connectivity issues, but just updated and it seems to be working now.

acwhite3 commented 6 years ago

Yes, things seem to have cleared up for me as well with the latest update. I was having intermittent problems with either the IPV6 problem or getting a connection but failing to resolve DNS. But, knock on wood, haven't had a connection problem of any sort since the last update.

Sent from ProtonMail, encrypted email based in Switzerland.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On May 8, 2018 3:14 AM, Alan Woo notifications@github.com wrote:

Just a note from my end as I haven't used protonvpn for some time due to the connectivity issues, but just updated and it seems to be working now.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

Rafficer commented 6 years ago

A user on reddit reported the same issue and said it got fixed by installing the openresolv package.

https://www.reddit.com/r/protonvpn/comments/8i7nmn

@mazen160 Should the openresolv package be a requirement? Does it differ from the resolvconf package?

mazen160 commented 6 years ago

@Rafficer This is quite odd. openresolv seems to be a middleware for handling /etc/resolv.conf, where protonvpn-cli has its builtin handler.

I haven't tried BunsenLabs, but Debian should work totally fine with the current requirements.

Also the changes he did (openresolv) is not related to ipv6 behaviour, just the DNS leakage part.

In addition, there should not be connection errors caused by DNS configurations, as the connection verification and IP checking is done using the current system's DNS, (connecting to protonmail.ch). This is intentionally done to avoid any DNS mishandling part.

I would say the user just did something in the background he might not be aware of, it doesn't seem to be related to openresolv.

We can check the openvpn logs to confirm too if he share it.

lfiolhais commented 6 years ago

@Rafficer Can confirm that solution worked for me as well, was also having IPv6 errors. I'm using Debian 9.

mazen160 commented 6 years ago

@lfiolhais Great!

Rafficer commented 6 years ago

Why is that great? If I understood @lfiolhais correctly, installing openresolv solved the issue?

mazen160 commented 6 years ago

@Rafficer Oh I mis-read it. I thought that he said that the latest updates have fixed the issues for him.

mazen160 commented 6 years ago

The issue should be only related to the ipv6 errors then. I need to figure out why openresolv fixed the errors, since openresolv is managing dns, not related to the ipv6 part

acwhite3 commented 6 years ago

For me, the latest fix solved the problems I was having with both IPV6 and the DNS lookup issue.

Sent from ProtonMail, encrypted email based in Switzerland.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On May 12, 2018 5:09 PM, Mazin Ahmed notifications@github.com wrote:

@Rafficer Oh I mis-read it. I thought that he said that the latest updates have fixed the issues for him.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

lfiolhais commented 6 years ago

@mazen160 @Rafficer Just to clear things up and confirm. Installing openresolv fixed the IPv6 errors I was having.

ghost commented 6 years ago

Me too. Now it works beautifully and really fast. Even my DNS leak tests are so much faster now.

Ubuntu 18.04 LTS

mazen160 commented 6 years ago

@msjenkins1 Is it because of the latest updates, or the openresolv package?

ghost commented 6 years ago

@mazen160 edit It was not related to the openresolv package for me. I was experiencing a seemingly separate issue.

xilopaint commented 6 years ago

@msjenkins1 do you have a free or paid account?

ghost commented 6 years ago

@xilopaint It's a paid account. Basic, Tier 2 in the --init. I've tried creating the logs and looking through them to no avail. I just tried connecting to VA-101, which --status says Internet: Offline, yet connected to a server in Canada and everything just worked perfectly.

marlid91 commented 6 years ago

I get this error message on Ubuntu 18.04 running the latest CLI:

Connecting... [!] 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 might cause issues in leaking the system's IPv6 address.

After enough tries (maybe it will work on the first try, maybe the third) it will connect without any error messages.

ghost commented 6 years ago

I've tracked down at the very least a determining factor for the issue I was having. It depends somehow on which server I connect to. If I connect to any of the servers with names like "US-VA#1" it works beautifully, however if I connect to the servers with three digits, like "US-VA#101", pvpn --status shows internet as offline, traceroute takes forever and webpages don't load, but I can still ping outside servers. I don't know what this means, but it seems to work with or without IPv6 enabled in /etc/sysctl.conf, so this may not even be the right thread for me...

xilopaint commented 6 years ago

@msjenkins1 you're probably running into #73.

xilopaint commented 6 years ago

Is there any reason to keep this issue open? I think IPv6 management is running ok on both Linux and macOS platforms.

ghost commented 6 years ago

I've ran into no reoccurring issues, myself.

On Sat, Aug 25, 2018, 22:25 Arthur Pinheiro notifications@github.com wrote:

Is there any reason to keep this issue open? I think IPv6 management is running ok on both Linux and macOS platforms.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ProtonVPN/protonvpn-cli/issues/77#issuecomment-416009198, or mute the thread https://github.com/notifications/unsubscribe-auth/AOawu4THGfpXWBvKMksuSzGE2AW5f5-Oks5uUgctgaJpZM4TIjSe .

mazen160 commented 6 years ago

I believe this should be fixed by now. Thank you everyone for working on this issue. It was very intresting bug to fix on popular platforms.

Awesome work :)

Best regards, Mazin

djnotes commented 5 years ago

@oonimooni could you try sudo pvpn -c ES#1 and tell me if it works for you?

I get the following, what does it mean?

[!] Error: OpenVPN is already running on this machine.
djnotes commented 5 years ago

I am having the same issue on Fedora 30. 

[!] 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.
xilopaint commented 5 years ago

@oonimooni could you try sudo pvpn -c ES#1 and tell me if it works for you?

I get the following, what does it mean?

[!] Error: OpenVPN is already running on this machine.

It means you already had a running OpenVPN process when tried to connect to ProtonVPN using protonvpn-cli. Are you sure you were not already connected to a VPN?

xilopaint commented 5 years ago

I am having the same issue on Fedora 30.

[!] 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.

Please, provide logs: PROTONVPN_CLI_LOG=true protonvpn-cli -f

djnotes commented 5 years ago

Yes, @xilopaint . I am not connected to a VPN. By the way, I have heard that OpenVPN traffic is easily detectable by ISPs. So, given the unsuccessful experience I have had so far with different OpenVPN connections so far (including ProtonVPN) on Linux, is there any alternative way to connect to ProtonVPN servers without using OpenVPN?

You might know Gnome supports a couple of different VPN setups: openconnect (Cisco AnyConnect) PPTP SSH vpnc

djnotes commented 5 years ago

@xilopaint Here's my log:
https://paste.ofcode.org/KG8epz5ZxGDn6NCYPnUkfi

djnotes commented 5 years ago

One more thing. I just found that if I connect to another VPN and then try connecting with proton-vpn-cli with the previous setup, then it does connect successfully. So, this, I think, increases the odds of ProtonVPN's DNS already blocked by my ISP, doesn't it?

xilopaint commented 5 years ago

I have heard that OpenVPN traffic is easily detectable by ISPs.

Your ISP can only detect you're connected to a ProtonVPN server but cannot see the data since it's encrypted. It's not an OpenVPN's problem.

Btw, I'm not sure you get my point. That error suggests protonvpn-cli didn't work for you because you had an openvpn process running. Are you still getting that error?

What's your output for ps cax | grep openvpn?

djnotes commented 5 years ago

@xilopaint openvpn was running but I was not connected. So I killed openvpn with kill -9 $(pgrep openvpn) and ran protonvpn-cli again. That openvpn already running error is gone. I can only connect to the first free server (JP) which I tried, when I am connected to another VPN (via openconnect). So, in case the ProtonVPN DNSes get blocked in ISP, is there a way to go around it?

xilopaint commented 5 years ago

Please, now you killed openvpn run PROTONVPN_CLI_LOG=true protonvpn-cli -f and provide the log.

djnotes commented 5 years ago

What I see in logs is mostly like the follows (So, not an IPv6 issue) which is identified sometimes as so probably by mistake: 

us=955292 RESOLVE: Cannot resolve host address: nl-free-02.protonvpn.com:1194 (Name or service not known)

That's weird. Why can't I resolve any of these domains? (tried nslookup nl-free-02.protonvpn.com which returns SERVFAIL)

xilopaint commented 5 years ago

Are you sure you don't have firewall restrictions?

Take a look into this: https://bobcares.com/blog/cannot-resolve-host-address-openvpn/

djnotes commented 5 years ago

Just turned off firewalld and tried again PROTONVPN_CLI_LOG=true protonvpn-cli -f.Got the same result. Here's the log:

https://paste.ofcode.org/3bqERXG9avhDvXTwZnhv7J4

xilopaint commented 5 years ago

Do you use the DNS servers of your ISP? If so, could you try to change them to some public DNS servers and try again?

Also, run nslookup again with the new DNS servers.

djnotes commented 5 years ago

Changed to 8.8.8.8 8.8.8.44 9.9.9.9 149.112.112.112 1.1.1.1 1.0.0.1 64.6.64.6 64.6.65.6, and still getting SERVFAIL when trying to nslookup any of the domains :(

xilopaint commented 5 years ago

Have you already tried to connect to openvpn directly using a config file?

djnotes commented 5 years ago

@xilopaint I just tried the following (output included): 

# openvpn --config /root/.protonvpn-cli/protonvpn_openvpn_config.conf 
Wed Jun 12 14:39:55 2019 OpenVPN 2.4.7 x86_64-redhat-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 20 2019
Wed Jun 12 14:39:55 2019 library versions: OpenSSL 1.1.1c FIPS  28 May 2019, LZO 2.08
Enter Auth Username: AguHWgJi4_FaxpNKz2yZ7kXM
Enter Auth Password: ************************
Wed Jun 12 14:42:03 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Wed Jun 12 14:42:03 2019 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Wed Jun 12 14:42:03 2019 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Wed Jun 12 14:42:16 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]10.10.34.35:5060
Wed Jun 12 14:42:16 2019 Socket Buffers: R=[212992->212992] S=[212992->212992]
Wed Jun 12 14:42:16 2019 UDP link local: (not bound)
Wed Jun 12 14:42:16 2019 UDP link remote: [AF_INET]10.10.34.35:5060
Wed Jun 12 14:43:16 2019 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Wed Jun 12 14:43:16 2019 TLS Error: TLS handshake failed
Wed Jun 12 14:43:16 2019 SIGUSR1[soft,tls-error] received, process restarting
Wed Jun 12 14:43:16 2019 Restart pause, 5 second(s)
Wed Jun 12 14:43:21 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Wed Jun 12 14:43:21 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]10.10.34.35:5060
Wed Jun 12 14:43:21 2019 Socket Buffers: R=[212992->212992] S=[212992->212992]
Wed Jun 12 14:43:21 2019 UDP link local: (not bound)
Wed Jun 12 14:43:21 2019 UDP link remote: [AF_INET]10.10.34.35:5060

No idea why I have no success with OpenVPN on my machine.

djnotes commented 5 years ago

Again, if I connect with another means like openconnect and then retry openvpn --config /root/.protonvpn_cli/protonvpn_openvpn_config.conf, the connection is successful and I can confirm that my system has got a new IP address (that of the Protonvpn server) by checking ip info services online.

xilopaint commented 5 years ago

I didn't mean this file, but the config .ovpn files you can download via the dashboard.

There's a guide in the Option B of this page on how to connect with a config file by running sudo openvpn <config_file.ovpn>.

djnotes commented 5 years ago

That one failed too!

Details:

# openvpn jp-free-01.protonvpn.com.udp.ovpn 
Wed Jun 12 14:45:59 2019 OpenVPN 2.4.7 x86_64-redhat-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 20 2019
Wed Jun 12 14:45:59 2019 library versions: OpenSSL 1.1.1c FIPS  28 May 2019, LZO 2.08
Enter Auth Username: AguHWgJi4_FaxpNKz2yZ7kXM
Enter Auth Password: ************************
Wed Jun 12 14:46:16 2019 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Wed Jun 12 14:46:16 2019 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Wed Jun 12 14:46:28 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]10.10.34.35:4569
Wed Jun 12 14:46:28 2019 Socket Buffers: R=[212992->212992] S=[212992->212992]
Wed Jun 12 14:46:28 2019 UDP link local: (not bound)
Wed Jun 12 14:46:28 2019 UDP link remote: [AF_INET]10.10.34.35:4569
Wed Jun 12 14:47:28 2019 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Wed Jun 12 14:47:28 2019 TLS Error: TLS handshake failed
Wed Jun 12 14:47:28 2019 SIGUSR1[soft,tls-error] received, process restarting
Wed Jun 12 14:47:28 2019 Restart pause, 5 second(s)
Wed Jun 12 14:47:33 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]10.10.34.35:4569
Wed Jun 12 14:47:33 2019 Socket Buffers: R=[212992->212992] S=[212992->212992]
Wed Jun 12 14:47:33 2019 UDP link local: (not bound)
Wed Jun 12 14:47:33 2019 UDP link remote: [AF_INET]10.10.34.35:4569
Wed Jun 12 14:48:33 2019 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Wed Jun 12 14:48:33 2019 TLS Error: TLS handshake failed
Wed Jun 12 14:48:33 2019 SIGUSR1[soft,tls-error] received, process restarting
Wed Jun 12 14:48:33 2019 Restart pause, 5 second(s)
Wed Jun 12 14:48:38 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]10.10.34.35:5060
Wed Jun 12 14:48:38 2019 Socket Buffers: R=[212992->212992] S=[212992->212992]
Wed Jun 12 14:48:38 2019 UDP link local: (not bound)
Wed Jun 12 14:48:38 2019 UDP link remote: [AF_INET]10.10.34.35:5060
xilopaint commented 5 years ago

Have you ever tried to connect your machine in another network?

djnotes commented 5 years ago

Yes, just connected to another wireless access point (from another ISP) and got this:

 openvpn jp-free-01.protonvpn.com.udp.ovpn 
Wed Jun 12 16:01:42 2019 OpenVPN 2.4.7 x86_64-redhat-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 20 2019
Wed Jun 12 16:01:42 2019 library versions: OpenSSL 1.1.1c FIPS  28 May 2019, LZO 2.08
Enter Auth Username: lguHWnJi4_FexpNKz2yZ7kRM
Enter Auth Password: ************************
Wed Jun 12 16:02:09 2019 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Wed Jun 12 16:02:09 2019 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Wed Jun 12 16:02:11 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:5060 (Name or service not known)
Wed Jun 12 16:02:11 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:5060 (Name or service not known)
Wed Jun 12 16:02:11 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:02:11 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:02:11 2019 Restart pause, 5 second(s)
Wed Jun 12 16:02:16 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:1194 (Name or service not known)
Wed Jun 12 16:02:16 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:1194 (Name or service not known)
Wed Jun 12 16:02:16 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:02:16 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:02:16 2019 Restart pause, 5 second(s)
Wed Jun 12 16:02:21 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:80 (Name or service not known)
Wed Jun 12 16:02:21 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:80 (Name or service not known)
Wed Jun 12 16:02:21 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:02:21 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:02:21 2019 Restart pause, 5 second(s)
Wed Jun 12 16:02:26 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:443 (Name or service not known)
Wed Jun 12 16:02:26 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:443 (Name or service not known)
Wed Jun 12 16:02:26 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:02:26 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:02:26 2019 Restart pause, 5 second(s)
Wed Jun 12 16:02:31 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:4569 (Name or service not known)
Wed Jun 12 16:02:31 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:4569 (Name or service not known)
Wed Jun 12 16:02:31 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:02:31 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:02:31 2019 Restart pause, 5 second(s)
Wed Jun 12 16:02:36 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:5060 (Name or service not known)
Wed Jun 12 16:02:36 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:5060 (Name or service not known)
Wed Jun 12 16:02:36 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:02:36 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:02:36 2019 Restart pause, 5 second(s)
Wed Jun 12 16:02:41 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:1194 (Name or service not known)
Wed Jun 12 16:02:41 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:1194 (Name or service not known)
Wed Jun 12 16:02:41 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:02:41 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:02:41 2019 Restart pause, 5 second(s)
Wed Jun 12 16:02:46 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:80 (Name or service not known)
Wed Jun 12 16:02:46 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:80 (Name or service not known)
Wed Jun 12 16:02:46 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:02:46 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:02:46 2019 Restart pause, 5 second(s)
Wed Jun 12 16:02:51 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:443 (Name or service not known)
Wed Jun 12 16:02:51 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:443 (Name or service not known)
Wed Jun 12 16:02:51 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:02:51 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:02:51 2019 Restart pause, 5 second(s)
Wed Jun 12 16:02:56 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:4569 (Name or service not known)
Wed Jun 12 16:02:56 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:4569 (Name or service not known)
Wed Jun 12 16:02:56 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:02:56 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:02:56 2019 Restart pause, 5 second(s)
Wed Jun 12 16:03:01 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:5060 (Name or service not known)
Wed Jun 12 16:03:01 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:5060 (Name or service not known)
Wed Jun 12 16:03:01 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:03:01 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:03:01 2019 Restart pause, 5 second(s)
Wed Jun 12 16:03:06 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:1194 (Name or service not known)
Wed Jun 12 16:03:06 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:1194 (Name or service not known)
Wed Jun 12 16:03:06 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:03:06 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:03:06 2019 Restart pause, 5 second(s)
Wed Jun 12 16:03:13 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:80 (Name or service not known)
Wed Jun 12 16:03:13 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:80 (Name or service not known)
Wed Jun 12 16:03:13 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:03:13 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:03:13 2019 Restart pause, 5 second(s)
Wed Jun 12 16:03:18 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:443 (Name or service not known)
Wed Jun 12 16:03:18 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:443 (Name or service not known)
Wed Jun 12 16:03:18 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:03:18 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:03:18 2019 Restart pause, 5 second(s)
Wed Jun 12 16:03:23 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:4569 (Name or service not known)
Wed Jun 12 16:03:23 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:4569 (Name or service not known)
Wed Jun 12 16:03:23 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:03:23 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:03:23 2019 Restart pause, 5 second(s)
Wed Jun 12 16:03:28 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:5060 (Name or service not known)
Wed Jun 12 16:03:28 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:5060 (Name or service not known)
Wed Jun 12 16:03:28 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:03:28 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:03:28 2019 Restart pause, 5 second(s)
Wed Jun 12 16:03:33 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:1194 (Name or service not known)
Wed Jun 12 16:03:33 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:1194 (Name or service not known)
Wed Jun 12 16:03:33 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:03:33 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:03:33 2019 Restart pause, 5 second(s)
Wed Jun 12 16:03:38 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:80 (Name or service not known)
Wed Jun 12 16:03:38 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:80 (Name or service not known)
Wed Jun 12 16:03:38 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:03:38 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:03:38 2019 Restart pause, 5 second(s)
Wed Jun 12 16:03:43 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:443 (Name or service not known)
Wed Jun 12 16:03:43 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:443 (Name or service not known)
Wed Jun 12 16:03:43 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:03:43 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:03:43 2019 Restart pause, 5 second(s)
Wed Jun 12 16:03:48 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:4569 (Name or service not known)
Wed Jun 12 16:03:48 2019 RESOLVE: Cannot resolve host address: jp-free-01.protonvpn.com:4569 (Name or service not known)
Wed Jun 12 16:03:48 2019 Could not determine IPv4/IPv6 protocol
Wed Jun 12 16:03:48 2019 SIGUSR1[soft,init_instance] received, process restarting
Wed Jun 12 16:03:48 2019 Restart pause, 5 second(s)
xilopaint commented 5 years ago

What's your output for cat /etc/resolv.conf?