-
Notifications
You must be signed in to change notification settings - Fork 355
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
Linux CLI cannot connect, retries forever #7412
Comments
It might help to disable quantum resistant tunnels:
New as in doesn't occur after downgrading to 2024.7? |
Disabling quantum-resistant tunnels and obfuscation as suggested in #7292 did not help. By new I just meant I haven't seen this before. I can't test other versions or anything else now because after rebooting the issue is gone. Hopefully the log is useful, otherwise I will have to wait until this happens again. |
Thank you for ruling that out! I couldn't identify any obvious cause after reading the logs, unfortunately. Feel free to ping us if/when it happens again. |
Have you seen these before? Seems like issues connecting to Mullvad API servers. I did check that internet works without the VPN in all cases, so not sure why these requests were failing/timing out. [2025-01-02 19:33:52.554][mullvad_daemon::device][ERROR] Error: Failed to check device or account validity
Caused by: Unexpected HTTP request error
Caused by: Hyper error
Caused by: error trying to connect: deadline has elapsed
Caused by: deadline has elapsed
[2025-01-02 19:33:52.554][mullvad_daemon::device][ERROR] Error: Failed to check device or account validity
Caused by: Unexpected HTTP request error
Caused by: Hyper error
Caused by: error trying to connect: deadline has elapsed
Caused by: deadline has elapsed
[2025-01-02 19:33:52.554][mullvad_daemon::device][ERROR] Error: Failed to check device or account validity
Caused by: Unexpected HTTP request error
Caused by: Hyper error
Caused by: error trying to connect: deadline has elapsed
Caused by: deadline has elapsed [2025-01-02 20:30:02.667][mullvad_api::rest][ERROR] Error: HTTP request failed
Caused by: Hyper error
Caused by: error trying to connect: Connection refused (os error 111)
Caused by: Connection refused (os error 111)
[2025-01-02 20:30:02.667][mullvad_daemon::device][ERROR] Failed to validate device: Unexpected HTTP request error
[2025-01-02 20:30:02.667][mullvad_daemon::device][ERROR] Error: Failed to check device or account validity
Caused by: Unexpected HTTP request error
Caused by: Hyper error
Caused by: error trying to connect: Connection refused (os error 111)
Caused by: Connection refused (os error 111) |
OK, it's an opensnitch issue, sorry. |
Is it a bug?
I have checked if others have reported this already
Current Behavior
Tries forever to connect to a relay. About every 30 seconds I get another "Connecting" to a new relay.
Expected Behavior
Instant connection like with the mobile app
Steps to Reproduce
mullvad connect
Failure Logs
Operating system version
Arch Linux
Mullvad VPN app version
2024.8
Additional Information
Connection behaviour has always been bad on Linux, takes 5 or 6 attempts and about 5 minutes to connect at all, and sometimes totally breaks (same behaviour as this issue, often after changing repeaters within the same wifi network) and requires a reboot.
This problem is new.
The text was updated successfully, but these errors were encountered: