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

OpenVpn:TLS Error: TLS handshake failed

Scheduled Pinned Locked Moved OpenVPN
7 Posts 4 Posters 5.7k 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.
  • Y
    yash
    last edited by Feb 13, 2019, 5:58 AM

    Hello All
    I had been tried to connect VPN from Pfsense , but it triggered to below error.

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

    1 Reply Last reply Reply Quote 0
    • J
      jimp Rebel Alliance Developer Netgate
      last edited by Feb 13, 2019, 3:38 PM

      That means the server received no response from the client. It could mean that the client is connecting to the wrong IP address, or that the traffic is being blocked before it reaches the server, or one of several other scenarios. Check the server log. If nothing shows up there at all at the same time the client tried to connect, then it's almost certainly a connectivity or firewall problem.

      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

      Need help fast? Netgate Global Support!

      Do not Chat/PM for help!

      1 Reply Last reply Reply Quote 0
      • Y
        yash
        last edited by Feb 14, 2019, 6:21 AM

        Hi jimp

        Thanks, i have been seen that openvpn service is running in pfsense 2.4.4, i would like you to share the error read UDP: Unknown error (code=10054) believe that pf-sense is blocking incoming connection.

        J 1 Reply Last reply Feb 14, 2019, 11:31 AM Reply Quote 0
        • R
          Rico LAYER 8 Rebel Alliance
          last edited by Feb 14, 2019, 10:44 AM

          Sure, by default any connection incoming is blocked on WAN.
          If you created your OpenVPN RAS with the wizard it will create some Firewall Rule for you.
          If you created OpenVPN RAS manual you need to put your Rule at WAN manual.

          -Rico

          1 Reply Last reply Reply Quote 0
          • J
            johnpoz LAYER 8 Global Moderator @yash
            last edited by Feb 14, 2019, 11:31 AM

            @yash said in OpenVpn:TLS Error: TLS handshake failed:

            read UDP: Unknown error (code=10054)

            Where exactly is this error? On the client? Or the server?

            As mentioned by Rico the wizard will auto create the firewall rule, but it might be on the bottom and a rule above it might block? Post up your wan rules if you have questions on if firewall is blocking etc..

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.8, 24.11

            1 Reply Last reply Reply Quote 0
            • Y
              yash
              last edited by Feb 14, 2019, 11:46 AM

              hello all

              Below error getting, while am connecting to VPN using Openvpn cliect.

              Thu Feb 14 17:10:06 2019 UDP link remote: [AF_INET] xxx.x.x.x.x:1199
              Thu Feb 14 17:10:06 2019 read UDP: Unknown error (code=10054)
              Thu Feb 14 17:10:08 2019 read UDP: Unknown error (code=10054)
              Thu Feb 14 17:10:12 2019 read UDP: Unknown error (code=10054)
              Thu Feb 14 17:10:20 2019 read UDP: Unknown error (code=10054)
              Thu Feb 14 17:10:36 2019 read UDP: Unknown error (code=10054)
              Thu Feb 14 17:11:06 2019 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
              Thu Feb 14 17:11:06 2019 TLS Error: TLS handshake failed
              Thu Feb 14 17:11:06 2019 SIGUSR1[soft,tls-error] received, process restarting
              Thu Feb 14 17:11:11 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]xxx.x.x.x.x:1199
              Thu Feb 14 17:11:11 2019 UDP link local (bound): [AF_INET][undef]:1194
              Thu Feb 14 17:11:11 2019 UDP link remote: [AF_INET]xxx.x.x.x.x:1199
              Thu Feb 14 17:11:11 2019 read UDP: Unknown error (code=10054)
              Thu Feb 14 17:11:13 2019 read UDP: Unknown error (code=10054)
              Thu Feb 14 17:11:17 2019 read UDP: Unknown error (code=10054)

              1 Reply Last reply Reply Quote 0
              • J
                johnpoz LAYER 8 Global Moderator
                last edited by Feb 14, 2019, 11:53 AM

                @yash said in OpenVpn:TLS Error: TLS handshake failed:

                read UDP: Unknown error (code=10054)

                You need to validate that port is open from your client to the server.. It could be blocked at your client side, etc.. Or sure you could be blocking it on pfsense, or some nat router between.

                Is that IP your public IP that you xxxxx out?

                Lets see your firewall rules on your wan to validate 1199 is open.. Also your pfsense is not behind a nat right? And has public IP on its wan? Simple sniff on the wan for UDP traffic 1199 and then try to connect with your client will tell you for sure if the traffic is getting to pfsense or not.

                An intelligent man is sometimes forced to be drunk to spend time with his fools
                If you get confused: Listen to the Music Play
                Please don't Chat/PM me for help, unless mod related
                SG-4860 24.11 | Lab VMs 2.8, 24.11

                1 Reply Last reply Reply Quote 0
                7 out of 7
                • First post
                  7/7
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                  This community forum collects and processes your personal information.
                  consent.not_received