0

Firefox extension not working correctly (Mac)

Example: I block all Google, Slashdot and a heap of others,

A few weeks ago I clicked a link which lead to Slashdot - and it loaded Slashdot.
What I should have see in a connection error.
Just now I tried to go to google.com - and it too loaded.

In Firefox settings > Configure how Firefox connects to the internet > I have my Automatic Proxy set to my nextdns ID - https://dns.nextdns.io/xxxxxx
I have clicked Reload, but I can still see blocked sites, they can still track me.

If I use the Mac app, which uses the same config, then what I want blocked, is actually blocked.

The problem is that Firefox is my daily browser. I also use Firefox Developer Ed (with containers), Edge and Brave for certain specific things and that usage is low. Using the App extends the blocking across all the browsers which is undesirable as I have to quit the App, and then have no control over what is happening in Firefox.

Am I correct in thinking this is a Mozilla issue?

5 replies

null
    • Mark_Riley
    • 7 mths ago
    • Reported - view

    Figured it out, and it's Firefox being confusing.

    I followed the all the steps in Firefox Setup as detailed by NextDNS

    1. Open Preferences.
    2. Scroll down to the Network Settings section and click on Settings.
    3. Scroll down and check Enable DNS over HTTPS.
    4. Select Custom, enter https://dns.nextdns.io/xxxxxx and click OK.
    5. Enter "about:config" in the address bar (and click on I Accept the risk! if asked).
    6. Set network.trr.mode to 3.

    This did NOT work.

    What I had to do was

    1. Open Preferences
    2. Click Privacy & Security
    3. Scroll down to Enable DNS over HTTPS using
    4. Choose Increased Protection or Max Protection and in whatever you choose, click Custom
    5. Enter your https://dns.nextdns.io/xxxxxx

    And now it works.

    So what Network Settings is doing I have no idea.

    Anyway, I'm happy :)

      • R_P_M
      • 7 mths ago
      • Reported - view

       The Firefox settings have changed since the NextDNS setup steps were written. It feels like they keep changing it every year (exaggeration).

      • Will_Tisdale
      • 7 mths ago
      • Reported - view

       It's actually NextDNS having old instructions.

      Firefox changed the way secure DNS is set a while ago and the instructions are outdated.

      • Mark_Riley
      • 7 mths ago
      • Reported - view

         Thanks both! Hopefully anyone else finds this solution - until nextDNS update their instructions, and Mozilla then makes more changes :)

      • NextDNs
      • 7 mths ago
      • Reported - view

      We will update the instructions shortly. Thanks for the heads up.

Login to reply

Content aside

  • 7 mths agoLast active
  • 5Replies
  • 227Views
  • 4 Following