Troubleshooting another issue I have determined that I cannot access the VPN Server page on the sysadmin module. Anytime I access the sysadmin page, scroll down and click VPN Server, I am met with a WHOOPS exception page.
I have tried the following:
Full system reboot
fwconsole ma downloadinstall sysadmin
fwconsole ma downloadinstall sysadmin --tag=17.0.2.24 (just to try a different version)
I have checked the OpenVPN server status on the server, and both the core service and the sysadmin_1 service are both running. I have a few phones on this server using the VPN and that is where I discovered my problem. The EPM is still building the cfg files pointing the phones to the local LAN network for the VPN, but it is not building the VPN files to create the connection. Before I backup/wipe/reload, wondering if someone has a solution to this?
Well here’s a fun update. I went ahead and performed a full backup, wiped the server, did a fresh debian install, all updates, etc. I checked the sysadmin > VPN Server page, it loads like it should. I do the restore of the backup…and now it’s the same problem again. What’s interesting, is the file it is referencing seems to be base64 encoded and if the file is modified, it fails to load it and returns that it is corrupt. So whatever this issue is, it is apparently replicating inside the backups too.
Unfortunately no. I am still seeing this same problem. The only thing I can think of to do is a backup and exclude the sysadmin module from that backup. I just haven’t done it.
Are you also not able to open the sysadmin VPN server page due to same undefined array key error ? If yes then is that after backup and restore or even happening on new configuration?
So I ended up buying support credits to get this resolved as school is starting back up soon. My issue was an invalid value in the sysadmin table on one record. The ‘remote’ field had 2 different ip addresses. They removed one and now all is working fine. I don’t know whether we have the ability or credentials to administer the database directly (phpMyAdmin, etc). Anyways, that is what was causing the issue for me. Maybe it will help you?
