This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

How to disable user prompt dialog: The proxy moz-proxy://xxxxxxx:8080 is requesting a username and password

  • 2 antwoorde
  • 1 het hierdie probleem
  • 37 views
  • Laaste antwoord deur thunderzhulei

more options

I'm using firefox in linux for selenium test automation. Some of my automation tests need a sysproxy (provided by my company) to access internet. These prefs are set in my test

"network.proxy.type": 1, "network.proxy.http": "company.proxy.com", "network.proxy.http_port": 8080

When firefox launches up, a prompt dialog is always shown asking for credentials for the proxy. I've added company .pem in path ~/.mozilla/certificates and these .pem are loaded correctly in firefox.

Is there a way to disable the user prompt dialog?

I'm using firefox in linux for selenium test automation. Some of my automation tests need a sysproxy (provided by my company) to access internet. These prefs are set in my test "network.proxy.type": 1, "network.proxy.http": "company.proxy.com", "network.proxy.http_port": 8080 When firefox launches up, a prompt dialog is always shown asking for credentials for the proxy. I've added company .pem in path ~/.mozilla/certificates and these .pem are loaded correctly in firefox. Is there a way to disable the user prompt dialog?

All Replies (2)

more options

Does setting signon.autologin.proxy = true work ?

See also Proxy:

more options

No, signon.autologin.proxy = true doesn't work. All .pems that our company proxy requires are installed via policies.json. I can see them in certificate manager.