2.7.5 doesn't work with 2.7.4 data restored

[aptalca]

I'm restoring 2.7.4 data in 2.7.5 as described in a previous post (docker environment):
1) sqlite3 back up all databases, and copy as.conf to backup folder
2) delete all data, openvpn is not installed at this point
3) Install 2.7.5, both the server and the client packages as a fresh install (subsequently stop openvpn-as)
4) sqlite3 restore databases from backup, copy over old as.conf into data folder
5) start openvpn-as

When I try to log in to admin interface, I get the following error after submitting credentials:
Sorry, a session error has occurred
It is possible that your session has expired or your login credentials do not allow access to this resource. See error text below for further details:
SESSION ERROR: argument of type 'NoneType' is not iterable: flat/twist:24,flat/ten:83,flat/flatstan:103,flat/ten:70,flat/ten:61,flat/flatstan:264,flat/ten:70,flat/ten:61,flat/flatstan:247,flat/flatstan:236,admin/astatus:165,admin/astatus:147 (exceptions.TypeError)
Retry Login

[novaflash]

This counts not as an upgrade but as a migration of data.

Are you following the steps laid out here?
https://openvpn.net/vpn-server-resource ... tallation/

[novaflash]

Oh and for the record, that error seems to me personally to indicate a lack of data. Since you have backups, you could try ovpn-init to reset the Access Server 2.7.5 so it will start up normally again, and then stop the Access Server service, and then try restoring the data from backups by overwriting/replacing the existing databases of Access Server 2.7.5. It might work then.

[aptalca]

Yes, I'm following the steps outlined for migrating data.

I just ran ovpn-init prior to restoring data and I'm getting the same error when logging in

Here's a log: https://pastebin.com/Z8nsLrKB

[novaflash]

I can restore data from AS 2.7.4 to AS 2.7.5 and it works fine. Something funky is up with your system or data.

You should contact access server support on the support ticket system and reference this forum post and send /var/log/openvpnas.log and other data you can think of might be useful in debugging this. I'd also advise investigating that log file yourself to see any obvious problems. Please also note that technically we do not release for docker and do not test on it. So it is I suppose at least possible there's a bug when used on docker. Or it could be the way the data is being migrated. I can't tell without more logs and we don't put those on public forums.

[aptalca]

Hi novaflash, thanks for your help.

With the help of a user and some luck, we identified the issue. It's not the migration process, but a specific setting we have in as.conf that causes the issue.

When we comment out the line "boot_pam_users.0=admin" in as.conf to prevent pam access and only rely on local authentication, and restart, the local users can no longer login and get the session error described above.

I simply set up a fresh 2.7.5 instance, with a pam admin user in ovpn-init. Logged in as the pam admin user, created a local user with admin rights. Then edited as.conf to comment out the first pam user and restarted. The local admin user can no longer login and gets the session error.

Thanks

[novaflash]

Good work. So it was some data issue, in as.conf and the OS this time. I would not have expected that to be the problem with such an error message to be honest. I'll make a note of it so we can look into it and perhaps make AS a little more clear about such problems in the future.

[novaflash]

We think we have found a way to make sure this won't be a problem in the next Access Server release anymore (the release after 2.7.5).

[aptalca]

Thanks, much appreciated

[lcasey001]

For what it is worth we had similar issues where a 2.7.4 configuration did not work on 2.7.5. Once necessary changes were made and had to rever back to 2.7.4 those configurations did not work as well. It was basically related to default subnets and subnet within user groups.

[kkinkopf]

I've been running this fine for many years upgrading over time with no issues. I have the exact issue as stated after upgrading from 2.7.4 to 2.7.5
I do not know Unbuntu 18.04. (or any version really)
Since I am running on Hyper-V I just reset back to my backup. This is the third time I am trying as people post work arounds. Can someone give a step by step command line to repair access to the admin console UI? I can use the VPN but no longer can gain access to the admin console.

Thanks a bunch!
Ken

[kkinkopf]

I've been running this fine for many years upgrading over time with no issues. I have the exact issue as stated after upgrading from 2.7.4 to 2.7.5
I do not know Unbuntu 18.04. (or any version really)
Since I am running on Hyper-V I just reset back to my backup. This is the third time I am trying as people post work arounds. Can someone give a step by step command line to repair access to the admin console UI? I can use the VPN but no longer can gain access to the admin console.

Thanks a bunch!
Ken