admin page does redirect to client page

awiechert

I've installed openvpn-as server on ubuntu 20.4 in docker. Currently I'm facing a strange behaviour.

When I try to login to https://localhost:943/admin/ I see the login page. After login I'm redirected to the licence agrement and if I click on agree it redirects me to https://localhost:943/?src=connect

I'm not able to visit the admin page. How can I fix this

openvpn_inc

Hello awiechert,

This is a symptom of a deeper problem. Please check /var/log/openvpnas.log for error messages. If those logs contain something sensitive, contact https://openvpn.net/support

Also note that officially we do not support running under Docker ourselves.

Kind regards,
Johan

awiechert

Hi,

thanks for your reply. I've added to log output for the call here. I personaly would guess this is not related to the dockerized setup.

https://pastebin.com/2zSJBCR1

openvpn_inc

Hello awiechert,

Probably not related to being in Docker. Then again, we don't test for that. But admittedly it sounds unlikely to be related to that.

What I see is a traceback about some unhandled error. This is the real problem. This is why you can't login normally.

Can I assume that you are actually really using Ubuntu 20.04 LTS as operating system, and that you have followed the installation instructions for Ubuntu 20.04 LTS from this page? https://openvpn.net/vpn-software-packages/

Sometimes we see people trying to run Access Server on for example Ubuntu 20.10 which is not supported. We only support the LTS version.

Can you tell us anything more about your environment? If you like, you can open a support ticket at https://openvpn.net/support and support more detailed information there. When we install Access Server on Ubuntu 20.04 LTS we do not see this problem. And I have a number of servers running on this platform without showing this traceback. So it would be helpful for us to learn how you are able to produce this problem, so that we can investigate and resolve it.

Kind regards,
Johan

awiechert

Hi Johan,

I can confirm it's ubuntu20.4 as I personaly only use LTS images too. I've used exactly this instructions here https://openvpn.net/vpn-software-packages/#collapse-ubuntu-0.

I'll try to rebuild this in a VM next days vs. a rebuild in Docker and add some further informations here. Is there an eays way to extend the log level?

openvpn_inc

Hello awiechert,

For this particular case I don't think increasing the log level gets us more than the traceback is already giving us. Usually our goal is to get to that traceback and find a way to reproduce/understand it. What's more interesting now is how to reproduce this as on Ubuntu 20.04 LTS I am not able to reproduce this problem at this moment.

Please let us know the results of your efforts - if there's a way to reproduce this we'd like to try and do so.

Kind regards,
Johan

moy144k

Hi,

I'm having a similar issue. So far what I've noticed is that if I log in to the admin page right after configuring the server, it works well. But after restarting the computer and log in, I get past the login page, but the website doesn't display properly and I receive an error in big red letters, "An error occurred while rendering the response."

Here's my log from /var/log/openvpnas.log
https://pastebin.com/4SgQvNkb

$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.4 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.4 LTS"
VERSION_ID="20.04"

moy144k

So after disabling the Wi-Fi adapter and wiring in through Ethernet, the issue hasn't reoccurred. Perhaps the Wi-Fi firmware is causing data corruption. I also had to delete and recreate the access server configuration after wiring in.

I did notice some glitches with the Wi-Fi and since the hardware is Intel on a Dell laptop, there may be some bugs or incompatibilities with the firmware.

I'll let you know if it happens again on the Ethernet connection.

openvpn_inc

Hi,

My guess would be a routing issue, where the system tries to configure more than one interface. You probably need to disable the wireless interface, if you plan to use Ethernet. Usually there is a Fn+key combination to turn off wireless.

In 20+ years of GNU/Linux use I have never known an instance of firmware causing data corruption other than possibly in a running instance of the relevant driver. So, no, that's not it.

regards, rob0

moy144k

Because of proprietary hardware, I had to use non-free firmware. This automatically used the latest iwlwifi 8000c firmware for the Intel Wireless 8260 hardware during the install. I forced the OS to use 1 version older to it and so far haven't experienced the same issue. The Wi-Fi connection is now stable and the website is too.