Trouble Connecting to NL France and others servers on port 443

[Solex1 2]

hello All,

Are any of you having trouble connecting to port 443?

53 works good, have not tried 80 yet.

Many thanks in advance,

      Solex1

[rainmakerraw 94]

Yes. See this thread. At first it seemed to be Google DNS issues but I'm on OpenDNS and now having problems again. I am also connecting over port 443 (UDP) and I was just disconnected and can't reconnect. The logs always say TLS negotiation/authentication failed after 60 seconds inactivity (no response received).

 

It seems maybe something bigger is going on.

 

Edit for logs showing an .ovpn for all NL servers (made in Air's config generator) connecting over 443 UDP timing out:

 

2014-06-03 01:54:22 *Tunnelblick: openvpnstart starting OpenVPN
2014-06-03 01:55:22 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
2014-06-03 01:55:22 TLS Error: TLS handshake failed
2014-06-03 01:55:22 SIGUSR1[soft,tls-error] received, process restarting
2014-06-03 01:55:22 MANAGEMENT: >STATE:1401756922,RECONNECTING,tls-error,,
2014-06-03 01:55:22 MANAGEMENT: CMD 'hold release'
2014-06-03 01:55:22 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2014-06-03 01:55:22 Socket Buffers: R=[196724->65536] S=[9216->65536]
2014-06-03 01:55:22 MANAGEMENT: >STATE:1401756922,RESOLVE,,,
2014-06-03 01:55:22 UDPv4 link local: [undef]
2014-06-03 01:55:22 UDPv4 link remote: [AF_INET]62.212.72.175:443
2014-06-03 01:55:22 MANAGEMENT: >STATE:1401756922,WAIT,,,
2014-06-03 01:55:42 *Tunnelblick: Disconnecting; notification window disconnect button pressed
2014-06-03 01:55:42 *Tunnelblick: Disconnecting using 'kill'
2014-06-03 01:55:42 event_wait : Interrupted system call (code=4)
2014-06-03 01:55:42 SIGTERM received, sending exit notification to peer
2014-06-03 01:55:47 *Tunnelblick: No 'post-disconnect.sh' script to execute
2014-06-03 01:55:47 *Tunnelblick: Expected disconnection occurred.
2014-06-03 01:55:47 SIGTERM[soft,exit-with-notification] received, process exiting
2014-06-03 01:55:47 MANAGEMENT: >STATE:1401756947,EXITING,exit-with-notification,,

Edited ... by rainmakerraw

[rainmakerraw 94]

I can confirm that port 80 works OK (NL servers over UDP) where port 443 is currently timing out. Tested on a MacBook Pro using the latest Tunnelblick beta and the latest openvpn v4.3.2.

[Staff 10019]

I can confirm that port 80 works OK (NL servers over UDP) where port 443 is currently timing out. Tested on a MacBook Pro using the latest Tunnelblick beta and the latest openvpn v4.3.2.

 

Hi,

 

this is some other problem, it's not related to DNS: from your logs the resolution is correct. At the moment we can only confirm you that there are no problems at all to connect to port 443, in UDP, to the NL servers (including Grafias, whose entry-IP is showed in your logs). Might it be a block by your ISP or by some system firewall to port 443 UDP?

 

Kind regards

[rainmakerraw 94]

 

I can confirm that port 80 works OK (NL servers over UDP) where port 443 is currently timing out. Tested on a MacBook Pro using the latest Tunnelblick beta and the latest openvpn v4.3.2.

 

Hi,

 

this is some other problem, it's not related to DNS: from your logs the resolution is correct. At the moment we can only confirm you that there are no problems at all to connect to port 443, in UDP, to the NL servers (including Grafias, whose entry-IP is showed in your logs). Might it be a block by your ISP or by some system firewall to port 443 UDP?

 

Kind regards

 

It isn't a firewall issue as the problem is replicated across two devices running Linux and Mac OS X Mavericks respectively. I can connect sometimes and not at other times (it just disconnects then refuses to reconnect for a while). Also two other users are suggesting the exact same issue today, so it's not just me.

 

I find it highly unlikely Virgin Media would be blocking access to some AirVPN servers, only some times. Plus I have now experienced a disconnection and failure to reconnect over port 80 also. Strange.

 

EDIT: I have now managed to reconnect to NL over port 443 UDP. It would seem that an ISP block is very unlikely. Remember I didn't start this thread, I only replied to it. Currently the top two threads listed in the applet at the side of the forum are both about this issue, from two other different users.

Edited ... by rainmakerraw

[Staff 10019]

 

 

I can confirm that port 80 works OK (NL servers over UDP) where port 443 is currently timing out. Tested on a MacBook Pro using the latest Tunnelblick beta and the latest openvpn v4.3.2.

 

Hi,

 

this is some other problem, it's not related to DNS: from your logs the resolution is correct. At the moment we can only confirm you that there are no problems at all to connect to port 443, in UDP, to the NL servers (including Grafias, whose entry-IP is showed in your logs). Might it be a block by your ISP or by some system firewall to port 443 UDP?

 

Kind regards

 

It isn't a firewall issue as the problem is replicated across two devices running Linux and Mac OS X Mavericks respectively. I can connect sometimes and not at other times (it just disconnects then refuses to reconnect for a while). Also two other users are suggesting the exact same issue today, so it's not just me.

 

I find it highly unlikely Virgin Media would be blocking access to some AirVPN servers, only some times. Plus I have now experienced a disconnection and failure to reconnect over port 80 also. Strange.

 

EDIT: I have now managed to reconnect to NL over port 443 UDP. It would seem that an ISP block is very unlikely. Remember I didn't start this thread, I only replied to it. Currently the top two threads listed in the applet at the side of the forum are both about this issue, from two other different users.

 

Hello!

 

There are around 800 clients currently connected to port 443 UDP of some NL server, globally. We have performed connections to 443 UDP from different ISPs (from Italy) to all the NL servers. No problem on our side has been detected. Maybe it's just a routing problem or some other problem between Virgin and Leaseweb (and optionally from the Solex1's ISP). Hopefully momentary. It must be said that this problem may overlap with the DNS issue. They might be two different problems that sometimes overlap, giving the feeling of erratic behavior.

 

