Ky sajt do të funksionojë me kufizime, teksa bëjmë mirëmbajtjen e tij për të përmirësuar punën tuaj. Nëse një artikull nuk e zgjidh problemin tuaj dhe dëshironi të bëni një pyetje, kemi bashkësinë tonë të asistencës, e gatshme për t’ju ndihmuar, te @FirefoxSupport në Twitter dhe/r/firefox në Reddit.

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Firefox is unable to load any new websites

  • 6 përgjigje
  • 5 e kanë hasur këtë problem
  • 9 parje
  • Përgjigjja më e re nga davidbundy

more options

Every now and then after running normally for some time Firefox is unable to load any new websites. Instead I get the message "Verbinden..." (I use the German version of firefox). Internet Explorer works as usual when this happens. If I then close firefox I am unable to restart because the Firefox process is still running. Instead I have to stop Firefox running in Task Manager and then restart firefox. It usually works ok for while until it crashes again.

Every now and then after running normally for some time Firefox is unable to load any new websites. Instead I get the message "Verbinden..." (I use the German version of firefox). Internet Explorer works as usual when this happens. If I then close firefox I am unable to restart because the Firefox process is still running. Instead I have to stop Firefox running in Task Manager and then restart firefox. It usually works ok for while until it crashes again.

Krejt Përgjigjet (6)

more options

It is possible that your security software (firewall, anti-virus) blocks or restricts Firefox or the plugin-container process without informing you, possibly after detecting changes (update) to the Firefox program.

Remove all rules for Firefox and the plugin-container from the permissions list in the firewall and let your firewall ask again for permission to get full unrestricted access to internet for Firefox and the plugin-container process and the updater process.

See:

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Firefox/Tools > Add-ons > Appearance).

  • Do NOT click the Reset button on the Safe Mode start window.

Check the connection settings.

If you do not need to use a proxy to connect to internet then try to select "No Proxy" if "Use the system proxy settings" or one of the others do not work properly.

See "Firefox connection settings":

See also:

more options

You may also want to check for malware.

Microsoft Security Essentials is a good permanent antivirus for Windows 7/Vista/XP if you don't already have one.


Further information can be found in the Troubleshoot Firefox issues caused by malware article.

more options

It just happened again for the first time since my last post.

For Antivirus I use Notion Internet Security. Last week I set the firewall to allow Firefox automatically but that doesn't seem to have helped. I have done a couple of full scans since this problem first occured and it didn't find any malware.

At the time of the crash I had no other active programs running. Fiefox has also not updated since the last post. According to Task Station 68 other processes were running at the time. Who knows?

I am still at a loss to see what is causing this. It is difficult to analyse because only happens about once a week even though I use firefox every day.

more options

Norton you mean? Check with all the tools i suggested, can you reproduce in safe mode with networking.

more options

As a test you can try to load some web pages via Google Translate with a random source language.

more options

This problem has not occured in the last few weeks and may have been solved in the Firefox updates 25.0 or 25.0.1.

It was previously happening intermittently about once a day. I was never able to reproduce the problem reliably, so the original cause remains unknown.