Site-2-Site VPN Connections missing
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello,
we are Using Omada-Device on 3 sites and have connections setup between a total of 5 sites.
Today I would be required to modify the data of one connection due to an IP-Adress change.
Then I noted, that on one site the "Site-2-Site" VPN-Tab is just gone?
The Dashboard and VPN-Tab show the VPN-Connections (without Names) as established (and they are working)
but I cannot modify them through the VPN-Tab. Trying to create an (inivisble) connection yields the error message,
that the same settings cannot be used.
Any ideas how to get the VPN connections back - If possible without a total-reset?
Any help appreciated.
Controller-Version is 5.9.32
Dashboard:
VPN-Status:
But nothing except open-vpn in the VPN-Configuration-Menu:
@dognose These Errors are visible in the javascript console, for chrome and InternetExplorer.
Maybe related, maybe not.
Just checked another OC200 on a second side - same Controller Version - There it works, and it doesn't show the "Canot read properties" Error in the console.
(Errors about Navigaion / stlyesheet are there as well)
@Clive_A I've tried with Incognito mode and two different browsers (and from a different PC) Result is the same.
I've now downgraded the Controller to 5.7.6 again and imported an auto-backup from before the upgrade - and it's working again.
Also, no errors (beside the wrong style-sheet mime type) in the JS-Console.
With 5.9.32 Wireguard VPN and FullMode for OpenVPN has been introduced.
Maybe these new features somehow mess with the existing configuration, making the controller crash on trying to display the Manual IPSec Connections?
@Clive_A
I've now upgraded the control version again.
After Upgrading, the Navigation-Error in the console was back:
Data still displayed correctly.
So, I also imported the auto-backup from yesterday again.
And still, data is displayed correctly and the "undefined-Error" is not appearing.
So, whatever was wrong with the data yesterday - we can savely conclude that this error in the Console was related to the missing display.
On the dashboard, each IPSec was shown without name as well. So, I strongly assume that "there" an empty name-property was handled to display "---" while in the actual
configuration view - it just tried to access a null-object and therefore failed to render the row.
Maybe - despite the question, why the name of the connections "vanished" - The script should be improved to handle undefined errors in this location as well.