Mozilla will shut down Pocket’s services on July 8, 2025. At that time users will no longer be able to access the Pocket website, apps and API. You can export your saved items and API data until October 8, 2025 before they are permanently removed. For more information, see this article.

Avatar for Username

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

"detect portal"

  • 2 replies
  • 26 have this problem
  • 360 views
  • Last reply by GaryDev

GaryDev
GaryDev

Did a recent upgrade from 49 something 54.0.1, and now I am getting traffic (according to my logs and some Wire-shark sniffing) that is going to a "detect portal" at firefox dot com. This is going out as a "DNS query" according to the sniffer... and this causes some response traffic where a CNAME is being set for a couple of akamai dot net addresses (in my case, its a1089.d.akamai.net at 24.244.3.32 and a1089.d.akamai.net at 24.244.3.18.

This is traffic I do not want, and I have a ton of the "akamai dot net" addresses blocked (mostly from the OS boot process, which also goes out to do a DNS query and returns many other CNAME aliases. And yes, I do have my SHAW ISP's DNS servers defined so I am not even sure why THAT happens..

Anyway, getting a dozen or so outgoing attempts that are being blocked by PeerBlock. Not sure why this is needed, and I would like to be able to disable this, or turn it off totally...

Solutions? :) Thanks kindly in advance.

Did a recent upgrade from 49 something 54.0.1, and now I am getting traffic (according to my logs and some Wire-shark sniffing) that is going to a "detect portal" at firefox dot com. This is going out as a "DNS query" according to the sniffer... and this causes some response traffic where a CNAME is being set for a couple of akamai dot net addresses (in my case, its a1089.d.akamai.net at 24.244.3.32 and a1089.d.akamai.net at 24.244.3.18. This is traffic I do not want, and I have a ton of the "akamai dot net" addresses blocked (mostly from the OS boot process, which also goes out to do a DNS query and returns many other CNAME aliases. And yes, I do have my SHAW ISP's DNS servers defined so I am not even sure why THAT happens.. Anyway, getting a dozen or so outgoing attempts that are being blocked by PeerBlock. Not sure why this is needed, and I would like to be able to disable this, or turn it off totally... Solutions? :) Thanks kindly in advance.

Chosen solution

hi, this is part of captive portal detection which was introduced in firefox 52 - in order to disable that, enter about:config into the firefox address bar (confirm the info message in case it shows up) & search for the preference named network.captive-portal-service.enabled. double-click it and change its value to false.

Read this answer in context 👍 11

All Replies (2)

philipp
philipp
  • Moderator

Chosen Solution

hi, this is part of captive portal detection which was introduced in firefox 52 - in order to disable that, enter about:config into the firefox address bar (confirm the info message in case it shows up) & search for the preference named network.captive-portal-service.enabled. double-click it and change its value to false.

GaryDev
GaryDev Question owner

Perfect. Thanks very much.. I did do the 'config' and searched for 'detect' and noticed several things "captive" related but didn't find the on/off switch. Guess I didn't dig deep enough. :)