Firefox do not found the server at the address...




10 years ago
10 years ago


(Reporter: Yvan Boisclair, Unassigned)


Firefox Tracking Flags

(Not tracked)




10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv: Gecko/2008070208 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv: Gecko/2008070208 Firefox/3.0.1

Since I install Firefox 3 I get the error screen '' Firefox do not found the server at the address...'' when I click on a link . I have to click on the RETRY button almost every time to finely have access to the new link. 
I think that the situation occur when the link his outside the actual server ??

Reproducible: Sometimes

Steps to Reproduce:
1.Click on a link that his outside the server
2.The error screen appear 
3.Click on the retry button 

Actual Results:  
I have to click once or twice on the RETRY button to have access at the new link.

Expected Results:  
When I click on a link, Firefox should find the new link address  immediately like with Firefox 2.

Comment 1

10 years ago
What links are you clicking? And what website is this at. If you need support, please visit This is not a support forum, but a technical bug tracking database. 

Comment 2

10 years ago
(In reply to comment #1)
> What links are you clicking? And what website is this at. 

It's no link in particular. 3 times out of 5 when I click on a link the error screen pop up and I have to click the retry button. For an example just before writing this note   I click in my bookmark on  Geckozone '''' and got the error screen that Firefox didn't fine the server. I click on the retry button and It work I was at the Geckozone web site.I also click in my startup page website Branchez-vous (
on the link '''' I got the same error message . I click on the retry button on I was at the Yearbook site. This append almost every time.

Comment 3

10 years ago
I experienced this problem with the last version 2 rev as well as with 3. 

The problem appears to be that Firefox is wrongly interpreting failure to respond(due to the fact that response times are increasing as Internet slowly dies under the load of rubbish being transmitted; much of it by system admins too stupid to trash spam, and bouncing it to the inevitably false from address instead) as a bad address.

The solution is to increase the time that Firefox waits for a response, and automatically try again on a time-out.

Comment 4

10 years ago
This is a MAJOR problem. I'm so sick and tired of false "Address not Found" errors that I've installed Chrome! I suggest that, in addition to identifying the error, i.e., no response, correctly, two buttons ("Keep trying" and "Open another page and keep trying" be added to the "no response" error message

Comment 5

10 years ago
Andrew, please keep this on topic to the bug. Adding buttons should be filed under a new bug as an enhancement. And do not use weak threats like "I've installed Chrome" to try to move this bug where you want it. Without enough information to diagnose or reproduce this bug, I can not confirm it. Have you checked your internet connection, the server, and tried the start Firefox in Safe Mode

Comment 6

10 years ago
I found this response offensive. 
The topic of the bug is "Address not found" and there are several otherbug reports , e.g., 441175 which relate to the generic problem, namely that Firefox is mis-handling no response errors. 
My "weak threat" was not a threat at all, but a statement of fact, namely that my frustration with this problem had led me to install a competing browser. IMO, the statement should have been viewed as a wake-up call to collate the numerous reports of problems associated with lack of response, and elevate the importance of fixing them. 
The condescending "Have you tried . . " simply adds insult to injury: Three users have confirmed this bug, one 441175, and I'm sure that a cursory search of page not found and related bug reports would reveal many, many more.
FWIT, fails pretty consistently; never.

Comment 7

10 years ago
Andrew, please read If this issue is the same as another bug, it should be marked as a duplicate of that bug. Please perform the steps in Comment #5.

Comment 8

10 years ago
Let's see now, did you mean:

1. Commenting
   1. No pointless comments? 
2. Changing Fields
   1. No messing with other people's bugs. Unless you are the bug assignee, or have some say over the use of their time, never change the Priority or Target Milestone fields. If in doubt, do NOT change the fields of bugs you do not own? 


If you see someone not following these rules, the first step is, as an exception to guideline 1.4, to make them aware of this document by PRIVATE mail. Flaming people publically in bugs violates guidelines 1.1 and 1.3?

Here are a few addresses for which Firefox fails to handle slow response properly (usually gets there after one or two retriess):

Hint: it's usually a false "Address not found," but the page is sometimes loaded as text and then loaded correctly on page reload. This suggests to me, although I've only been working with computers for 50 years, that the problem may have something to do with image loading.

Comment 9

10 years ago
Duplicate bug list: 441175, 435323,437426, 441764, 454342, 455602, 456012
(result of a cursory search).
Bug 441175 seems to be the closest to this issue.
Last Resolved: 10 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 441175
You need to log in before you can comment on or make changes to this bug.