OpenVPN shuts off, needs manual turning off and on to restore

Hi team
So for about 5 days now, OpenVPN shuts off randomly. Basically the client is unable to connect with a request timeout error message. Checking if 1194 port is open results in an error.
But as soon as you access the controller, go into the OpenVPN instance, you turn it off, give it 5 seconds and your turn it back on - everything returns back to normal for... almost 24 hours. Then this scenario repeats itself, we go in, solve it, et cetera.
This is what we have on the logs (the screenshot above).
This is happening to about 6 of the 13 controllers we are currently managing. All of them are updated to the latest version and the issue started 2 day before TP-Link issued the latest update.
Let me know if you are experiencing this as well, or if you have some work around. Thank you.
P.S. I don't know why attaching the image sets it up above the text ?!?!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Clive_A The router does not respond at UPD port 1194 at all when the issue appears. I tried it with Ncat.
VPN not operational:
nc -v -u -z -w 3 192.168.0.1 1194
Ncat: Version 7.50
Ncat: Connected to 192.168.0.1:1194.
Ncat: Connection refused.
VPN operational:
nc -v -u -z -w 3 192.168.0.1 1194
Ncat: Version 7.50
Ncat: Connected to 192.168.0.1:1194.
Ncat: UDP packet sent successfully
Ncat: 1 bytes sent, 0 bytes received in 2.01 seconds.
- Copy Link
- Report Inappropriate Content
Anton320 wrote
@Clive_A The router does not respond at UPD port 1194 at all when the issue appears. I tried it with Ncat.
VPN not operational:
nc -v -u -z -w 3 192.168.0.1 1194
Ncat: Version 7.50
Ncat: Connected to 192.168.0.1:1194.
Ncat: Connection refused.
VPN operational:
nc -v -u -z -w 3 192.168.0.1 1194
Ncat: Version 7.50
Ncat: Connected to 192.168.0.1:1194.
Ncat: UDP packet sent successfully
Ncat: 1 bytes sent, 0 bytes received in 2.01 seconds.
I think we need a ticket to follow this up individually.
I need information in your email:
1. Omada Controller version. If possible, offer remote access to the privacy account email address as admin in your controller, which I will reply to in the email as you agree.
2. Omada router model, hardware and firmware version.
3. If you are using the Omada V5.15 controller, provide the device info exported from the router.
Since the beginning of 2025, we no longer create the email tickets for the user. To assist and figure it out efficiently, we recommend submitting a support ticket via email.
Please include:
1. Your Forum ID;
2. Your community nickname;
3. A detailed description of the issue and result if I have suggested anything on the thread, and the troubleshooting steps you've taken in the subject line or body of your email.
- Copy Link
- Report Inappropriate Content
p3r3s wrote
@laurentiu907 First, I switched from OpenVPN to L2TP/IPSec (same problem). I've been using Wireguard since yesterday, and it's been working fine for the first 24 hours.
Hardware Version: ER605 v2.0
Firmware Version: 2.3.0 Build 20250428 Rel.18967
I need information in your email:
1. Omada Controller version. If possible, offer remote access to the privacy account email address as admin in your controller, which I will reply to in the email as you agree.
2. Omada router model, hardware and firmware version.
3. If you are using the Omada V5.15 controller, provide the device info exported from the router.
Since the beginning of 2025, we no longer create the email tickets for the user. To assist and figure it out efficiently, we recommend submitting a support ticket via email.
Please include:
1. Your Forum ID;
2. Your community nickname;
3. A detailed description of the issue and result if I have suggested anything on the thread, and the troubleshooting steps you've taken in the subject line or body of your email.
- Copy Link
- Report Inappropriate Content
laurentiu907 wrote
@Clive_A here are the screenshots with the firmware versions - as requested.
For the other request (the network diagram and the role of this router in this VPN connection ?!?!) - I believe I didn't make myself clear enough.
The Omada router (ER605) IS the OpenVPN server for the outside clients. There is no diagram to be drawn. The TP-Link router acts as an OpenVPN instance for the remote clients that need to connect by VPN to the Omada network resources.
I need information in your email:
1. Omada Controller version. If possible, offer remote access to the privacy account email address as admin in your controller, which I will reply to in the email as you agree.
2. Omada router model, hardware and firmware version.
3. If you are using the Omada V5.15 controller, provide the device info exported from the router.
Since the beginning of 2025, we no longer create the email tickets for the user. To assist and figure it out efficiently, we recommend submitting a support ticket via email.
Please include:
1. Your Forum ID;
2. Your community nickname;
3. A detailed description of the issue and result if I have suggested anything on the thread, and the troubleshooting steps you've taken in the subject line or body of your email.
- Copy Link
- Report Inappropriate Content
@Clive_A Hi, since ~1 week I experience the exact same issue on 3 out of 4 ER605 I manage (2 are Omada-managed, other 2 are standalone) all have with 2.2.5 or 2.2.6 firmware version.
- Copy Link
- Report Inappropriate Content
Wireguard has been working without any problems for a few days now, so the problem is probably on the OpenVPN and L2TP side only.
Hardware Version: ER605 v2.0
Firmware Version: 2.3.0 Build 20250428 Rel.18967
Standalon
- Copy Link
- Report Inappropriate Content
@laurentiu907 I am having the same issue with OpenVPN on ER605 v2.0 as standalone, firmware 2.3.0 build 20250428. All clients are Windows 11 running OpenVPN Connect.
OpenVPN server on the router seems to crash, no connection can ben made. My frequency is seeming random. If I click the disable and then enable, the service starts again. Or, I can simply cycle power and correct the problem. I also have two ipsec vpn tunnels that are configured that remain connected durining this time, no issue with those with OpenVPN fails. This problem was happening prior to the firmware 2.3.0 20250428 on occasion but was hoping the new firmware would corrrect it.
- Copy Link
- Report Inappropriate Content
drac8029 wrote
@laurentiu907 I am having the same issue with OpenVPN on ER605 v2.0 as standalone, firmware 2.3.0 build 20250428. All clients are Windows 11 running OpenVPN Connect.
OpenVPN server on the router seems to crash, no connection can ben made. My frequency is seeming random. If I click the disable and then enable, the service starts again. Or, I can simply cycle power and correct the problem. I also have two ipsec vpn tunnels that are configured that remain connected durining this time, no issue with those with OpenVPN fails. This problem was happening prior to the firmware 2.3.0 20250428 on occasion but was hoping the new firmware would corrrect it.
I see all of your problems. This happens to different Omada routers with different firmware.
It is getting clear to me that this issue is related to the OVPN client update on your client devices. Somehow, it breaks the connection after some time.
Recommend that you revert to the previous version to monitor this. Or you can keep the current version and work with us to debug.
Please bear in mind that troubleshooting and debugging will take some time before we reach a conclusion on the reason.
This has been taken to the dev and test team's attention.
And IMHO, it is not recommended to update the OVPN software unless it is widely tested and stable on their feedback. For the sake of stability, it is recommended not to update frequently to avoid any unknown compatibility or other issues.
- Copy Link
- Report Inappropriate Content
It's not about a OVPN client update. We didn't update the client software on any of the client devices recently, nor the firmware on routers. Also, the whole thing is NOT about breaking the connection, the OVPN server ITSELF is breaking on the router side.
- Copy Link
- Report Inappropriate Content
@Clive_A The only remedy is to restart the ER605 or disable/re-enable the OpenVPN service on the router itself. I do not understand why you think this is a client side issue?
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 1054
Replies: 30
Voters 0
No one has voted for it yet.