How do I inhibit the startup connection to 82.103.134.102?
I've tried configuring all update.enabled to false in about:config, created {73a6fe31-595d-460b-a920-fcc0f8843232}.update.enabled false, and unchecked the ABE boxes in
Noscript-Options-Advanced-WAN IP and Enable ABE with no luck.
Thankee kindly.
Inhibiting startup connection to 82.103.134.102
-
Guest
Inhibiting startup connection to 82.103.134.102
Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20100101 Firefox/11.0
Re: Inhibiting startup connection to 82.103.134.102
try
about:config -> set noscript.ABE.wanIpAsLocal to false, then set empty value for noscript.ABE.wanIpCheckURL
about:config -> set noscript.ABE.wanIpAsLocal to false, then set empty value for noscript.ABE.wanIpCheckURL
*Always* check the changelogs BEFORE updating that important software!
Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20100101 Firefox/17.0
-
Guest
Re: Inhibiting startup connection to 82.103.134.102
No luck, but after some rooting around, I discovered that it's the initial version check that's causing it. Setting all the update.enabled stuff to false fails to inhibit it I think because noscript starts out with noscript.version blank and noscript.subscription.lastCheck set to a big negative number.
I realized this was what was happening when I inadvertently let one through while checking back here and it suddenly stopped doing it. I then compared the prefs.js with a previous one and discovered that what changed was that noscript.version had been set to "2.6.8.17" and noscript.subscription.lastCheck had been deleted. I verified that was it by reverting to an older prefs.js, adding the version, deleting the lastCheck, setting the update.enableds to false, and setting noscript.subscription.checkInterval to 999999999 for good measure, and sure enough, no more connections on startup.
Thanks
I realized this was what was happening when I inadvertently let one through while checking back here and it suddenly stopped doing it. I then compared the prefs.js with a previous one and discovered that what changed was that noscript.version had been set to "2.6.8.17" and noscript.subscription.lastCheck had been deleted. I verified that was it by reverting to an older prefs.js, adding the version, deleting the lastCheck, setting the update.enableds to false, and setting noscript.subscription.checkInterval to 999999999 for good measure, and sure enough, no more connections on startup.
Thanks
Mozilla/9.3 (Windows NT 5.1; rv:93.0) Panda/20330621 Firefox/93.0