Proton vpn

rbb

Hello,
I've not experienced this issue. Proton has consistently worked well with Graphene from my own experience.

ProfessorMonks

I was also having a terrible time using Proton VPN, however this seems to have resolved itself when I enabled "Always-on VPN" and "Block connections without VPN" which forces it to reconnect to a server. Having only "Always-on VPN" enabled appeared to not trigger connection failures to reattempt a connection quickly enough resulting in long periods (upto an hour) without a network connection.

n3t_admin Maybe if people started leaving on masse they would do something about it.

I agree with this sentiment, however I and perhaps others feel compelled to stay due to long term upfront commitments. For example, I have secured a 24 month plan with Proton and in return received a steep discount. Mullvad is certainly top tier, and I would like to return to them at my next opportunity.

rbb

Is it not worth considering that it may be a device specific issue rather than a Proton issue? If it were in fact a Proton issue, would it not stand to reason that it would affect all users equally?

Byteang3l

Vomitorius sometimes VPN profiles can get corrupted by updates, leading to an endless attempt to establish a connection. The best method I've seen that works long term is to go into the VPN settings where it shows the options for auto connect VPN and block connections without VPN, delete the VPN profile there, force stop the app and clear cache, and try to re-establish the connection then, it'll prompt to generate a new VPN profile and should work fine from there.

Vomitorius

Byteang3l did not help, tried already.

krysor

Vomitorius Have you tried using the "Report an issue" option in the ProtonVPN app and provide some logs? I received a comprehensive reply on my first attempt.

n3t_admin Mullvad has the same issue. In fact, it was a Mullvad employee who made the inital Bug report in the AOSP issue tracker.

That's the reply I received 3 weeks ago from the Proton VPN support:

Hi,

Thank you for reaching out to us.

We want to inform you that this issue is primarily related to Android rather than Proton VPN. We have reported it to Google for further investigation: https://issuetracker.google.com/issues/441315112

In the meantime, the only solution we recommend is to reboot your device when the issue occurs.

We are also monitoring this situation on our end, and I will provide you with updates as soon as they become available.

I apologize for any inconvenience this may have caused.

Have a great day!
Kind regards

Vomitorius

krysor yes. Support only replied with pointless suggestions, like changing protocol or similar shit I already did before and INFORMED him about it.
What I hate about Proton support it's their inability to confess they do not know the issue solution, but problem is known and they work towards it. Instead of that, we keep conversating hollow and pointless discussions and useless tries. Annoying.

krysor

Vomitorius It's an AOSP issue

Vomitorius

krysor this brings more clarity than proton support.

krysor

Vomitorius I honestly don't know why. I feel like the support usually gives the solutions to the most common problems that are usually user side.

Last few times I tried to properly provide the logs including the ones from the app system settings and I got replies straight from their developers and these were usually on point.

But another time I messaged them about Proton Pass extension not working in Safari in Lockdown Mode after update to MacOS 26 Tahoe. I didn't know how to provide the logs. After going back and forth and having found the same issue reported on Reddit, their developer replied to me saying they're aware of it and are working on it.

Vomitorius

krysor obviously their weird inner rules maybe does not allow to forward issue faster to upper tier, they must circlejerk with issue first.

krysor

Vomitorius BTW I am a Proton Drive Plus subscriber so maybe they give a slightly higher priority to my requests compared with free users? Pure speculation. Could all be coincidental.

Vomitorius

krysor never was a free user, always paid sub.

Gossygos

I had this problem yesterday, not sure it was triggered by an update, it just hung "connecting". The only fix was to reboot the phone. I'm using the free version so can't really complain. Apart from this proton has been the most reliable VPN I've used (including my paid PIA)

VAULT

Hmmmm... I ALWAYS run Proton VPN on my P9PXL and it NEVER happens to me... BUT I only have main profile... hmmmm...

graphny

Successfully connecting to Tor and then switching back to ProtonVPN always works for me. It might also work with other VPNs, but I don’t have a second VPN app to confirm. Works in Owner profile and Secondary profile.
Edit: I use InviZible Pro for Tor.

graphny

https://discuss.grapheneos.org/d/28204-proton-vpn-cant-connect-after-it-updates/9

https://github.com/mullvad/mullvadvpn-app/issues/8488#issuecomment-3272143606

For users facing this problem, as mentioned in our report to google there are multiple ways to fix the broken VPN profile, do one of the following and you will be able to connect again:

Restarting the phone.

Switching to another VPN profile (make sure it is established) and then reconnect using the original, previously faulty, VPN.

Uninstall and reinstall the VPN app

Vomitorius

graphny so? I know there is an issue by myself. I know rebooting solves the problem aswell. The thing is it should not be like that.

W1zardK1ng

Vomitorius Not a Proton issue i think.
I have exact same issue with windscribe config with WG Tunnel. Same issue on pixel tablet and and 6a.

graphny

Vomitorius Not having the issue is best. I posted to let people know rebooting is not the only fix.