Hi All
I have an issue while I’m updating my Pritunl Client, it suddenly does not connect after an update but if I install to the previous version which is 1.3.4026.10 it connects, Have any of you experienced the same thing?
-Pritunl Client v1.3.4058.0 (can’t connect)
-Pritunl Client v1.3.4026.10 (can connect)
My Pritunl Server version (pritunl v1.32.3805.95)
btw this all happens on all windows/mac devices
Send the service logs from the top right menu.
Copy the full log in text formate.
same issue here:
2024-10-22 15:33:55][ERRO] ▶ connection: Disconnecting ◆ client_disconnect=true ◆ client_disconnect_waiters=0 ◆ client_disconnected=false ◆ client_provider=true ◆ client_startime=40 ◆ data_iface="" ◆ data_mode="" ◆ data_remotes=[]string{"11.22.33.44", "example.com*"} ◆ data_status="connecting" ◆ data_timestamp=0 ◆ data_tun_iface="" ◆ ovpn_auth_failed=false ◆ ovpn_cmd=false ◆ ovpn_connected=false ◆ ovpn_dir="" ◆ ovpn_last_auth_failed=-1 ◆ ovpn_management_pass=false ◆ ovpn_management_port=0 ◆ ovpn_path="openvpn" ◆ ovpn_remotes=[]string{} ◆ ovpn_running=0 ◆ ovpn_tap_iface="" ◆ profile_device_auth=false ◆ profile_disable_dns=false ◆ profile_disable_gateway=false ◆ profile_dynamic_firewall=false ◆ profile_force_connect=false ◆ profile_force_dns=false ◆ profile_geo_sort=false ◆ profile_id="50b7df84d4c80f29" ◆ profile_mode="ovpn" ◆ profile_reconnect=true ◆ profile_sso_auth=true ◆ profile_system_profile=false ◆ profile_timeout=false ◆ state_closed=false ◆ state_closed_waiters=0 ◆ state_deadline=false ◆ state_delay=false ◆ state_interactive=false ◆ state_no_reconnect=false ◆ state_stop=true ◆ state_system_interactive=false ◆ state_temp_paths=[]string{} ◆ state_time=time.Date(2024, time.October, 22, 15, 33, 15, 656277575, time.Local) ◆ wg_bash_path="" ◆ wg_conf_path="" ◆ wg_conf_path2="" ◆ wg_connected=false ◆ wg_last_handshake=0 ◆ wg_path="/usr/bin/wg" ◆ wg_priv_key=false ◆ wg_pub_key=false ◆ wg_quick_path="/usr/bin/wg-quick" ◆ wg_server_pub_key=false ◆ wg_sso_start=time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC) ◆ wg_sso_token=false ◆ wg_util_path=""
Unfortunately i cant roll back. where can i download the former deb package?
found it and back online now. maybe issue its related to sso-auth. the new client did not try to open the browser for sso.
There was an issue with an incorrectly handled error causing only one remote to be attempted. Check the logs for Attempting remotes followed by one Attempting remote then a disconnect. This will be fixed in an update this week.