Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Learn More

Server Not Found error only affects Firefox

  • 10 odpovědí
  • 1 má tento problém
  • 4 zobrazení
  • Poslední odpověď od John99

more options

Was using v36 with no problems. Added a password to my WinXP Pro user account, system began updating file securities The file updates unexpectedly quit. Upon restart and logging into Windows, Firefox now shows "Server Not Found" error for every site (Chrome can get to same URLs) Did not actively update any firewall, security scanners, or connectivity settings Have tried different proxy settings and all the suggestions at https://support.mozilla.org/en-US/kb/firefox-cant-load-websites-other-browsers-can to no avail. Even tried to see if calls were being made through Fiddler -- they are not. Need more suggestions.

please help.

Was using v36 with no problems. Added a password to my WinXP Pro user account, system began updating file securities The file updates unexpectedly quit. Upon restart and logging into Windows, Firefox now shows "Server Not Found" error for every site (Chrome can get to same URLs) Did not actively update any firewall, security scanners, or connectivity settings Have tried different proxy settings and all the suggestions at https://support.mozilla.org/en-US/kb/firefox-cant-load-websites-other-browsers-can to no avail. Even tried to see if calls were being made through Fiddler -- they are not. Need more suggestions. please help.

Všechny odpovědi (10)

more options
more options

It didn't help -- UGH!

All works fine in SAFE MODE with NETWORKING

more options

Tried everything...could not get it going... reinstalled v35 and problem is gone!

Turned off auto install updates

A

more options

It is likely it is some other program is interfering if it works in Windows Safe Mode but not otherwise.

Possibilities include some program in an autostart folder. Some security related program, or some form of malware.

You mention fiddler what is that ?

If it is the software the above link relates to, that seems likely to be capable of adversely affecting Firefox's operation.

more options

Checked for malware -- none found Fiddler is simply an HTTP monitor -- worked w/ FF since v1 Believe all security is off... have AVG Free but cannot find a user interface

Oh well -- getting pages served on v35 :)

A

more options

I note downgrading helps you but it is not a good solution. The old outdated version increase risk to your computer and your personal data.

The problem probably will not go away by itself and you could get stuck on an ever more out of date version of Firefox.

Trying the steps suggested in /questions/1049998 may help. You would be safer temporarily using ESR portable, and working to troubleshoot issues with Firefox 36, and if necessary filing a bug. However you do need to first of all investigate why it works in Windows SafeMode.

more options

disabling the .http2 configs did not work

is there a work around for the DNS "ANY" issue for me to try? I'll search.

A

more options

Try with Windows firewall and AVG firewall disabled.

more options

Do not have AVG installed and I did disable Windows Firewall. Neither helped to my dismay....

I cannot believe none of these fixes are working for me.

more options

AG said

disabling the .http2 configs did not work is there a work around for the DNS "ANY" issue for me to try? I'll search. A

The easiest method is just to wait a few days for the Fx36.0.1 update. If you use Firefox Menu Button -> Help -> AboutFirefox each day that will check to see if the upgrade is available.

The bug fix is I think merely changing prefs and so you could do that yourself. It may be safer to use a spare additional profile, or backup the file prefs.js when trying that initially, because making mistakes in about:config may break Firefox.

Just toggling the pref network.dns.get-ttl to false should fix the issue, that basically is what is done in

Bug 1093983 - DNS resolver should not use 'ANY' to get cached records for TTL 

One of the bug fixes about to be applied in the imminent Fx36.0.1 point Release