Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Server Not Found error only affects Firefox

  • 10 个回答
  • 1 人有此问题
  • 8 次查看
  • 最后回复者为 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.

所有回复 (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