Business Community > Gateways > OpenVPN stopped working after upgrade
< Gateways

OpenVPN stopped working after upgrade

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

OpenVPN stopped working after upgrade

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
OpenVPN stopped working after upgrade
OpenVPN stopped working after upgrade
2025-01-08 04:19:56 - last edited 2025-01-08 14:57:23
Tags: #Network Connectivity #OpenVPN
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: 2.2.6 Build 20240718 Rel.82712

I had OpenVPN working on the version "2.0.1 Build 20220223". After upgrading to the latest version "2.2.6 Build 20240718 Rel.82712", it fails to connect. Logs below:

 

Tue Jan  7 22:08:58 2025 OpenVPN 2.6.12 [git:v2.6.12/038a94bae57a446c] Windows [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] [DCO] built on Jul 18 2024
Tue Jan  7 22:08:58 2025 Windows version 10.0 (Windows 10 or greater), amd64 executable
Tue Jan  7 22:08:58 2025 library versions: OpenSSL 3.3.1 4 Jun 2024, LZO 2.10
Tue Jan  7 22:08:58 2025 DCO version: 1.2.1
Tue Jan  7 22:08:58 2025 TCP/UDP: Preserving recently used remote address: [AF_INET][MY-PUBLIC-IP-ADDR]:1197
Tue Jan  7 22:08:58 2025 UDPv4 link local: (not bound)
Tue Jan  7 22:08:58 2025 UDPv4 link remote: [AF_INET][MY-PUBLIC-IP-ADDR]:1197
Tue Jan  7 22:09:25 2025 [server_server1] Peer Connection Initiated with [AF_INET][MY-PUBLIC-IP-ADDR]:1197
Tue Jan  7 22:10:29 2025 No reply from server to push requests in 64s
Tue Jan  7 22:10:29 2025 SIGUSR1[soft,no-push-reply] received, process restarting
Tue Jan  7 22:10:30 2025 TCP/UDP: Preserving recently used remote address: [AF_INET][MY-PUBLIC-IP-ADDR]:1197
Tue Jan  7 22:10:30 2025 UDPv4 link local: (not bound)
Tue Jan  7 22:10:30 2025 UDPv4 link remote: [AF_INET][MY-PUBLIC-IP-ADDR]:1197
Tue Jan  7 22:11:30 2025 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue Jan  7 22:11:30 2025 TLS Error: TLS handshake failed
Tue Jan  7 22:11:30 2025 SIGUSR1[soft,tls-error] received, process restarting
Tue Jan  7 22:11:31 2025 TCP/UDP: Preserving recently used remote address: [AF_INET][MY-PUBLIC-IP-ADDR]:1197
Tue Jan  7 22:11:31 2025 UDPv4 link local: (not bound)
Tue Jan  7 22:11:31 2025 UDPv4 link remote: [AF_INET][MY-PUBLIC-IP-ADDR]:1197
Tue Jan  7 22:11:34 2025 [server_server1] Peer Connection Initiated with [AF_INET][MY-PUBLIC-IP-ADDR]:1197
Tue Jan  7 22:12:36 2025 No reply from server to push requests in 62s
Tue Jan  7 22:12:36 2025 SIGUSR1[soft,no-push-reply] received, process restarting
Tue Jan  7 22:12:37 2025 TCP/UDP: Preserving recently used remote address: [AF_INET][MY-PUBLIC-IP-ADDR]:1197
Tue Jan  7 22:12:37 2025 UDPv4 link local: (not bound)
Tue Jan  7 22:12:37 2025 UDPv4 link remote: [AF_INET][MY-PUBLIC-IP-ADDR]:1197
Tue Jan  7 22:13:37 2025 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue Jan  7 22:13:37 2025 TLS Error: TLS handshake failed
Tue Jan  7 22:13:37 2025 SIGUSR1[soft,tls-error] received, process restarting
Tue Jan  7 22:13:38 2025 TCP/UDP: Preserving recently used remote address: [AF_INET][MY-PUBLIC-IP-ADDR]:1197
Tue Jan  7 22:13:38 2025 UDPv4 link local: (not bound)
Tue Jan  7 22:13:38 2025 UDPv4 link remote: [AF_INET][MY-PUBLIC-IP-ADDR]:1197
Tue Jan  7 22:13:43 2025 [server_server1] Peer Connection Initiated with [AF_INET][MY-PUBLIC-IP-ADDR]:1197

...

 

I have regenerated the server certificate as well after the upgrade but still the same error.

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:OpenVPN stopped working after upgrade-Solution
2025-01-08 14:57:19 - last edited 2025-01-08 17:22:53

I deleted my current OpenVPN configuration, rebooted the router, created a new configuration and it worked!

 

--------

 

Also I added the line:


windows-driver wintun

 

to switch to "OpenVPN Wintun"

 

The default the adapter is "OpenVPN TAP-Windows6".

 

---------

 

Also added the line:

 

data-ciphers AES-128-CBC

 

to remove this message

 

DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.

 

 

 

Recommended Solution
  1  
  1  
#4
Options
3 Reply
Re:OpenVPN stopped working after upgrade
2025-01-08 06:21:48

Hi @snathan 

Thanks for posting in our business forum.

Reading this log gives an indication that the remote server is not reachable.

What's the result of your check on WAN?

  0  
  0  
#2
Options
Re:OpenVPN stopped working after upgrade
2025-01-08 12:51:15

Hello and thanks for the suggesion. Below is what I used to test my WAN connection as well as OpenVPN is actively listening and responding on the designated port.

 

nc -vz -u [MY-PUBLIC-IP-ADDR] 1197
Connection to [MY-PUBLIC-IP-ADDR] 1197 port [udp/*] succeeded!

 

I also serve a lot of other services on that WAN so pretty sure it's up and running.

 

Thanks

 

 

  0  
  0  
#3
Options
Re:OpenVPN stopped working after upgrade-Solution
2025-01-08 14:57:19 - last edited 2025-01-08 17:22:53

I deleted my current OpenVPN configuration, rebooted the router, created a new configuration and it worked!

 

--------

 

Also I added the line:


windows-driver wintun

 

to switch to "OpenVPN Wintun"

 

The default the adapter is "OpenVPN TAP-Windows6".

 

---------

 

Also added the line:

 

data-ciphers AES-128-CBC

 

to remove this message

 

DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.

 

 

 

Recommended Solution
  1  
  1  
#4
Options

Information

Helpful: 0

Views: 836

Replies: 3

Tags

Network Connectivity OpenVPN
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.