Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

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 not loading any websites

  • 4 përgjigje
  • 0 e kanë hasur këtë problem
  • 172 parje
  • Përgjigjja më e re nga Colin Bird

I have just installed Firefox on a new iMac, running MacOS 15.2. Firefox will not load any of the websites I have tried, whereas Safari and Chrome do. I have cleared the History and also set "No proxy" but loading still fails.

I have just installed Firefox on a new iMac, running MacOS 15.2. Firefox will not load any of the websites I have tried, whereas Safari and Chrome do. I have cleared the History and also set "No proxy" but loading still fails.

Zgjidhje e zgjedhur

Problem solved, by pure chance! In the process of fixing an unrelated issue, I had to install Apple's Rosetta software (my previous iMac was rather old: 2013). When I next checked Firefox, it was working as normal, so the problem must have been compatibility-related.

Lexojeni këtë përgjigje brenda kontekstit 👍 0

Krejt Përgjigjet (4)

Should I raise this concern with Mozilla as a problem? If so, how do I do that?

Hi Colin

Is there any error message shown?

Hi Paul, No, the dot to the left of the tab name goes side-to-side for a while then stops, leaving a sand-timer icon but the pane remains blank. Being new to this forum, I replied to my original question, then discovered how to reply from the email you sent. In the meantime, one of my test websites did actually load - after a long delay - but was then entirely unresponsive. Thanks for your help - Colin

Zgjidhja e Zgjedhur

Problem solved, by pure chance! In the process of fixing an unrelated issue, I had to install Apple's Rosetta software (my previous iMac was rather old: 2013). When I next checked Firefox, it was working as normal, so the problem must have been compatibility-related.