Stuck on Checking connection; cannot reach ipv6.am.i.mullvad.net

[gen495]

Platform: macOS 14.7 Mullvad app: 2024.5 (2024-09-03) Browsers: Firefox 130.1, Firefox Nightly 132.0a1 Extension versions: 0.8.5, also seems to apply to 0.9.0

There is a possible confounding issue with how my system firewall is configured. The issue applies with Mullvad app ipv6 both on and off.

Issue description:

• clicking on the Mullvad extension icon gives this

it takes ~30-40 seconds to show the currently connected ipv4 proxy, and 10s more to show that the DNS leak tests failed. Looking at the extension in the network tab, from about:debugging#/runtime/this-firefox -> inspect, there's an issue connecting to ipv6.am.i.mullvad.net (NS_ERROR_NET_TIMEOUT)

• the same issues are present in the network monitor tab for https://mullvad.net/en/check, showing no ability to check for DNS leaks (NS_BINDING_ABORTED)
• clicking on the Mullvad extension icon while not connected to the proxy gives the same waiting delay, but clicking it again shows the connection information okay. (the connection to the ipv6 subdomain fails with NS_ERROR_UNKNOWN_HOST almost immediately)
• when disconnected from the proxy, it seems (with a single test) that the DNS leak checks succeed.

I can't seem to reach ipv6.am.i.mullvad.net on my host system either. Going into the browser proxy settings and disabling "Proxy DNS when using SOCKS v5" sometimes makes this work, but sometimes not. It may be worth noting that the SOCKS host IP is different across different browser instances. My host just uses 10.64.0.1.

This seemed to be working mostly fine (with some issues maybe) about a week ago; I'm not sure if updating the desktop app caused anything to break or work better.

The issue persisted:

• in my original browser profile, temporarily disabling extensions and enabling 0.8.5
• in some other completely fresh browser profiles, in both Firefox and Firefox nightly

I don't have more time to debug right now, sorry.

Workaround My UX issue of having to wait 30+ seconds to change location can be resolved by blocking requests to the ipv6 URL in devtools

[deadcombo]

I am experiencing the same issue. The workaround of blocking the ipv6 domain in the dev tools solves it as well for me.

[deadcombo]

@gen495 see #197 TL;DR reinstall the extension.

To clarify, I experienced both the issues described here and #197 simultaneously, including Mullvad Extension being set as controlling proxy settings in about:preferences.

EDIT: I'm wrong, sorry. After a browser restart the ipv6 issue is back, guess the filter was still on. It disables Leta every once in a while as well.

[MrChocolatine]

I am having the same issue, the extension stuck on Checking connection:

I am using through Mullvad Browser, which means I have not changed the browser default configuration.

Strangely, in the Proxy tab of the extension I get the message Connect first to Mullvad VPN (WireGuard) to use the proxy. while I am connected to the VPN with WireGuard: