Open Bug 490483 Opened 15 years ago Updated 1 month ago

Configusing wording of error message when Socks5 proxy is not accessible

Categories

(Core :: Networking: Proxy, defect, P3)

defect

Tracking

()

People

(Reporter: mcepl, Unassigned)

Details

(Keywords: ux-error-recovery, Whiteboard: [necko-backlog])

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3) Gecko/20090327 Fedora/3.1-0.11.beta3.fc11 Firefox/3.1b3
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3) Gecko/20090327 Fedora/3.1-0.11.beta3.fc11 Firefox/3.1b3

(originally filed as https://bugzilla.redhat.com/show_bug.cgi?id=498039)

When I have 

user_pref("network.proxy.socks", "localhost");
user_pref("network.proxy.socks_port", 9999);
user_pref("network.proxy.type", 1);

in prefs.js (by mistake, sloppy work with mouse) and forget about it, the error message I get is:

<blockquote>
The connection was reset

The connection to the server was reset while the page was loading.

    *   The site could be temporarily unavailable or too busy. Try again in a
        few moments.

    *   If you are unable to load any pages, check your computer's network
        connection.

    *   If your computer or network is protected by a firewall or proxy, make
        sure that Firefox is permitted to access the Web.
</blockquote>

How in the world I should understand from that that firefox cannot get connection to Socks5 proxy?


Reproducible: Always

Steps to Reproduce:
1.misconfigure firefox
2.six months later ...
3.start up firefox and go to any website
Actual Results:  
non-sensical boiler-plate error message

Expected Results:  
error message saying something in the sense "I cannot get connection to Socks5 proxy you have configured"
Actually, I wasn't sloppy with the mouse, I don't use Firefox as my main web browser (I use Epiphany), and it was setup with a Socks proxy during the holidays to listen to radio from home.

I thought the errors, when I needed to use Firefox, were due to recent nspr/gcc 4.4.0 bugs.

The error message should definitely have a better error message when the proxies aren't available, rather than blame the firewall or website.
This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
I am sorry for missing this needinfo. Yes, I can reproduce this very well with firefox-3.6.12-1.fc14.x86_64, the error message hasn't changed at all.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: INCOMPLETE → ---
Confirmed with Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b9pre) Gecko/20110101 Firefox/4.0b9pre ID:20110101030401

The error message has improved slightly:
"The connection has timed out
 The server at website.com is taking too long to respond.
 *  The site could be temporarily unavailable or too busy. Try again in a few
    moments.
 *  If you are unable to load any pages, check your computer's network
    connection.
 *  If your computer or network is protected by a firewall or proxy, make sure
    that Minefield is permitted to access the Web."

However there is still no mention that it's the proxy that cant be connected to.

It looks like this was fixed once already in bug 56629.
	
However perhaps bug 226943 regressed it? (Guess only from summary, haven't checked regression range).
Component: General → Networking
OS: Linux → All
Product: Firefox → Core
QA Contact: general → networking
Hardware: x86 → All
Whiteboard: [CLOSEME 2010-11-01]
Version: unspecified → Trunk
FWIW, while checking I never got the "Reset" Message from Comment 0 nor the "Timed out" Message from Comment 5.

Anyways here's what i figured out:

with a fake/invalid SOCKS v5 Server there once was


Proxy Server Refused Connection

Firefox is configured to use a proxy server that is refusing connections.

The browser is configured to use a proxy server, but the proxy refused a connection.

    * Is the browser's proxy configuration correct? Check the settings and try again.
    * Does the proxy service allow connections from this network?
    * Still having trouble? Consult your network administrator or Internet provider for assistance.


this changed to

The proxy server is refusing connections
              
Firefox is configured to use a proxy server that is refusing connections.
        
  Check the proxy settings to make sure that they are correct.
  Contact your network administrator to make sure the proxy server is
  working.


Last good nightly: 2005-08-29
First bad nightly: 2005-08-30

Bonsai Range:
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=PhoenixTinderbox&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2005-08-29+03%3A00&maxdate=2005-08-30+03%3A00&cvsroot=%2Fcvsroot
=> likely by Bug 305998


then it changed to current Message

Unable to connect
        
Firefox can't establish a connection to the server at www.google.com.
        
  The site could be temporarily unavailable or too busy. Try again in a few
    moments.
  If you are unable to load any pages, check your computer's network
    connection.
  If your computer or network is protected by a firewall or proxy, make sure
    that Nightly is permitted to access the Web.

Last good nightly: 2011-03-31
First bad nightly: 2011-04-01

Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=422bbd8245a7&tochange=1a89509e25e4
=> likely by Bug 280661
Status: REOPENED → NEW
Whiteboard: [necko-backlog]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Priority: P1 → P3
Severity: normal → S3

Moving bug to Core/Networking: Proxy.

Component: Networking → Networking: Proxy
You need to log in before you can comment on or make changes to this bug.