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

Támogatás keresése

Kerülje el a támogatási csalásokat. Sosem kérjük arra, hogy hívjon fel egy telefonszámot vagy osszon meg személyes információkat. Jelentse a gyanús tevékenységeket a „Visszaélés bejelentése” lehetőséggel.

További tudnivalók
A témacsoportot lezárták és archiválták. Tegyen fel új kérdést, ha segítségre van szüksége.
Megoldva Archivált

When I connect to a server that isn't responding, Firefox doesn't display any error messages. It just hangs there.

hedera megválaszolva
hedera

I've had two incidents recently where FireFox would simply display a blank screen. In both cases when I tried the same web site in Google Chrome, Chrome displayed an error message that helped me solve the problem. Firefox just sits there blankly. I can't find a box to check in FireFox options that says, "display system error messages." How do I do this? I prefer FireFox to Chrome, but if FireFox won't tell me what's wrong, I can't use it. This problem cost me over a week in a recent site upgrade.

I've had two incidents recently where FireFox would simply display a blank screen. In both cases when I tried the same web site in Google Chrome, Chrome displayed an error message that helped me solve the problem. Firefox just sits there blankly. I can't find a box to check in FireFox options that says, "display system error messages." How do I do this? I prefer FireFox to Chrome, but if FireFox won't tell me what's wrong, I can't use it. This problem cost me over a week in a recent site upgrade.

Összes válasz (2)

Kiválasztott megoldás

A possible cause is security software (firewall) that 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 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:

This seems to have fixed it, at least for now, thanks for the tip.