Due to server slowness, downtime, and other issues, Eclipse will be moving to a more stable and efficient platform that should result in much better stability. There is no timeline for this yet, just want you to know what's happening with all the downtime and I have a plan to fix it.
Duke wrote: ↑08 Apr 2026, 10:13
I've noticed that some settings have been changed after updating from v149 beta to v149.0.2 like the warning before opening about:config, network.captive-portal-service.enabled or Safe Browsing.
Very annoying.
On top of that I've just noticed that R3dfox keeps on connecting to detectportal.firefox.com every time I open a new window (Ctrl+N) even though network.captive-portal-service.enabled is set to false.
This never ever happened with previous versions, not even with v149 beta
Correction:
It was there in v149 beta but not in v148.0.2 and previous versions.
I always backup before updating and I've just checked all of these versions.
Update:
Even worse, I have removed the http://detectportal.firefox.com/canonical.html URL from captivedetect.canonicalURL setting and it still connects to detectportal.firefox.com !
WTH is going on ?
R3dfox-CaptivePortal.png (14.34 KiB) Viewed 549 times
Duke wrote: ↑08 Apr 2026, 10:13
I've noticed that some settings have been changed after updating from v149 beta to v149.0.2 like the warning before opening about:config, network.captive-portal-service.enabled or Safe Browsing.
Very annoying.
On top of that I've just noticed that R3dfox keeps on connecting to detectportal.firefox.com every time I open a new window (Ctrl+N) even though network.captive-portal-service.enabled is set to false.
This never ever happened with previous versions, not even with v149 beta
Correction:
It was there in v149 beta but not in v148.0.2 and previous versions.
I always backup before updating and I've just checked all of these versions.
Update:
Even worse, I have removed the http://detectportal.firefox.com/canonical.html URL from captivedetect.canonicalURL setting and it still connects to detectportal.firefox.com !
WTH is going on ?
I had to set network.connectivity-service.enabled to false.
The NetworkConnectivityService will periodically connect to the same URL we use for captive portal detection, but will restrict its preferences to either IPv4 or IPv6.