Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    OpenVPN TLS Key Negotiation Failed after 4.2.1 update

    Scheduled Pinned Locked Moved OpenVPN
    2 Posts 2 Posters 1.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K Offline
      kblack
      last edited by

      Hey after updating to 4.2.1 last night im getting the error message below. I've tried removing the current OpenVPN server, adding a Server using the wizard and exporting out a new client but with the same error. i replaced my Wan ip address with (WAN) below in case you suggest that that is the issue.

      Has anyone else had the same issue and if you have what was your fix.

      ill be restoring to 2.3.5 this evening :-( .

      Tue Oct 31 08:58:22 2017 UDPv4 link remote: AF_INET:1194
      Tue Oct 31 08:59:22 2017 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
      Tue Oct 31 08:59:22 2017 TLS Error: TLS handshake failed
      Tue Oct 31 08:59:22 2017 SIGUSR1[soft,tls-error] received, process restarting
      Tue Oct 31 08:59:24 2017 UDPv4 link local (bound): [undef]
      Tue Oct 31 08:59:24 2017 UDPv4 link remote: AF_INET:1194
      Tue Oct 31 09:00:24 2017 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
      Tue Oct 31 09:00:24 2017 TLS Error: TLS handshake failed
      Tue Oct 31 09:00:24 2017 SIGUSR1[soft,tls-error] received, process restarting
      Tue Oct 31 09:00:26 2017 UDPv4 link local (bound): [undef]
      Tue Oct 31 09:00:26 2017 UDPv4 link remote: AF_INET:1194

      1 Reply Last reply Reply Quote 0
      • V Offline
        viragomann
        last edited by

        Looks like the client doesn't reach the server.
        Ensure that the server listens on WAN address or you've forwarded port 1194 to the address it is listening. Also ensure the incoming packets are allowed by firewall rules.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.