User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/20061204 Firefox/126.96.36.199 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/20061204 Firefox/184.108.40.206 Every single site or search, including a Google search for Mozilla, comes up with Server not found. Upon a second try, it will work. Also, was working in my online billpay and went from the first secure and locked page, to the next page within the site to go to the billpay section, and it came up server not found, and suddenly, while still in the site, it was no longer secure and no longer locked. This is happening on both mine and my husbands' computers. I have checked Zone Alarm and put the green check as instructed, but for 220.127.116.11 it is listed as Firefox Installer in the list by the check, and as Firefox at the bottom. Don't know if this helps. Very concerning that Firefox can unlock a secure bank site with an error. Reproducible: Always Steps to Reproduce: 1. Try to go to any website, or perform any search. 2. Server not found error will appear 3. Try again, you will connect (on a locked site, you will now be unlocked and no longer secure) Actual Results: See above. Expected Results: See above. Firefox should take you to the requested site or search on the first try. This problem has only been encountered since downloading the new version 18.104.22.168
Firefox should NEVER unlock a secure site with an error.
11 years ago
Duplicate of this bug: 370088
"server not found" means we couldn't connect for some reason. Could be the a temporary server glitch, a local firewall issue, or the number of connections allowed to Firefox was saturated with other requests. Pressing the "try again" button often works when the problem was temporary (as opposed to a mis-typed URL) and is not itself an issue. If you're getting it all the time that sounds like something's wrong, but would not be a security problem. For that I'll direct you to our community support forums to get help figuring out, see http://www.mozilla.org/support/#community The other aspect, the locked site showing unlocked, has me more concerned. Does that happen on a lot of secure sites, or one in particular? When it's "unlocked" does the lock go away entirely, or does it become a lock with a red slash through it? That would indicate "mixed" mode which means the site in question directed Firefox to load insecure content as part of the page (sometimes an ad?).
The server not found issue happens every time. No matter where you go or what you are doing, or if you have nothing else working at the same time, it happens every time. Yes, the try again key does work. But this problem, with having to hit try again every single time that you use the internet, has only occurred since loading the new Firefox 22.214.171.124 and is happening on both my computer, and my husbands' computer, which has a completely different set of programs on it. The problem is with the new Firefox program. This issue never occurred until downloading the new version. Please tell me that you are working on this. Regarding the unlock, it was on my banking site. This is first I have experienced it. It was a lock with a red slash through it, so is this an issue that I should bring up with my bank? No, it was not an ad, it was simply a glitch again with Firefox saying it couldn't load, try again, and then it went unsecure.
Component: Error Console → General
OK Y'ALL - HERE IT IS! I installed FF2.0 to a new dir. opened in SAFE MODE and had DISABLED extensions and reset to defaults. NO PROBLEM! My suspicion is... it's an errant extension. I will do upgrades later & try when i have more time. But that should put you all on the right road.
Most likely an bugged extension. We're glad you were able to get it to work. If you wish, try uninstalling extensions one by one until you identify which one causes the problem and bring it up with the extension author. Thanks!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.