-
-
Notifications
You must be signed in to change notification settings - Fork 13.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
protonvpn-gui: timeout #307462
Comments
Hi @Atemu, Thanks for pinging me. Could you show me the output of |
It's |
Could you share your logs when doing a quick connect? |
Gotcha, that might be the issue. As quoted in #302011 (comment) , ProtonVPN uses a NetworkManager Connection property that's introduced in NetworkManager 1.46, which is in NixOS Unstable and will be used with Gnome 46 when that releases on NixOS. Could you try to switch to Unstable for NetworkManager and see if that works for you? |
I am on unstable, I linked the Nixpkgs revision I'm using. |
Sorry about that, I misread the version. I'll post my logs. Are you using Gnome Keyring? |
Should have noted that down. I've updated the additional context section. |
Note: PR title should be updated to actually describe the issue in short. "Timeout"? What kind, how/when does it occur? |
My logs from Unstable are as follows:
My systemd logs with
Could you try to use Gnome Keyring (or KWallet and clear all configuration of ProtonVPN and see if the issue persists? Proton lists these 2 as required dependencies: https://protonvpn.com/support/official-linux-vpn-debian/ |
@Andreas02-dev Is this issue still reproducing with the latest ProtonVPN version? |
I'll try to check it out today, will let you know. |
I don't have any issues with the latest version in nixpkgs (4.3.0). |
Describe the bug
A clear and concise description of what the bug is.
When attempting to connect, I get a spinner and then an incredibly unhelpful error message:
timeout
.(Proton should get into making operating systems, they could easily rival M$ Windows at least in this quality.)
The log is not any more helpful:
This is what happens inside NM during that time:
So it appears to be doing something; setting up the leak protection and the tunnel interface(?).
What I find weird is that systemd/NM stops those targets and also nsncd. That might be part of the problem? No nsncd, no DNS. Though I don't know how pvpn is supposed to work here?
I'd really like to see the diff to a successful log here because, apparently, it's working for others in #302011.
Steps To Reproduce
Steps to reproduce the behavior:
protonvpn-app
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Running i3 on X11 but that shouldn't matter.
For testing, my secret service implementation is keepassxc's. It's unlocked and working (I can see ProtonVPN adding its entries).
Notify maintainers
@WolfangAukang (also CC @JohnRTitor @pbsds @Andreas02-dev)
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.7bb2ccd
Add a 👍 reaction to issues you find important.
The text was updated successfully, but these errors were encountered: