-
Notifications
You must be signed in to change notification settings - Fork 64
App hangs on connection #12
Comments
Hey @joshbowyer Does the issue persist after the latest update ? |
So it looks like it just fails to connect. It creates the three network devices (*intfr0) but after a while the connecting screen eventually just shows a Close button and returns to the main screen which still says not connected, and I have no network connectivity.
|
Hey @joshbowyer please ensure you're running on the latest versions. |
I am. I just updated this morning from the official repo.
|
Are there logs I can check? Or does it just bootstrap NetworkManager? |
Hey @joshbowyer You can check the logs via the following commands:
If you don't manage to figure it out, you're more then welcome to reach out to our incredible support team at: https://protonvpn.com/support-form which will help you out. |
The following appears to be the issue: protonvpn.log:2021-06-23 09:04:47,899 — nm_client_mixin.py — ERROR — __dynamic_callback:124 — Exception: NM.Client.add_connection_finish() takes exactly 2 arguments (1 given) The following might be a result of the above but posting it for posterity: protonvpn-daemon.log:2021-06-23 08:44:29,894 — dbus_daemon_reconnector.py — ERROR — manually_start_vpn_conn:272 — Unknown reconnector error: Expected a string or unicode object. |
Hey @joshbowyer please provide also the output of |
Got a few new lines after trying again after a reboot. Jul 07 10:04:35 mobian NetworkManager[687]: [1625670275.1629] device (pvpnroutintrf0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') |
This seems to be the issue: |
That stuck out to me too, but what is causing that? I have an initialized keychain |
By |
nm-applet is indeed missing (as this isn't a shell that uses applets).
Can this be changed? Maybe a simple conditional to check which shell is being used or something? And to ignore/continue if it's a shell without applets (phosh for example)?
|
@joshbowyer it's a dependency for NetworkManager to work properly. Could you try the following:
|
The connection works either way.
|
Hello, I have the same issue because I am using Let me know if I need to open a new issue. Thanks for your help ! |
I suspect protonvpn needs nm-applet and a notification server. When I start np-applet with notifications disabled (nm-applet --no-agent), protonvpn hangs during the connection. For me, enabling notifications (taking out the --no-agent flag and having a server) fixes the problem. |
Well the agent is needed mostly for NM because the openvpn password is stored in the keyring. Some versions of
And this is key here, since the "store password only for this user" won't work on lubuntu systems that use the native nm-tray because NM will need to ask keyring for the password, thus users wanting to use our app will need to switch to nm-applet. As an example, I'm running Manjaro with Gnome (5.10.42-1-MANJARO) and I don't have the network-manager-applet package installed. Currently, nm related packages installed on my system are:
|
I have all the Debian equivalents of those installed but it doesnt work.
Did you see the error log I posted here showing an incorrect amount of arguments?
|
@joshbowyer if you referring to
Then it's most probably not the cause. If this was the cause then the results would've been different. Either way this has been fixed, and should ship with next update. |
I'm having a related issue (#9). I use KDE and by default this nm-applet is not running. Has the dependency to nm-applet been removed? |
So we have to explicitly run nm-applet in an additional window every time we want to connect? Isn't there a workaround where nm-applet can automaticaly run in the background?... |
Bumping, would it be possible to simply check for nm-applet and if its not present to connect without it? That way if its present the functionality isnt removed but if its not then it doesnt fail |
Bumping again, the app is currently unusable without nm-applet and many distros now dont ship with it |
Is the connection established on the second try? |
Nope
|
similar issue also on manjaro kde. latest protonvpn version |
When clicking Quick Connect, the vpn connection is established but the interface is stuck on Connecting with the waiting circle animation going indefinitely.
Debian Bullseye aarch64
Also, does the Kill Switch functionality work if the app is closed but libindicator is not used (such as when using a desktop environment that does not implement it, like Phosh)?
The text was updated successfully, but these errors were encountered: