hello everybody,
I've installed openvpn access server v2.8.2 on Ubuntu 16.04.6 and bought license for 70 clients.
Everything is working just fine except the Status-->Log reports menu. When I click it I get the following error message:
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: SESSION: Your session has expired, please reauthenticate (9007)
could anyone help?
regards, Manolis
SESSION ERROR
-
TonyG
- OpenVpn Newbie
- Posts: 1
- Joined: Tue Mar 24, 2020 1:52 pm
Re: SESSION ERROR
Same issue here.
-
nerdbitmn
- OpenVpn Newbie
- Posts: 1
- Joined: Wed Mar 25, 2020 5:32 pm
Re: SESSION ERROR
From support, this is an issue for 2.8.2.
A character being logged to the DB is causing issues in the web rendering. Support said the issue is benign and a new release is coming soon.
A character being logged to the DB is causing issues in the web rendering. Support said the issue is benign and a new release is coming soon.
-
Pippin
- Forum Team
- Posts: 1201
- Joined: Wed Jul 01, 2015 8:03 am
- Location: irc://irc.libera.chat:6697/openvpn
Re: SESSION ERROR
Thank for reporting it here.
I gloomily came to the ironic conclusion that if you take a highly intelligent person and give them the best possible, elite education, then you will most likely wind up with an academic who is completely impervious to reality.
Halton Arp
Halton Arp
-
fletcho
- OpenVpn Newbie
- Posts: 1
- Joined: Fri Sep 11, 2020 6:51 am
Re: SESSION ERROR
I have the same issue but the upgrade didn't resolve things.
I see the bug was fixed in version 2.8.3 so I upgraded the instance to 2.8.6 (from 2.8.2).
The Session Error still occurs each time I click on the Log Reports link and I suspect this is due to the "character" being in the DB? Can you please share the detail on which character it is so that I can try and recover the DB?
Many thanks!
I see the bug was fixed in version 2.8.3 so I upgraded the instance to 2.8.6 (from 2.8.2).
The Session Error still occurs each time I click on the Log Reports link and I suspect this is due to the "character" being in the DB? Can you please share the detail on which character it is so that I can try and recover the DB?
Many thanks!