[BUG] Session Android doesn't connect when VPN is on

[Johnleed41]

Code of conduct

• I have read and agree to adhere to the Code of Conduct

Self-training on how to write a bug report

• I have learned how to write a bug report

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I am currently using the latest Mullvad VPN on android. If the VPN is on then session fails to connect. Waiting several minutes doesn't help.

This is an issue which appears to be caused by enabling Multihop

Expected Behavior

It should connect as the FAQ says VPNs should connect

Steps To Reproduce

1. Turn on Mullvad VPN
2. Open Session app
3. Wait but the connection status never goes green
4. Disable Mullvad VPN
5. Session swiftly connects

How to reproduce by changing Mullvad settings:

1. If Multihop is on, session app fails to connect
2. As soon as Multihop is toggle off, session app can connect

Android Version

Android 16

Session Version

1.29.1

Anything else?

No response

[Johnleed41]

It appears one of the settings in Mullvad is causing this issue. Will test and get back

[Johnleed41]

The culprit appears to be Mullvad's option:
Multihop

Description as per the app:
Multihop routes your traffic into one WireGuard server and out another, making it harder to trace. This results in increased latency but increases anonymity online.

Could this be tester and/or patched as this feature is quite important for some users who use it? Thanks!

[Arcterus]

I have the same issue with a different multi-hop VPN. It sometimes works and sometimes doesn't. AFAICT the logs are just saying all the HTTP requests are failing to connect.

[pottsandpans]

Thanks for raising, this issue is being tracked internally via SES-5056.