n30w1n Posted August 18, 2005 Share Posted August 18, 2005 I've been having an annoying problem with Firefox 1.06.. One in about 20 (ballpark) links I click or URLs I type in returns a "could not be found" alert. When I click it again everything is fine... There's obviously no problem with the pages, it's happening on pretty much any website I visit :ermm: Any suggestions? Anyone else having the same problem? Link to comment Share on other sites More sharing options...
H3lix Posted August 18, 2005 Share Posted August 18, 2005 I've been having an annoying problem with Firefox 1.06.. One in about 20 (ballpark) links I click or URLs I type in returns a "could not be found" alert. When I click it again everything is fine... There's obviously no problem with the pages, it's happening on pretty much any website I visit :ermm: Any suggestions? Anyone else having the same problem? 586392989[/snapback] I have the same problem. I too would like an answer to this. Link to comment Share on other sites More sharing options...
bangbang023 Veteran Posted August 18, 2005 Veteran Share Posted August 18, 2005 Try creating a new, vanilla profile and see if it happens. Link to comment Share on other sites More sharing options...
Kurt Posted August 18, 2005 Share Posted August 18, 2005 It happened to me millions of time... and I did re-create profile.. It's still same.. :/ Link to comment Share on other sites More sharing options...
mrnxdmx Posted September 1, 2005 Share Posted September 1, 2005 i am having same issue here, i have formatted my pc, so its a new installation of firefox. sometimes when i try open page in ie, it opens with no errors. Link to comment Share on other sites More sharing options...
IceDogg Posted September 2, 2005 Share Posted September 2, 2005 I thought I seen an answer to this a while back. Something to do with setting your timeout errors higher or something, but I be dang if I can find it now. Sorry, but I thought I would post what I could remember and maybe point someone in the right direction. I think it was a setting in the about:config that would up the timeout for a page and it fixed this error (most of the time). Hope this helps somewhat, sorry I couldn't find or remember more. Link to comment Share on other sites More sharing options...
Recommended Posts