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

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

Scheduled Pinned Locked Moved OpenVPN
7 Posts 2 Posters 1.1k 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.
  • D
    Dmaj
    last edited by Jan 31, 2023, 10:44 PM

    Hello World,

    I am hoping someone in this community is able to help me, I know a little about networking but am no expert. I have been following youtube videos from the likes of Lawrence Systems but have not been able to implement a working OpenVPN server with outside connections.

    Lawrence Systems "Tutorial: pfsense OpenVPN Configuration For Remote Users 2020"
    https://www.youtube.com/watch?v=PgielyUFGeQ

    pfSense system

    38ef52c9-e3ab-42af-adea-8679c627b02d-image.png

    This issue I have is a PC within my local network is able to connect to the OpenVPN server so I know the credentials and authentication are correct however when I try to connect with my mobile device on 4G I get timeout errors. I have a Family member whom I believe was testing with his windows computer and received the error message:-

    2023-01-30 22:36:05 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
    

    I'm waiting for him to clear his log retest and send me this information.

    My successful connection, local computer Log output is below:-

    2023-01-30 19:28:22 OpenVPN 2.5.2 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 21 2021
    2023-01-30 19:28:22 Windows version 10.0 (Windows 10 or greater) 64bit
    2023-01-30 19:28:22 library versions: OpenSSL 1.1.1k  25 Mar 2021, LZO 2.10
    Enter Management Password:
    2023-01-30 19:28:28 TCP/UDP: Preserving recently used remote address: [AF_INET]10.132.152.178:1194
    2023-01-30 19:28:28 UDPv4 link local: (not bound)
    2023-01-30 19:28:28 UDPv4 link remote: [AF_INET]10.132.152.178:1194
    2023-01-30 19:28:29 [EMBY SERVER SC] Peer Connection Initiated with [AF_INET]10.132.152.178:1194
    2023-01-30 19:28:29 open_tun
    2023-01-30 19:28:29 tap-windows6 device [Local Area Connection] opened
    2023-01-30 19:28:29 Set TAP-Windows TUN subnet mode network/local/netmask = 10.0.8.0/10.0.8.2/255.255.255.0 [SUCCEEDED]
    2023-01-30 19:28:29 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.0.8.2/255.255.255.0 on interface {26AEFC9F-261E-4EE7-920F-48A8B1C9E54C} [DHCP-serv: 10.0.8.254, lease-time: 31536000]
    2023-01-30 19:28:29 Successful ARP Flush on interface [6] {26AEFC9F-261E-4EE7-920F-48A8B1C9E54C}
    2023-01-30 19:28:29 IPv4 MTU set to 1500 on interface 6 using service
    2023-01-30 19:28:34 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
    2023-01-30 19:28:34 Initialization Sequence Completed
    2023-01-30 19:28:42 SIGTERM received, sending exit notification to peer
    2023-01-30 19:28:44 SIGTERM[soft,exit-with-notification] received, process exiting
    

    I saw on the Netgear documentation that you can assign an interface to the server which I believe I have also compelled and set up the correct NAT and Firewall rules however I feel this is where the outside connections are failing.

    I believe that I have identified the inbound connections (pfSense logs seem to update very slowly! ) but I never seem to identify outbound traffic to the inbound IP address.

    NAT Rules

    d519af56-c532-40b9-9753-f0549d022983-image.png

    Firewall Rules

    a789a786-5852-4e4f-9ba6-43b811df28e8-image.png

    67eece6a-b45e-435a-bf68-70e74e07438d-image.png

    OpenVPN Server

    8ae20ee2-a51a-4063-83eb-23e53e038d59-image.png

    365b109e-994b-4b79-a6ae-9c349f6a64d1-image.png

    .ovpn

    dev tun
    persist-tun
    persist-key
    data-ciphers AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305:AES-256-CBC
    data-ciphers-fallback AES-256-CBC
    auth SHA256
    tls-client
    client
    resolv-retry infinite
    remote 10.132.152.178 1194 udp4
    nobind
    verify-x509-name "EMBY SERVER SC" name
    auth-user-pass
    remote-cert-tls server
    explicit-exit-notify
    

    Please can someone help point me in the right direction?

    V 1 Reply Last reply Jan 31, 2023, 11:23 PM Reply Quote 0
    • V
      viragomann @Dmaj
      last edited by Jan 31, 2023, 11:23 PM

      @dmaj
      I am missing information about what is in front of your WAN. Your WAN has obviously a private IP, so is there an ISP router in front of it?

      If so you have to forward UDP port 1194 on it to the pfSense WAN address.

      D 1 Reply Last reply Jan 31, 2023, 11:27 PM Reply Quote 0
      • D
        Dmaj @viragomann
        last edited by Jan 31, 2023, 11:27 PM

        Hello @viragomann

        Thanks for posting. No other router exists. Fiber to the home then is converted into RJ45 straight into pfSense network adapter.

        V 1 Reply Last reply Jan 31, 2023, 11:33 PM Reply Quote 0
        • V
          viragomann @Dmaj
          last edited by Jan 31, 2023, 11:33 PM

          @dmaj
          I see 10.132.152.17 in your config and log as your WAN.
          If this is your WAN address there is sadly no way to access it from the internet. It's a private address and between this and the www might be a router who doesn't forward anything to you.

          D 1 Reply Last reply Jan 31, 2023, 11:53 PM Reply Quote 0
          • D
            Dmaj @viragomann
            last edited by Jan 31, 2023, 11:53 PM

            @viragomann

            And I assume if I tried to use my public IP address without my ISP forwarding traffic it would not hit my router? I also tried dynamic DNS service but at the time I was not seeing anything different in my test results, I'll quickly double-check this statement.

            V 1 Reply Last reply Feb 1, 2023, 12:02 AM Reply Quote 0
            • V
              viragomann @Dmaj
              last edited by Feb 1, 2023, 12:02 AM

              @dmaj
              As mentioned, all I can see is a private address. If there is no ISP router at your location it's at the ISPs site and your WAN IP will not be reachable from the internet.

              Dynamic DNS services often refuse private IP addresses, but some may accept it.

              D 1 Reply Last reply Feb 14, 2023, 8:21 PM Reply Quote 0
              • D
                Dmaj @viragomann
                last edited by Feb 14, 2023, 8:21 PM

                @viragomann

                I appreciate your help, it pushed me in the right direction, there must indeed have been my ISP router out in the street box/head office. My WAN was using a private IP address with I assume the public IP address at my ISP router.

                I believe that traffic was hitting my Pfsense router but the outbound traffic was not being NAT'd correctly by the ISP router.

                Anyway, I upgraded to have a public IP on my router which resolved the issue.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                  [[user:consent.lead]]
                  [[user:consent.not_received]]