The Proxy Moz Proxy Is Requesting A Username And Password

The Proxy Moz Proxy Is Requesting A Username And Password

helmutziegler – Mozilla Support

HTTP & SOCKS Rotating Residential

  • 32 million IPs for all purposes
  • Worldwide locations
  • 3 day moneyback guarantee


Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.
Learn More
The message comes often some seconds after a new site or adress was opened but not everytime. In earlier versions it was quite rare but now it comes almost with every change. The solution I have found in the web
1- In the Firefox Address Bar, type in “About:config”
2 – Click on button to continue
3 – In search bar, type in “Websocket”
4 – Set network. websocket. enabled to false
worked just for the first day. The parameter is still set to false, but it does not help any more.
I have the german message but the problem seems to be general and was not solved up to now.
Chosen solution
The Reset Firefox feature can fix many issues by restoring Firefox to its factory default state while saving your essential information.
Note: This will cause you to lose any Extensions and some Preferences.
Open websites will not be saved in Firefox versions lower than 25.
To Reset Firefox do the following:
Go to Firefox > Help > Troubleshooting Information.
Click the “Reset Firefox” button.
Firefox will close and reset. After Firefox is done, it will show a window with the information that is imported. Click Finish.
Firefox will open with all factory defaults applied.
Further information can be found in the Refresh Firefox – reset add-ons and settings article.
Did this fix your problems? Please report back to us!
Hope this helps!
Read this answer in context
All Replies (3)
Chosen Solution
Hello Curtis
Thank you, the problem seems to be fixed.
Open - GitHub

HTTP & SOCKS Rotating & Static Proxies

  • 72 million IPs for all purposes
  • Worldwide locations
  • 3 day moneyback guarantee


Open – GitHub

I think this issue needs to be considered as two independent enhancements but I won’t split them to different issues until some further progress has been made.
There are many technical challenges with this issue but possibly the biggest is not really technical:
How long does the user want to wait at startup for credentials to be made available from the password manager?
The best I can come up with is: until the user clicks a button to say “Stop waiting”.
We could show a window with messaging and a button a bit like this:
Kee is waiting for you to open your password database.
Your browser will not work correctly until you do this or click the button below.
[Stop Waiting] Assuming we go for that answer or find a better one some day, the technical challenges can then begin.
There is no documentation about how to actually implement this technically but after a few hours searching I’ve dug out one clue from last year:. I have no idea if that will work the same in other browsers.
Rough notes on what would be required to implement this follow:
A new onAuthRequired listener at top level in, added before the current first-step for loading the extension (async load of our config)
Create a promise that gets resolved when artListening() has been run.
Resolve the promise with the function that currently gets invoked by existing event handlers (possibly need 2 different versions of all this code to handle Chrome and Firefox differences)
Assign the resolved function to a local var so that all pending network auth requests can be handled and all future auth requests can flow straight through to execute that function without the need for the promise
Create a separate promise that gets resolved by the user action of clicking on the “stop waiting” button
Create a new dialog window (store some sort of global reference so we only create one even if there are multiple auth requests at startup)
Launch that dialog window the first time the onAuthRequired listener is invoked (unless artListening() has already run – need to be able to track that somehow)
All above must be implemented in a way that easily allows a config setting to influence the waiting period – either by disabling the feature (no waiting), waiting indefinitely (per the plan above) or waiting for up to a certain number of seconds. It’s not necessary to actually implement those config options though – it can be slotted in retrospectively if we find a real-world benefit from them.
Regrettably I’m leaning towards saying that this enhancement is too high cost and risk for me to attempt in the foreseeable future but if someone manages to find the considerable amount time required to implement and test all of the above on multiple browsers I’m happy to accept a pull request.
I’ve updated the old pull request so if you download and build that version of Kee I think this might work.
I still can’t find any practical way to test this myself so as before, I need people who are actually using a proxy to build and test this custom version of Kee before I can take this issue any further.
Please let me know how you get on with this test version.
Firefox asks for proxy details, but only when accessing facebook

Firefox asks for proxy details, but only when accessing facebook

At work, all requests are forwarded to a central load-balancing, caching Squid proxy server. If I try to access Facebook from within Firefox, I get the standard proxy authentication dialog:
The proxy moz-proxy is requesting a username and password.
The site says: “moz-proxy
However, this dialog comes only for facebook & only when accessed from Firefox – any clues as to why this happens? Accessing from Internet Explorer or Chrome works fine, and yes Facebook is not blocked.
Just Firefox gives this problem. I have installed NTLM Auth for Firefox addon, but it hasn’t helped.
The proxy settings are set to auto detect, same as in Internet Explorer & Chrome.
I’m using the current stable version of Firefox, 10. 0. 2 on Windows XP SP3
asked Mar 9 ’12 at 6:02
Sathyajith Bhat♦Sathyajith Bhat60. 4k36 gold badges176 silver badges263 bronze badges
Most probably, your proxy is blocking the WebSocket protocol. Chrome before version 14 and IE don’t support it, so they are not affected.
Go to the URL about:config, search for the key network. websocket. enabled and switch it to false.
HackToHell6, 2723 gold badges36 silver badges62 bronze badges
answered Jun 12 ’12 at 17:04
mcortesemcortese1661 silver badge2 bronze badges
I Just tried the suggestion in the accepted answer and I’m afraid it didn’t fix my problem, as well as these other suggestion which also didn’t work: (These solutions may be currently outdated)
However, while browsing the aboug:config page I found this entry:
If this is set to TRUE the prompt does not appear anymore.
BTW: It does only work if you log in at least once. If you cancel it, it keeps appearing.
And, as a consequence, if you use the private browsing feature (I use it at work, for personal stuff: e-mail, etc. ), every time you start a new private session you have to accept the login prompt. Not a big problem though…
answered Jul 30 ’13 at 11:27
I’ve been having the same issue for a while now. It’s a bug specific to Firefox, and only when accessing Facebook addresses through a proxy. This page itself, for instance, brings up the dialog a total of 10 times, taking 10 clicks before I can dismiss it and go about my business.
I have since downgraded to Firefox 4. 1, which fixed the issue. It’s not a great workaround, but it’s there.
EDIT: It turns out that last bit was premature – I’ve now started experiencing the same problem on 4. 1.
answered Apr 5 ’12 at 6:08
Firefox 8 added Origin tag for images, which has caused some specific proxy issues. If Facebook works for you with Firefox 7, I would say it’s a bug in Firefox.
answered Mar 9 ’12 at 10:04
eiseis1, 9691 gold badge23 silver badges37 bronze badges
Not the answer you’re looking for? Browse other questions tagged windows-xp firefox proxy or ask your own question.

Frequently Asked Questions about the proxy moz proxy is requesting a username and password

Share this post

Leave a Reply

Your email address will not be published.