Mozilla VPN cannot be turned ON after renaming the app on Windows/macOS

[data-sync-user]

Important details:

• quitting and reopening the app does not solve the issue  (even after allowing access to the app through the Firewall). The issue is resolved after returning to the original name (Mozilla VPN);
• reproducing on macOS as well;

Affected versions:

• 2.18.0 (2.202310241849)

Tested Platforms:

• Windows 10/11;

Prerequisites:

• Have Mozilla VPN app installed and open;
• Have a Mozilla account with an active subscription;
• Be signed in;  

Steps to reproduce:

1. Navigate to Mozilla VPN installation path and rename the Mozilla VPN app (the .exe file);
2. Attempt to turn ON the VPN and observe the behavior;

Expected result:

• The VPN is turned ON;

Actual result:

• The VPN cannot be turned ON;

Notes:

• See the attached video and logs;
• Tried the same scenario while using the NordVPN, and the client can connect after renaming the app;

┆Issue is synchronized with this Jira Bug ┆Reporter: Bianca Hidecuti

[data-sync-user]

➤ Santiago Andrigo commented:

Can reproduce (but still Lowest priority)

[data-sync-user]

➤ Valentina Virlics commented:

I would advocate for this ticket’s priority to go up, because:

• app name could be easily changed by mistake;
• user trying to turn ON the VPN has no idea what happens and why he cannot turn ON the client;
• other VPNs work;

Thank you!

[data-sync-user]

➤ Santiago Andrigo commented:

I don’t believe there is a significant chance that a user will both locate the binary file and then accidentally rename it.

[data-sync-user]

➤ Bianca Hidecuti commented:

Update: I am able to reproduce this on macOS 14 as well (using a testing device where I am able to rename the app). Updated the ticket accordingly.

[data-sync-user]

➤ Valentina Virlics commented:

“qa-wishlist” reasons:

• other VPNs don’t have this issue;
• technical users can easily locate and change an app name ;