VPN goes into no signal state but device does not lose internet connection and location is still masked by the VPN

[data-sync-user]

Description

VPN 2.16 on Android goes into No Signal state a few moments after being turned On. In spite of the error message, the user’s device does not lose internet connection and IP location is still being masked when confirming on mullvad site. Issue occurs on single hop and multihop, as well when using cellular network or Wifi.

Does it impact functionality or aesthetics? Aesthetics Does this endanger users? What would be compromised and how likely is the threat? How annoying is this for affected users? (Think about how much 'in the way' this is, relative to what the user is trying to do) Visual indication that there is an error in the VPN gives the impression that it is not working correctly. Does it degrade the user experience significantly? No Is it legally sensitive? No

Centrality Is it on a core user journey or on a secondary one? Core journey

Technical Information

Platform: Android 8, Android 9 FX product: Mozilla VPN Version: 2.16 Region/Languages Network type (Mobile/Wifi)

Steps to Reproduce

1. Install Moz VPN
2. Select desired location
3. Turn VPN On to connect
4. Monitor VPN’s connection state

Actual Results

VPN shows No signal error

Expected Results

VPN should show VPN is On with no error messages

┆Issue is synchronized with this Jira Bug ┆Reporter: Juan Zapata

[data-sync-user]

➤ Magdalena Schwaighofer commented:

[^MZ logs Android.txt]

I have requested the complete logs from this user multiple times, but they were somehow unable to send me the complete file. It looks like the last part of the logs is missing, but I wasn't able to get more from this user sorry

[data-sync-user]

➤ Magdalena Schwaighofer commented:

I received a set of logs on 2.16 for this issue

[^logs_Android_nosignal.txt]

[data-sync-user]

➤ Juan Zapata commented:

Attaching another set of logs

[^MozVPN-Android.txt]

[data-sync-user]

➤ Juan Zapata commented:

Lesley Norton Would you require more logs for this issue? So far we only have 10 user reports and 1 user reported that after some time, the issue went away on its own

[data-sync-user]

➤ Magdalena Schwaighofer commented:

We continue to get user reports on 2.17 - so far we have 21 users reporting the “no signal” error on Android

Latest set of logs on 2.17 attached

[^android2.17_nosignal.txt]

[data-sync-user]

➤ Magdalena Schwaighofer commented:

one user provided another set of logs on 2.18 - it looks incomplete, but that is the best they could provide

[^MZ logs.md]

[data-sync-user]

➤ Vinoo Cherian commented:

Logs show the same socket binding error as https://mozilla-hub.atlassian.net/browse/VPN-5732 ( https://mozilla-hub.atlassian.net/browse/VPN-5732|smart-link ). Juan said this always repros on some Android devices. Error: bind error: Permission denied

[hazelybell]

This is happening on Debian (I built it myself):

[01.01.2024 13:24:10.501] (PingHelper) Debug: Sending ping seq: 163
[01.01.2024 13:24:10.502] (DnsPingSender) Error: Attempted to send DNS ping, but socket is invalid.
[01.01.2024 13:24:11.502] (PingHelper) Debug: Sending ping seq: 164
[01.01.2024 13:24:11.502] (DnsPingSender) Error: Attempted to send DNS ping, but socket is invalid.

[data-sync-user]

➤ Magdalena Schwaighofer commented:

Some device information provided by 2 of my users:

• Samsung Galaxy S7 Smartphone. Android 8.0.0
• Samsung Galaxy S8 smartphone - SM-G950F - Android 9

[data-sync-user]

➤ Juan Zapata commented:

Affected devices from other user reports:

Samsung SM-J337A, Android 9.0

Samsung Tab A – SM-T580, Android 8.1

[data-sync-user]

➤ Magdalena Schwaighofer commented:

another device: Huawei Y5 2019; EMUI 9.10 446 ; Android 9

[data-sync-user]

➤ Magdalena Schwaighofer commented:

Another device: HUAWEI P30 Pro ; Model VOLG-L29 ; Android 9.0

[data-sync-user]

➤ Magdalena Schwaighofer commented:

adding another smartphone: Samsung Galaxy S10e Android_Version 9, Kernel - Version 4 14 85-17063867 . One UI-Version

[data-sync-user]

➤ Juan Zapata commented:

Adding more devices affected with this issue:

Galaxy S7, Android 8 Samsung J7, Android 9 Samsung Galaxy A5, Android 8 Sansubg T580UD Samsung Note 8 Android 9 HUAWEI Y6 Android 9

[data-sync-user]

➤ Juan Zapata commented:

59 users affected since originally reported in V 2.16.

2 Users reports on 2.21

[data-sync-user]

➤ Beatriz Rizental Machado commented:

I can reproduce this 100% of the time on Linux. I filed it in a separate ticket https://mozilla-hub.atlassian.net/browse/VPN-6114 ( https://mozilla-hub.atlassian.net/browse/VPN-6114|smart-link ) .

I see in the logs here:

[13.11.2023 13:27:47.367] (DnsPingSender) Error: Attempted to send DNS ping, but socket is invalid. [13.11.2023 13:27:48.319] (DnsPingSender) Error: Attempted to send DNS ping, but socket is invalid.So it looks like the same thing.

[data-sync-user]

➤ Basti commented:

Looks similar to the issue here: https://mozilla-hub.atlassian.net/browse/VPN-6267 ( https://mozilla-hub.atlassian.net/browse/VPN-6267|smart-link )

Marking this as in progress, can we re-visit this when 2.22 is live?

[data-sync-user]

➤ Santiago Andrigo commented:

Removing 2.22 as fixVersion as that version is live and I believe this fix is not there.