Oh nice, I actually didn’t know that. Pretty nice feature.

I don’t think there is split tunneling in the browser add-on, not exactly sure what you mean.

See my update in the main post, please check if you also had split tunneling enabled. Still a weird behavior but now it is narrowed down to this feature.

See my update in the post, now everything makes a little more sense and it is for sure related to the split tunneling feature.

good to hear that I am not the only one and it is reproducible

again, this doesn’t make sense as the NordVPN Firefox extension is using the same IP address ranges. Also I tried different VPN server in different regions, even the “IP obfuscating” ones

No I am not sure, I don’t really see any error message, just a timeout. Not sure how an error of the DNS resolver looks like compared to any error caused by a timeout. However the DNS resolution should indeed be returning a different error, at least when entering a random non existing URL Firefox returns “server not found” instead of “problem loading page”(and NS_ERROR_NET_TIMEOUT in network debugging consoel). But what else could it be? It is so strange that the combination of Firefox and NordVPN extension does work, so it seems that the routing through the vpn network generally works, so it actually has to be something with the windows client interaction I guess.

That doesn’t make sense, why would it only cause google.com to break? Also I tried turning it off completely, didn’t work.

you are my hero for today 🤗