Kind regards

[rainmakerraw 94]

OK so I just got disconnected again after 15 mins 44 seconds, and I can't reconnect because the domain can't resolve. It's a weird issue, I agree. Although the log says inactivity timeout, the connection was active the whole time (downloading a torrent). Here is the log again from tunnelblick:

 

2014-06-03 03:14:12 *Tunnelblick: This computer's apparent public IP address changed from xx.xx.xxx.xxx before connection to 37.48.81.42 after connection
2014-06-03 03:28:31 *Tunnelblick: No 'reconnecting.sh' script to execute
2014-06-03 03:28:31 [server] Inactivity timeout (--ping-restart), restarting
2014-06-03 03:28:31 SIGUSR1[soft,ping-restart] received, process restarting
2014-06-03 03:28:31 MANAGEMENT: >STATE:1401762511,RECONNECTING,ping-restart,,
2014-06-03 03:28:31 MANAGEMENT: CMD 'hold release'
2014-06-03 03:28:31 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2014-06-03 03:28:31 Socket Buffers: R=[196724->65536] S=[9216->65536]
2014-06-03 03:28:31 MANAGEMENT: >STATE:1401762511,RESOLVE,,,
2014-06-03 03:29:01 RESOLVE: Cannot resolve host address: nl.vpn.airdns.org: nodename nor servname provided, or not known
2014-06-03 03:29:01 MANAGEMENT: >STATE:1401762541,RESOLVE,,,
2014-06-03 03:29:31 RESOLVE: Cannot resolve host address: nl.vpn.airdns.org: nodename nor servname provided, or not known

[Solex1 2]

Hello All,

Strange, but i thought you all should know. Its not my isp. Im finding it has to do copyrights some country have and enforce them and other counties don't. Not sure so i will stop rambling.

Many thanks in advance again,

       Solex1

[Solex1 2]

Thanks for you input rainmakerraw and Staff.

Regards.

       Solex1