Hello, I’m testing authentication timeouts with Google SSO and I’ve noticed that the client does not seem to recognize the server pushed openvpn disconnect when authentication has expired. I see the message in the client logs but the connection just continuously tries to restart while on the profile page it still shows as connected. When using wireguard as the connection method the client disconnects as expected when the server terminates the session. This seems like an unintended bug in the client? I have both Pritunl and OpenVPN authentication cache disabled.
The client will continue to attempt to reconnect unless reconnection is disabled in the top right settings.
Hi Zach,
I tried out that setting but the situation is still the same. I’ve double checked the setting again and its is indeed disabled, stopped and started the server, re-imported the connection profile on the client, but when connected with OpenVPN the client still says connected log after the server kills the connection.
Open the logs in the top right menu and check the log for the profile that is having the issue.
There are issues on Windows where the TAP adapters become unusable. The client update today will also reset the TAP adapters with the reset networking option in the client menu.
2025-09-05 08:24:16 TCP/UDP: Preserving recently used remote address: [AF_INET]<redacted>:18300
2025-09-05 08:24:16 UDPv4 link local: (not bound)
2025-09-05 08:24:16 UDPv4 link remote: [AF_INET]<redacted>:18300
2025-09-05 08:24:20 Server poll timeout, restarting
2025-09-05 08:24:20 SIGUSR1[soft,server_poll] received, process restarting
This just repeats forever until I hit the disconnect button. I’m using TUN not TAP for the connection.