Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Firefox inbuilt VPN does not work with DNS over HTTPs enabled with Max Protection enabled

  • 2 Mbohovái
  • 1 oguereko ko apañuái
  • 21 Hecha
  • Mbohovái ipaháva jbr
  • Moĩporãmbyre

Trotter999
Trotter999

The VPN works if I Enable DNS over HTTPS using Default Protection, however if I select Max Protection and use Cloudflare, it does not work as it cannot resolve DNS.

If I disable the VPN or select Defualt Protection, DNS works again.

Windows 11 Pro 25H2 26200.8313 Firefox 150.0.1

The VPN works if I Enable DNS over HTTPS using Default Protection, however if I select Max Protection and use Cloudflare, it does not work as it cannot resolve DNS. If I disable the VPN or select Defualt Protection, DNS works again. Windows 11 Pro 25H2 26200.8313 Firefox 150.0.1
Mba’erechaha japyhypyre oñondivegua

Ñemoĩporã poravopyre

Thanks for the investigations. Normally there are some exceptions so it's interesting the features don't check each other's presence or mention the mitigation options in the error message. I've seen similar feedback on Mozilla Connect but wasn't able to find any bug filed on that topic, so there's now one by another reporter: https://bugzilla.mozilla.org/show_bug.cgi?id=2037364 if you want to follow any updates.

Thanks for reporting this!

Emoñe’ẽ ko mbohavái ejeregua reheve 👍 0

Opaite Mbohovái (2)

Trotter999
Trotter999 Porandu apoha

It looks like enabling the Firefox VPN and having DNS over HTTPs enabled could cause issues, hence why it does not work. Possibly Firefox should disable DNS over HTTPs when the VPN is active, and enable it again when the VPN is stopped.

jbr
jbr

Ñemoĩporã poravopyre

Thanks for the investigations. Normally there are some exceptions so it's interesting the features don't check each other's presence or mention the mitigation options in the error message. I've seen similar feedback on Mozilla Connect but wasn't able to find any bug filed on that topic, so there's now one by another reporter: https://bugzilla.mozilla.org/show_bug.cgi?id=2037364 if you want to follow any updates.

Thanks for reporting this!

Eporandumína

Nde eikéke nde mba’etepe embohovái hag̃ua ñe’ẽmondo. Ikatúpa, emoñepyrũ peteĩ porandu, ndereguerekói gueteriramo nemba’ete.