Weird UI after Sleep

[GibMeMyPacket]

Issue report

Operating system: Windows 10

App version: 2022.5

Issue description

The issue is that usually, when i put the computer to sleep while Mullvad has been connected (via SSH bridge), after that i wake the computer up, Mullvad is not getting connected and acting weird! It doesn't happen all the time, but i can pretty sure say half the time. https://i.imgur.com/5mcRMTk.gif The gif above shows the issue.

To get it fixed, i have to restart or close all processes of Mullvad via Process Hacker by searching Mullvad and selecting all processes in it.

[faern]

Please send a problem report from within the app. We will need app logs in order to figure out what went wrong here.

[GibMeMyPacket]

Please send a problem report from within the app. We will need app logs in order to figure out what went wrong here.

Done, however i can tell that the last logs are:

System information:
mullvad-product-version: 2022.5
os: Windows 10 Build 19045

====================
Log: \\?\C:\ProgramData\Mullvad VPN\openvpn.log
====================
OpenVPN 2.5.3 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZ4] [AEAD] built on Jul  8 2021
Windows version 10.0 (Windows 10 or greater) 64bit
library versions: OpenSSL 1.1.1j  16 Feb 2021
[mullvad_daemon::management_interface][DEBUG] disconnect_tunnel
[mullvad_daemon][DEBUG] Target state Secured => Unsecured
[mullvad_daemon::management_interface][DEBUG] connect_tunnel
[mullvad_daemon][DEBUG] Target state Unsecured => Secured
[mullvad_daemon::management_interface][DEBUG] get_account_data
[mullvad_api::access][DEBUG] Replacing expired access token
[mullvad_api::access][DEBUG] Fetching access token for an account

====================
Log: \\?\~\AppData\Local\Mullvad VPN\logs\frontend-renderer.log
====================
[error] Failed to update the location: 5 NOT_FOUND: no location was found
[verbose] Tunnel state: disconnecting
[verbose] Tunnel state: error
[verbose] Tunnel state: disconnecting
[verbose] Tunnel state: connecting
[verbose] Tunnel state: disconnecting

These are all that relates to the time after i woke the computer up.

[nihaals]

Running sudo killall mullvad-daemon fixes it for me (on macOS) whenever it happens, although my UI issues are slightly different (I think it's the same issue though, and it might be because of using a different OS).

[GibMeMyPacket]

Running sudo killall mullvad-daemon fixes it for me (on macOS) whenever it happens, although my UI issues are slightly different (I think it's the same issue though, and it might be because of using a different OS).

Termination on mullvad-daemon process in windows causes Mullvad app to stuck at Connecting to mullvad service Closing and opening mullvad doesn't fix that and i had to manually start MullvadVPN service in services.

[faern]

Yeah, the frontend is not responsible for spawning the system service/daemon. That has to be running, otherwise the GUI will just tell you it's waiting for the system service. It just works on macOS because the system automatically brings the daemon up again I guess.

[nihaals]

Restarting it through your service manager instead of manually killing the process is probably better too (e.g. systemd restart mullvad-daemon), I only started killing the process myself since that's what I originally found that worked and didn't look at the services.

[TESTER-sec]

The issue is that usually, when i put the computer to sleep while Mullvad has been connected (via SSH bridge), after that i wake the computer up, Mullvad is not getting connected and acting weird! It doesn't happen all the time, but i can pretty sure say half the time. https://i.imgur.com/5mcRMTk.gif The gif above shows the issue.

To get it fixed, i have to restart or close all processes of Mullvad via Process Hacker by searching Mullvad and selecting all processes in it.

I can confirm similar problematic behaviors induced after waking from Sleep on Windows 11 22H2. The weird behaviors are independent of the Mullvad VPN configuration. These intermittent behaviors occur with ANY settings configuration.

The very same issue shown in your linked GIF has occurred multiple times after waking the system from Sleep. Sometimes Mullvad will not connect at all despite no problem with network access. Sometimes the taskbar Manage Network Connections will show zero available networks. Sometimes the taskbar disable\enable Wifi will cause the GUI to freeze and crash. Sometimes there is a "flood" or "spamming" of Mullvad connection alerts during the waking-from-sleep process - as many as a few hundred. To fix these issues always requires a system reboot (a network reset does not work).

[dlon]

There's probably an issue with S0 sleep (i.e., "modern standby"). The system service does not get suspended, but the Electron app does. The latter gets flooded with state changes when waking up.

[TESTER-sec]

Issue report

Operating system: Windows 10

App version: 2022.5

Issue description

The issue is that usually, when i put the computer to sleep while Mullvad has been connected (via SSH bridge), after that i wake the computer up, Mullvad is not getting connected and acting weird! It doesn't happen all the time, but i can pretty sure say half the time. https://i.imgur.com/5mcRMTk.gif The gif above shows the issue.

To get it fixed, i have to restart or close all processes of Mullvad via Process Hacker by searching Mullvad and selecting all processes in it.

[SleepyAnubis]

I can confirm similar problematic behaviors induced after waking from Sleep on Windows 11 22H2. The weird behaviors are independent of the Mullvad VPN configuration. These intermittent behaviors occur with ANY settings configuration.

The very same issue shown in your linked GIF has occurred multiple times after waking the system from Sleep. Sometimes Mullvad will not connect at all despite no problem with network access. Sometimes the taskbar Manage Network Connections will show zero available networks. Sometimes the taskbar disable\enable Wifi will cause the GUI to freeze and crash. Sometimes there is a "flood" or "spamming" of Mullvad connection alerts during the waking-from-sleep process - as many as a few hundred. To fix these issues always requires a system reboot (a network reset does not work).

Having these same issues, Windows 10 22H2.

I find killing the client and mullvad-daemon then restarting the client does fix it though. Waking from sleep is definitely the trigger

[TESTER-sec]

Waking from sleep is definitely the trigger

It definitely is the trigger but there are those on Mullvad's support team\staff members that insist that it is not the trigger. Furthermore, they insist that it is the configuration and\or Windows and Mullvad is not responsible to fix it. The suggested fix I have been given by one particular Mullvad support team member is "Just use default configuration" (which does not solve the problem). In his mind, he does not care the users have paid for features, and he suggests not using them because he does not want to troubleshoot or fix the issue.

Another tactic is that they always ask if you have a security product installed. If you reply "Yes," they immediately shut down the troubleshooting and ticket. The reply in invariably "We have to assume the problem is not Mullvad but your security software "- or something along those lines. It is funny that every other VPN company does not do this, but Mullvad does it every single time.

[raksooo]

We've fixed a bunch of issues in our latest beta release. Please try it out and let us know if there are any improvements in regard of these issues: https://mullvad.net/download/beta