Hello,
Can confirm on my system with 2.12.3 that public IP is still being shown correctly on web login.
However, it sounds like a bug or imperfection. In reality when you access the Access Server on the TCP port 443 (the default HTTPS port and assuming default configuration) you are actually hitting the OpenVPN TCP daemon which then transfers the connection internally to the web services. That way the OpenVPN TCP daemon and the web services can share the same port. That is useful to bypass certain simple firewalls that block everything except TCP 443 (HTTPS traffic). And maybe in your particular configuration that shows up as 127.0.0.1 because it's internal traffic.
I'd suggest contacting support and sending a sacli support output so we can see if there is a particular configuration that would solve this.
Oh, and try accessing your Access Server's web interface on port TCP 943. Like https://123.45.67.89:943/ or such.
Kind regards,
Johan
Can confirm on my system with 2.12.3 that public IP is still being shown correctly on web login.
However, it sounds like a bug or imperfection. In reality when you access the Access Server on the TCP port 443 (the default HTTPS port and assuming default configuration) you are actually hitting the OpenVPN TCP daemon which then transfers the connection internally to the web services. That way the OpenVPN TCP daemon and the web services can share the same port. That is useful to bypass certain simple firewalls that block everything except TCP 443 (HTTPS traffic). And maybe in your particular configuration that shows up as 127.0.0.1 because it's internal traffic.
I'd suggest contacting support and sending a sacli support output so we can see if there is a particular configuration that would solve this.
Oh, and try accessing your Access Server's web interface on port TCP 943. Like https://123.45.67.89:943/ or such.
Kind regards,
Johan
Statistics: Posted by openvpn_inc — Tue Nov 28, 2023 9:39 pm