OpenVPN Error TLS key negotiation failed to occur within 60 seconds on my Archer VR1210v v1

OpenVPN Error TLS key negotiation failed to occur within 60 seconds on my Archer VR1210v v1

OpenVPN Error TLS key negotiation failed to occur within 60 seconds on my Archer VR1210v v1
OpenVPN Error TLS key negotiation failed to occur within 60 seconds on my Archer VR1210v v1
Friday - last edited 17 hours ago
Tags: #VPN
Model: Archer VR1210v  
Hardware Version: V1
Firmware Version: 2.0.0 0.10 v6041.0 Build 240708 Rel.13164n

Hi,

I have a problem with my Archer VR1210V, I have setup OpenVPN with Dynamic DNS on NO-IP and this service is logged correctly but when I try to connect with OpenVPN GUI V11.56.0.0 (OpenVPN v2.6.15) I receive always same error. I have reported log below.

Thanks

 

2025-11-07 11:04:15 WARNING: Compression for receiving enabled. Compression has been used in the past to break encryption. Sent packets are not compressed unless "allow-compression yes" is also set.
2025-11-07 11:04:15 Note: --data-ciphers-fallback with cipher 'AES-128-CBC' disables data channel offload.
2025-11-07 11:04:15 OpenVPN 2.6.15 [git:v2.6.15/90bdd59a95170169] Windows [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [DCO] built on Sep 22 2025
2025-11-07 11:04:15 Windows version 10.0 (Windows 10 or greater), amd64 executable
2025-11-07 11:04:15 library versions: OpenSSL 3.5.3 16 Sep 2025, LZO 2.10
2025-11-07 11:04:15 DCO version: 1.3.3
2025-11-07 11:04:15 MANAGEMENT: TCP Socket listening on [AF_INET]
2025-11-07 11:04:15 Need hold release from management interface, waiting...
2025-11-07 11:04:16 MANAGEMENT: Client connected from [AF_INET]
2025-11-07 11:04:16 MANAGEMENT: CMD 'state on'
2025-11-07 11:04:16 MANAGEMENT: CMD 'log on all'
2025-11-07 11:04:16 MANAGEMENT: CMD 'echo on all'
2025-11-07 11:04:16 MANAGEMENT: CMD 'byte count 5'
2025-11-07 11:04:16 MANAGEMENT: CMD 'state'
2025-11-07 11:04:16 MANAGEMENT: CMD 'hold off'
2025-11-07 11:04:16 MANAGEMENT: CMD 'hold release'
2025-11-07 11:04:16 WARNING: No server certificate verification method has been enabled.
2025-11-07 11:04:16 MANAGEMENT: >STATE:1762509856,RESOLVE,,,,,,
2025-11-07 11:04:16 TCP/UDP: Preserving recently used remote address: [AF_INET] xxx.xxx.xxx.xxx:1194
2025-11-07 11:04:16 Socket Buffers: R=[65536->65536] S=[65536->65536]
2025-11-07 11:04:16 UDPv4 link local: (not bound)
2025-11-07 11:04:16 UDPv4 link remote: [AF_INET]xxx.xxx.xxx.xxx:1194
2025-11-07 11:04:16 MANAGEMENT: >STATE:1762509856,WAIT,,,,,,
2025-11-07 11:05:16 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
2025-11-07 11:05:16 TLS Error: TLS handshake failed
2025-11-07 11:05:16 SIGUSR1[soft, tls- error] received, process restarting
2025-11-07 11:05:16 MANAGEMENT: >STATE:1762509916,RECONNECTING,t l s-error,,,,,
2025-11-07 11:05:16 Restart pause, 1 second(s)
2025-11-07 11:05:17 WARNING: No server certificate verification method has been enabled.
2025-11-07 11:05:17 MANAGEMENT: >STATE:1762509917,RESOLVE,,,,,,
2025-11-07 11:05:17 TCP/UDP: Preserving recently used remote address: [AF_INET]xxx.xxx.xxx.xxx:1194
2025-11-07 11:05:17 Socket Buffers: R=[65536->65536] S=[65536->65536]
2025-11-07 11:05:17 UDPv4 link local: (not bound)
2025-11-07 11:05:17 UDPv4 link remote: [AF_INET]xxx.xxx.xxx.xxx:1194
2025-11-07 11:05:17 MANAGEMENT: >STATE:1762509917,WAIT,,,,,,
2025-11-07 11:05:52 S I G TERM[hard,] received, process exiting
2025-11-07 11:05:52 MANAGEMENT: >STATE:1762509952,EXITING,S I G TERM,,,,,

 

My actually VPN configuration file:

client
dev tun
proto udp
float
nobind
data-ciphers-fallback AES-128-CBC
comp-lzo adaptive
resolv-retry infinite
persist-key
persist-tun
verb 3
remote xxx  xx  xx 1194

<ca>
</ca>
<cert>
</cert>
<key>
</key>


I have add "data-ciphers-fallback AES-128-CBC" row only to try a different way to solve my problem but without success...

  0      
  0      
#1
Options
1 Reply
Re:OpenVPN Error TLS key negotiation failed to occur within 60 seconds on my Archer VR1210v v1
10 hours ago

Hello @NETCITIES_NICO ,

Welcome to our community.

 

Archer VR1210v is a customized device specifically designed for local Service Providers. Its software is tailored to meet the unique requirements of these providers, ensuring alignment with their specific needs.

Due to the specialized nature of the firmware on your device, our ability to provide troubleshooting may be limited. We recommend contacting the technical support of your Service Provider who supplied the device, as they are best suited to provide the necessary assistance for your device.

  0  
  0  
#2
Options