Closed brad-defined closed 1 year ago
The most recent version of Mobile Nebula changed the behavior here slightly, but we can at minimum improve wording here. Detecting a running VPN would probably be even better. At least currently, only one VPN can be active at a time:
There can be only one VPN connection running at the same time. The existing interface is deactivated when a new one is created.
-- https://developer.android.com/reference/android/net/VpnService.html
From Jeff Wright on Slack:
In case anyone else runs into this issue: if you have another VPN on an Android phone set to Always-on, Nebula Android will fail to connect with a VPN permissions error. Took me a bit to realize what was going on. Said something like "allow VPN permissions when requested" but permissions had never been requested.
definednetworking.slack.com/archives/CS01XE0KZ/p1681145123777509
We had a couple of reports in Slack about the Nebula app spinning on startup: https://nebulaoss.slack.com/archives/CRWJJM52B/p1654479054750989
Frank resolved it by ensuring there wasn't another VPN app marked 'Always On'.
https://nebulaoss.slack.com/archives/CS01XE0KZ/p1655050891622509
Sebastian reported the same thing, and removing another VPN that's "Always On" resolved it. https://nebulaoss.slack.com/archives/CS01XE0KZ/p1655052142562449