when attempting login to Mozilla VPN on a new desktop device, logging in successfully in my browser did not change state within the Mozilla VPN app, which continued "waiting for sign-in".
versions
- mozillavpn 2.29.0 (2.202506162352)
- macos sequoia 15.5
- firefox 141.0.3 (aarch64)
solution
to fix this, i temporarily disabled my ad blocker for vpn.mozilla.org to complete login.
cause
i use ublock origin and i had enabled the "block outsider intrusion into lan" filter set.
apparently, the mozilla VPN login makes a cross-domain request to localhost at 127.0.0.1, and was interrupted by this filter.
maybe Mozilla VPN should not rely on a cross-domain request to log in
i think it is generally not a great pattern, and also, many people will be running filter lists or blocking this kind of request for security reasons and privacy reasons and by default someday
not solutions
i am posting this github issue so that my particular cause and solution is documented somewhere.
annoyingly, lots of discussion contained little information and few suggestions other than 'contact support, the solution they give you is easy'
clearly similar issues may happen for several reasons, and vary depending on platform and version.
github issues that did not help (but at least made it clear that the causes could be various)
mozilla support questions with an accepted answer containing no information:
mozilla support articles that were not helpful
reddit threads with no solutions
┆Issue is synchronized with this Jira Task
when attempting login to Mozilla VPN on a new desktop device, logging in successfully in my browser did not change state within the Mozilla VPN app, which continued "waiting for sign-in".
versions
solution
to fix this, i temporarily disabled my ad blocker for vpn.mozilla.org to complete login.
cause
i use ublock origin and i had enabled the "block outsider intrusion into lan" filter set.
apparently, the mozilla VPN login makes a cross-domain request to localhost at 127.0.0.1, and was interrupted by this filter.
maybe Mozilla VPN should not rely on a cross-domain request to log in
i think it is generally not a great pattern, and also, many people will be running filter lists or blocking this kind of request for security reasons and privacy reasons and by default someday
not solutions
i am posting this github issue so that my particular cause and solution is documented somewhere.
annoyingly, lots of discussion contained little information and few suggestions other than 'contact support, the solution they give you is easy'
clearly similar issues may happen for several reasons, and vary depending on platform and version.
github issues that did not help (but at least made it clear that the causes could be various)
mozilla support questions with an accepted answer containing no information:
mozilla support articles that were not helpful
reddit threads with no solutions
┆Issue is synchronized with this Jira Task