This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Oops! Firefox could not find xxxxxx Error on recently visited sites

  • 2 replies
  • 29 have this problem
  • 9 views
  • Paskiausią atsakymą parašė thisnotreal

more options

I just got a new laptop, downloaded Firefox and having the Oops! Firefox could not find error. It happens with any site. Hitting refresh loads the page just fine. I've disabled IV6, I've made sure Firefox is on the Windows 7 Firewall exception list (deleted and re-added it), and Ive disabled DNS prefetching. Google Chrome has the same problem on my computer but IE 8 does not.

I just got a new laptop, downloaded Firefox and having the Oops! Firefox could not find error. It happens with any site. Hitting refresh loads the page just fine. I've disabled IV6, I've made sure Firefox is on the Windows 7 Firewall exception list (deleted and re-added it), and Ive disabled DNS prefetching. Google Chrome has the same problem on my computer but IE 8 does not.

All Replies (2)

more options

Do a malware check with a few malware scan programs.
You need to use all programs because each detects different malware.
Make sure that you update each program to get the latest version of the database before doing a scan.

See also "Spyware on Windows": http://kb.mozillazine.org/Popups_not_blocked and What to do when searches take you to the wrong search website


See also http://kb.mozillazine.org/Error_loading_websites - "Error_loading_some_websites"

more options

Thanks for the quick reply, I have done all the scans mentioned and they all found 0 infections besides the standard cookies and what not. The issue still exists though.