Skip to content

CavsPlace by Cavalier Broadband

Narrow screen resolution Wide screen resolution Auto adjust screen size Increase font size Decrease font size Default font size

Got wireless?

If you have a personal router and are connecting it to our network, wait! Please visit the appropriate section for a "how-to" first! Incorrectly configured or connected routers are one of the top reasons your connection gets suspended.

Going somewhere?

When going on break, please take a minute to look over the "best practices" of what to do when leaving on break .

Need help?

It's always a good idea to have this checklist handy. Over 90% of the calls we get from folks who can't access the internet are "self solved" here.
Home arrow Support arrow Frequently Asked Questions arrow Firefox :: Connection Interrupted
Firefox :: Connection Interrupted PDF Print E-mail
Written by Wahoo Prime   
Monday, 29 September 2008

Do you get the following error message surfing the Internet in Firefox?

Connection Interrupted | The connection to the server was reset while the page was loading.

If so please follow these simple steps to see if the problem is with some Firefox settings.

In Firefox, type: "about:config" in the address bar then, type in "ipv6" in the top filter bar if the value = "false", right click and select "toggle".

the value now should change from "false" to "true".

If you need more technical information, proceed to read below this line for a more mundane explanation.

What is this setting and why does it matter?

We also have the following article:

http://www.cavsplace.net/content/view/52/27/

Up until updating to Firefox 3.x this was not an issue if you disabled IPv6 on your computer. Mozilla developers perhaps ought to look at querying the network stack before trying to use a disabled or unused protocol in a future update. 

When surfing the Internet with an IPv4 address , Vista, MAC and other platforms sometimes try to prefer IPv6 over IPv4. If there is no IPv6 DNS server responding to your queries, then obviously the browser "should" use IPv4, but Firefox, like a lot of over things you use, is software, and sometimes someone in another timezone makes a decision when they put out an update. the article above refers to disabling IPv6 entirely, but even when it is, a browser misconfiguration can still cause this problem.

It's problematic that Firefox does not look at the protocol stack and change its configuration accordingly.  Right now, manually changing your Firefox config is perhaps the quickest and easiest solution.

 network.dns.disableIPv6;true

So even if your IPv6 stack is disabled or not in use, the browser is doing its own thing, which causes this issue.

 

Last Updated ( Monday, 29 September 2008 )
 
Next >