I think that this has been answered before, because, on my old computer, I did something to fix this problem, but I can't find it. When using Firefox, I regularly get a "not found" error when attempting to go to a website. When I re-click on the same link or select the same bookmark or re-enter the same url, the site will popup immediately.
Like I said, I used to have the same problem when I installed Firefox on my old PC (which is dead, so I can't check the settings). What causes this and what do I need to do to fix it?
I copied the bookmarks from a backup that I had from the old PC. I don't think that the bookmarks are the problem because the same problem occurs whether I use a bookmark, click on a hypertext link, enter the url manually or even going to my homepage after launching Firefox.
If doesn't happen all of the time (maybe once in every ten or twenty websites).
Yes, I set that based on one of your previous posts (it was set that way on the old PC too). In looking at the other settings, I think that setting "network.dns.disableIPv6" to true is what fixed the problem on my other PC. However, I already have that set to true. So this can't be the solution.
Licker, in you Firefox profile directory there is a subdirectory named 'extensions' where every extension has its own directory and if you look at the dates of those you can see which was changed recently. Go inside that directory and in the 'chrome' directory you can see the name of the extension in question. A lot of extensions have recently been upgraded to be compatible with the upcoming 1.5 release, but onfortunately some of those break 1.0.7 if you upgrade.
C:\Documents and Settings\licker\Application Data\Mozilla\Firefox\Profiles\xxxxx.default\extensions
should be something like that--if you're on 1.5 and had a decent collection of extension, it may be time do to some cleaning after you uninstall the ones not working.
I finally got around to uninstalling the "Flashgot" extension. I never used this anyway, and it was the one most recently upgraded. The "not found" problem has gone away.