TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)

Got a problem with Viscosity or need help? Ask here!

davo124

Posts: 2
Joined: Sat Jan 18, 2020 2:59 pm

Post by davo124 » Sat Jan 18, 2020 3:14 pm
Hi,

The problem started when I upgraded my MacBook Pro to macOS 10.15.2. I was running Viscosity 1.8.3, and the problem persists on 1.8.4.

I get the TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity).
I have 2 other computers, and iMac and my wife's MacBookPro, both running macOS 10.15.1. All 3 of my computers have identical config files. The 2 computers running the older version of macOS have no trouble connecting.
(I have literally sat at my iMac with my MacBook Pro next to it, the iMac connects, the MacBook Pro never will.)

Below is a copy of the connection log. I need to be able to connect when travelling. Any ideas on how to correct the issue?

Thanks,

David

log file (IP details hidden):
2020-01-18 15:01:32: Viscosity Mac 1.8.4 (1528)
2020-01-18 15:01:32: Viscosity OpenVPN Engine Started
2020-01-18 15:01:32: Running on macOS 10.15.2
2020-01-18 15:01:32: ---------
2020-01-18 15:01:32: State changed to Connecting
2020-01-18 15:01:32: Checking reachability status of connection...
2020-01-18 15:01:32: Connection is reachable. Starting connection attempt.
2020-01-18 15:01:32: OpenVPN 2.4.8 x86_64-apple-darwin [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [MH/RECVDA] [AEAD] built on Dec 21 2019
2020-01-18 15:01:32: library versions: OpenSSL 1.1.1d 10 Sep 2019, LZO 2.10
2020-01-18 15:01:33: Valid endpoint found: IP details hidden:1194:udp
2020-01-18 15:01:33: TCP/UDP: Preserving recently used remote address: [AF_INET]IP details hidden:1194
2020-01-18 15:01:33: UDP link local (bound): [AF_INET][undef]:0
2020-01-18 15:01:33: UDP link remote: [AF_INET]IP details hidden:1194
2020-01-18 15:01:33: State changed to Authenticating
2020-01-18 15:01:33: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2020-01-18 15:02:33: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
2020-01-18 15:02:33: TLS Error: TLS handshake failed
2020-01-18 15:02:33: SIGTERM[soft,tls-error] received, process exiting
2020-01-18 15:02:33: State changed to Disconnected

James

User avatar
Posts: 1985
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Mon Jan 20, 2020 6:34 pm
Hi David,

Thanks for posting your log. The relevant item here is:
Code: Select all
2020-01-18 15:02:33: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)

This indicates that OpenVPN isn’t able to connect to the remote VPN server at all. No connection is ever established. It likely means your connection details are out of date (for example the connection address or port number may have changed), however it could also mean something is blocking your connection (such as firewall or other software on your computer, router, etc.).

As you have connections working on other computers I recommend exporting one of these connections from Viscosity (select the connection in the Preferences window, click on the cog, and then select one of the export options). You can then import this connection on MacBook Pro and see if you're able to connect.

If you're still unable to connect, then it's going to be some on that computer, or its network connection, that is blocking your connection attempt.

More information can be found in the following KB article:
https://www.sparklabs.com/support/kb/ar ... 0-seconds/

Cheers,
James
James Bekkema
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

davo124

Posts: 2
Joined: Sat Jan 18, 2020 2:59 pm

Post by davo124 » Mon Jan 20, 2020 9:56 pm
Thanks James.

I went through that page that you linked before I reported my issue.

In fact, the MacBook Pro was the original connection, I set up the other computers from its config file.

The only difference in set-up of my 3 computers is the macOS version number.

So, that leaves:
1. An issue on my MacBook Pro (no idea what got corrupted, even a fresh install of Viscosity did not help); or
2. A problem with macOS 10.15.2 (the problem started with the .2 update). Anyone else reported a problem with macOS 10.15.2 (or is it just me?)

Cheers,

David
3 posts Page 1 of 1