This thread was archived. Please ask a new question if you need help.
Android VPN no longer connecting
For no apparent reason the VPN on my Android phone has stopped connecting. It just stays on the "Connecting... Attempting to confirm connection" screen on my phone. I have cleared the cache and uninstalled and reinstalled. Nothing has helped. Please advise.
Have the exact same problem and reinstalling app did not resolve it. Worse, have made three requests to Mozilla Support with no adequate response. Next move is account deletion.Read this answer in context 👍 1
All Replies (8)
You can also do the following: Try signing out of the Mozilla VPN (you can do this by going to the gear icon on the top right of the application, then scrolling down to "Sign out"), uninstalling it, re-downloading it, and reinstalling it. The sign out is an important part of the process due to deleting some files that otherwise don't get purged.
Let us know if you keep having issues.
Have the exact same problem and reinstalling app did not resolve it. Worse, have made three requests to Mozilla Support with no adequate response. Next move is account deletion.
Here are the logs. It's repeating again and again. I've tried with and without IPv6
[2021-08-05T12:00:03.726] [info] - (VPNServiceBinder) - GOT TRANSACTION 1 [2021-08-05T12:00:03.726] [info] - (VPNServiceBinder) - Activiation Requested, parsing Config [2021-08-05T12:00:03.852] (VPNServiceBinder) - Stored new Tunnel config in Service [2021-08-05T12:00:03.863] [error] - (VPNService) - VPN Permission Already Present [2021-08-05T12:00:03.864] [error] - (VPNService) - VPN Permission Already Present [2021-08-05T12:00:03.864] [info] - (VPNService) - Permission okay [2021-08-05T12:00:03.864] [error] - (VPNService) - Tunnel already up [2021-08-05T12:00:04.145] [info] - (VPNService) - Go backend 219296a [2021-08-05T12:00:04.779] [info] - (VPNServiceBinder) - GOT TRANSACTION 4 [2021-08-05T12:00:13.905] [info] - (VPNServiceBinder) - GOT TRANSACTION 5
gleanEnabled -> true installationTime -> 2021-06-05T09:51:24.006 ipv6Enabled -> false languageCode -> nativeAndroidDataMigrated -> true previousLanguageCode -> fr systemLanguageCodeMigrated -> true telemetryPolicyShown -> true
ABI -> arm-little_endian-ilp32-eabi OS -> android OS Version -> 9.0 APP Version -> 2.4.0 Build ID -> 16270550
Signing out and reinstalling didn't help. Also on Android 9.
I just updated the Mozilla vpn app on my samsung 10 this morning, and it began having this issue. Have been unable to connect since the update...
Anyone seeing any improvement? The only thing I can think of that would have changed on my phone is that I used the Play Store to update my apps over the weekend. I didn't notice the problem till Monday. I scanned the apps that were updated but nothing jumped out as something that might affect networking.
Modified by laulau
Is this purely a UI problem? I was playing with Mozilla VPN and saw some interesting behavior.
I started the app and tapped the slide switch to turn on the VPN. The UI displayed the message "Connecting...Masking connection and location" and promptly got stuck as it has for the past two weeks. So I closed the UI. Curiously, I noticed the key icon and the VPN icon in the status bar (at the top of the phone screen) were still there. So I restarted the UI.
And this time it said "VPN is on. Secure and private" with the time counter incrementing. ???? Was the VPN really on? So I did a quick check with whatismyip.com to see where my connection was located. And it said Los Angeles, exactly where I had my VPN connection pointed! So it looked as if the VPN was connected and working. No "Attempting to confirm connection" message and then turning off.
So another data point. I have a support request filed with Mozilla and sent logs but haven't received any updates.
@laulau, I think you are correct, it is the UI. I had the same problem, tried closing the UI as you said, and when I reopened the app it was on, timer running. Looks like you have to close the user interface screen and then reopen to see it is already working. Definite tweak needed here! :)