Jump to content
Not connected, Your IP: 18.218.184.214
Sign in to follow this  
majoriscannis

How to fix constant restart loop

Recommended Posts

Was wondering if anyone knew how to fix the constant restart loop. I try to log on to a server and it redirects and then restarts for 3 secs then goes to another server and restarts. Any assistance would be appreciated.

 

Share this post


Link to post

Was wondering if anyone knew how to fix the constant restart loop. I try to log on to a server and it redirects and then restarts for 3 secs then goes to another server and restarts.

What Operating system/platform are you using....if Windows 10 see below(links).

Share this post


Link to post

Got the same on Ubuntu 16.04.

It's actually for certain servers and not all of them, thankfully.

Something to do with ipv6 I guess because the loop is

Checking route ipv4 then immediately Checking route ipv6 and failing.

On other servers, it is NOT checking route ipv6 and seems to be fine with ipv4.

So cancel your connection attemp and try selecting another server in the list to see if it's the same.

Hope this help.

Share this post


Link to post

To be more precise, some servers are checking for ipv6 routes and others are not.

I just tried again, first on Chara (NL), which is checking route ipv6 after ipv4 and failing:

 

. 2018.07.07 10:19:28 - Unable to compute route for 2a00:1678:2470:14:8b1f:21a6:b646:bf3d: IPv6 VPN gateway not available.
. 2018.07.07 10:19:28 - Flushing DNS
I 2018.07.07 10:19:30 - Checking route IPv4
I 2018.07.07 10:19:30 - Checking route IPv6
. 2018.07.07 10:19:30 - curl: (7) Couldn't connect to server
. 2018.07.07 10:19:30 - Checking route (2° try)
. 2018.07.07 10:19:31 - curl: (7) Couldn't connect to server
. 2018.07.07 10:19:31 - Checking route (3° try)
. 2018.07.07 10:19:33 - curl: (7) Couldn't connect to server
E 2018.07.07 10:19:33 - Checking route IPv6 failed.
. 2018.07.07 10:19:33 - OpenVPN > Initialization Sequence Completed
! 2018.07.07 10:19:33 - Disconnecting
 

Then on Phaet (NL), which is not checking ipv6 after ipv4 and it's working.

Can you check the logs to see if you've got the same behaviour? And maybe try the Phaet server to see if it works.

If you do, maybe rename the topic to something like "checking route ipv6 not working".

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Security Check
    Play CAPTCHA Audio
    Refresh Image
Sign in to follow this  

×
×
  • Create New...