You are not logged in.
After system update (pacman -Syu) On Saturday 2025-11-08 the proton-vpn-gtk-app starting giving a connection error and then loops in an effort to reconnect
I have re-installed the app and all proton dependencies including the python-proton-vpn-local-agent that was just released at version 1.6.0-1
Here are the current version of the components installed
proton-vpn-gtk-app 4.12.0-1
python-proton-core 0.7.0-1
python-proton-keyring-linux 0.2.1-1
python-proton-vpn-api-core 4.13.1-1
python-proton-vpn-local-agent 1.6.0-1
python-proton-vpn-network-manager 0.13.4-1
The following is error listed in the vpn-app.log
2025-11-10T04:40:43.136533+00:00 | proton.vpn.backend.linux.networkmanager.core.localagent_mixin:69 | INFO | Waiting for agent status from node-us-314.protonvpn.net...
2025-11-10T04:40:46.179457+00:00 | concurrent.futures:342 | ERROR | exception calling callback for <Future at 0x78ec83ff1250 state=finished raised LocalAgentError>
Traceback (most recent call last):
File "/usr/lib/python3.13/concurrent/futures/_base.py", line 340, in _invoke_callbacks
callback(self)
~~~~~~~~^^^^^^
File "/usr/lib/python3.13/site-packages/proton/vpn/backend/linux/networkmanager/core/localagent_mixin.py", line 97, in _handle_future_result
future.result()
~~~~~~~~~~~~~^^
File "/usr/lib/python3.13/concurrent/futures/_base.py", line 449, in result
return self.__get_result()
~~~~~~~~~~~~~~~~~^^
File "/usr/lib/python3.13/concurrent/futures/_base.py", line 401, in __get_result
raise self._exception
File "/usr/lib/python3.13/site-packages/proton/vpn/backend/linux/networkmanager/core/localagent_mixin.py", line 75, in _start_local_agent_listener
if not await self.__attempt_to_connect_to_listener(context):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.13/site-packages/proton/vpn/backend/linux/networkmanager/core/localagent_mixin.py", line 214, in __attempt_to_connect_to_listener
await self._agent_listener.connect(
self._vpnserver.domain, self._vpncredentials.pubkey_credentials
)
File "/usr/lib/python3.13/site-packages/proton/vpn/backend/linux/networkmanager/core/local_agent/listener.py", line 51, in connect
self._listener = await Listener.connect(domain, private_key,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
certificate)
^^^^^^^^^^^^
local_agent.LocalAgentError: Tokio(Os { code: 113, kind: HostUnreachable, message: "No route to host" })
2025-11-10T04:40:46.179570+00:00 | proton.vpn.core.connection:508 | INFO | CONN:STATE_CHANGED | Error
2025-11-10T04:40:46.179623+00:00 | proton.vpn.connection.states:401 | WARNING | Reached connection error state: UnexpectedError (None)
2025-11-10T04:40:46.182530+00:00 | proton.vpn.app.gtk.services.reconnector.reconnector:196 | INFO | VPN connection drop was detected.
2025-11-10T04:40:46.182598+00:00 | proton.vpn.app.gtk.services.reconnector.reconnector:133 | INFO | Reconnection attempt #6 scheduled in 65.91 seconds.
Any help is greatly appreciated
Thank you
Last edited by imanani (2025-11-25 01:06:56)
Offline
Hi,
I can confirm something broke, I can't establish a connection either. The timeline corresponds roughly with yours.
I noticed that it was possible to establish a vpn connection when handling the killswitch interface in a certain way.
Rolling back proton-vpn-gtk-app to version (4.9.7-1) did not solve the problem for me.
Then tried to roll back it's dependencies to other previous versions as from the pacman logs:
python-proton-vpn-api-core (0.42.5-1)
python-proton-vpn-local-agent (1.4.5-1)
python-proton-vpn-network-manager (0.12.14-1)
python-proton-vpn-local-agent (1.4.5-1)
python-proton-core (0.4.0-4)
This did not solve the problem either, which is why I believe changes in another package probably broke the functionality.
Anyway, there seems to be a problem in the way the killswitch interface is handled.
Good luck finding the problem.
I am interested in finding a solution too.
Offline
update,
I was not able to make any progress with the GUI app
So I worked directly with the wireguard tools. I had to get openresolv and Networkmanager to work together
The wireguard connection with the Protonvpn would show a good connection but the protonvpn server was not reachable and therefore no network at all.
I gave up and installed Debian 13 on another computer as it is officially supported by Protonvpn.
I installed Protonvpn directly from their servers but the same error occurred.
I have submitted a support ticket with Protonvpn.
I will update this thread if I get any info or if there is an updated version that works
Offline
Current Protonvpn app does not work on 10.x.x.x network.
work around use 172.16.x.x network or 192.168.1.x
Open ticket with proton. expect a fix in the next version.
Offline