Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Why won't Firefox 7 stay on a website?

  • 4 antwoorden
  • 1 heeft dit probleem
  • 1 weergave
  • Laatste antwoord van jlykins

more options

When I go to a website, the page loads normally and seems to work for about 3-5 seconds. Then Firefox goes into connection mode--I don't know what it is trying to connect to. It can't find the page its looking for and I get redirected to a 404 error page with a list of websites. My homepage doesn't do this.

Just to be clear, this happens on every website making Firefox completely unusable
When I go to a website, the page loads normally and seems to work for about 3-5 seconds. Then Firefox goes into connection mode--I don't know what it is trying to connect to. It can't find the page its looking for and I get redirected to a 404 error page with a list of websites. My homepage doesn't do this. Just to be clear, this happens on every website making Firefox completely unusable

Alle antwoorden (4)

more options

Type in the address bar

about:config

Accept the warning.

In the page that appears, in the Filter box, type

network.http.max-connections

Change the value to 32 (which is probably set to 256 in your case).

Close that page.

Restart the browser.

Bewerkt door amkeew op

more options

Thank you for your swift response. I've been having problems with firefox losing the internet and permanently connecting, so from the help system I learned to change http.network.max-connections from 256 max to 48 max. This solved the firefox freezing problem, but this web page jumping problem started about 12 hours later. I changed the http max-connections from 48 to 32, but the problem remains. Thank you for the help.

more options

Disable all the add-ons one by one and see which is causing this problem.

more options

It was the Apture 2.0 add-on. Thank you very much for the fast and effective help.

J Lykins