OpenVPN Broken after Controller Update
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I recently updated my Omada OC200 Controller to Firmware Version 5.13.24. After the update my OpenVPN Client-to-site Servers are no longer working.
I had 3 OpenVPN servers running, each tied to the correct network (VLAN). I had a user complain that he could no longer connect via OpenVPN. I began by attempting to restart the servers. When trying to toggle them back to the "On" state, I got an error stating the Port was already in use. This is incorrect, because I specified a specific port per server which followed my VLAN numbering scheme (21194,31194,61194). Either way, I remade the servers with different ports to get around this error. I exported the new profile and input it into the OpenVPN client, and can no longer connect to the VPN.
These VPN's were functioning fine before the update, now I cannot find a reason why they are no longer working.
An example of one of my VPN Server's Settings.
Name: AdminVPN
Status: Enable
Purpose: Client-to-Site VPN
VPN Type: VPN Server - OpenVPN
Account Password: Enable
Tunnel Mode: Full
Protocol: UDP
Service Port: 51194
Authentication Mode: Local
WAN: WAN/LAN4
IP Pool: 192.168.60.0/24
Primary DNS: Blank
Secondary DNS: Blank
Router is an ER8411.
Any help would be appreciated. I'd like to iterate that VPN access is critical for our business operations, and a simple controller update should not break these settings.
Hi @D1LLeX
Thanks for posting in our business forum.
Except for the complaint on the router update, anything else you checked?
Treat it like a problem like it does not work ever.
You should also check if the firmware of the router is up-to-date.
And you actually tested it yourself with it, that right based on your description?
What system do you use? Do you find this article on the router page?
