Web Admin redirects to /__session_start__/ and hangs

Morfi717

Hello

I have weird problem accessing web admin UI.
On opera,chrome,firefox @ windows, I open https://IP:934/admin or https://IP:1194/admin and it opens fine (except SSL warning).
However on Internet Explorer AND Safari iOS AND Chrome iOS it redirects me to https://IP:934/admin/__session_start__/ and throws 403 Forbidden.

I would probably ignore the Internet Explorer but I can't ignore Safari/Chrome@iOS as it makes me unable to configure my ovpn client (I also can't access https://IP:934/?src=connect -- it redirects me to https://IP:934/__session_start__/?src=connect and throws 403).

Thanks in advance for your help

UPDATE: Just a side note, if I add my own, proper SSL certificate (then connect through domain https://domain:934), the problem persists (just the SSL warning is gone)

The Johan

Never heard of anything like this, sorry. Sounds to me like some weird firewall/antivirus interference issue to be honest.

Morfi717

Theres no software av or fw from the servers side except linux iptables. As for the client side, PC is behind a router but cell phone is on 4G network thus totally two different networks and operating systems but exactly same issue.

I want to mention that connecting to the vpn server works fine (i managed to import ovpn file through itunes). Its just the web UI.

I wonder if it has anything to do with this weird redirection to https://client.openvpn.net:946 -- thats not my server yet it parttakes in ovpn client configuration. Can I somehow disable it or is it essential part of the entreprise deployment?

The Johan

I'm pretty sure it has nothing to do with client.openvpn.net. That's also a name that only points to your own PC.

Morfi717

I found the issue although it was totally unrelated to the openvpn itself -- I'm leaving the solution anyway.

The problem was that the *server* could not resolve any domain (I had faulty DNS configuration and thus could not resolve any host whatsoever). Correcting the nameservers on the machine fixed the problem above.

The Johan

Thank you for reporting back, hopefully it's useful to someone else if anyone ever encounters this again.