Useless error message: Hmm. We’re having trouble finding that site.
Categories
(Core :: Networking, defect, P3)
Tracking
()
People
(Reporter: minfrin, Unassigned, NeedInfo)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.6 Safari/605.1.15
Steps to reproduce:
Made an attempt to access an IPv6 only DNS address.
Actual results:
Error appeared saying:
"Hmm. We’re having trouble finding that site.
We can’t connect to the server at dns.name.
If you entered the right address, you can:
Try again later
Check your network connection
Check that Firefox has permission to access the web (you might be connected but behind a firewall)"
Expected results:
The real error message needs to appear somewhere on this page, so when the end user who hasn't a clue asks someone who does have a clue, the problem can be identified.
Was the problem a DNS error? If so, what was the error? Was it connection refused? Connection timed out? Permission denied? What IP address were you trying to get to?
In the absence of a specific, concrete error message, people helping the end user don't have a hope.
|
||
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•1 year ago
•
|
||
Thanks for raising this.
We are tracking network error logging issue through Bug 1872711.
We will add this bug to the list.
|
|
||
Updated•1 year ago
|
|
||
Comment 3•5 months ago
|
||
Given no developer seems to know this is a problem, I’m suggesting this might be an issue that primarily affects slow connections. I have a slow connection myself and Firefox often have trouble with sites that should be perfectly resolvable and reachable (such as my city’s public library, or pages that belong to a local TV station). A second try always resolves the problem.
This happens even with my other instance of Firefox which has been configured to use a local proxy. Given that the proxy will show its own timeout error message if there’s a true timeout, this means Firefox is actually bypassing the configured proxy. By observation, it looks like Firefox always tries to DNS resolve the site’s domain on its own (even if a proxy is used) and time out after a hard-coded timeout that only makes sense for fast connections.
|
||
Comment 4•5 months ago
|
||
(In reply to Ambrose Li from comment #3)
Given no developer seems to know this is a problem, I’m suggesting this might be an issue that primarily affects slow connections. I have a slow connection myself and Firefox often have trouble with sites that should be perfectly resolvable and reachable (such as my city’s public library, or pages that belong to a local TV station). A second try always resolves the problem.
This happens even with my other instance of Firefox which has been configured to use a local proxy. Given that the proxy will show its own timeout error message if there’s a true timeout, this means Firefox is actually bypassing the configured proxy. By observation, it looks like Firefox always tries to DNS resolve the site’s domain on its own (even if a proxy is used) and time out after a hard-coded timeout that only makes sense for fast connections.
Hi,
Could you capture an HTTP log for the issue you saw? Please open a new bug and attach the log there.
Thanks.
Description
•