Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Using system wide proxy setting in Linux

  • 3 回覆
  • 0 有這個問題
  • 595 次檢視
  • 最近回覆由 hinko.kocevar
  • 已解決

I have the HTTP_PROXY, HTTPS_PROXY and FTP_PROXY (and their lowercase counterparts) exported and then the firefox binary is started from the shell script. The settings in firefox say it will 'Use system proxy settings'. Nevertheless I do not see the proxy being used as I can not access the web pages that need the proxy. The 'about:config' also does not show that firefox picked up any proxy related information from the shell environment.

I know the proxy address is correct because if I use brave browser instead of firefox (same shell script that launches brave) I can reach the web pages behind the proxy as expected.

I have the HTTP_PROXY, HTTPS_PROXY and FTP_PROXY (and their lowercase counterparts) exported and then the firefox binary is started from the shell script. The settings in firefox say it will 'Use system proxy settings'. Nevertheless I do not see the proxy being used as I can not access the web pages that need the proxy. The 'about:config' also does not show that firefox picked up any proxy related information from the shell environment. I know the proxy address is correct because if I use brave browser instead of firefox (same shell script that launches brave) I can reach the web pages behind the proxy as expected.

被選擇的解決方法

If your proxy is set up in the following format: "<proxy_user>:<proxy_password>@<proxy_host>", you have to add a scheme (http://).

從原來的回覆中察看解決方案 👍 1

所有回覆 (3)

If the 'Manual proxy configuration' is used instead I can access the web pages behind the proxy. But this is not what I want to do; I would like firefox to pick up the system wide proxy settings.

選擇的解決方法

If your proxy is set up in the following format: "<proxy_user>:<proxy_password>@<proxy_host>", you have to add a scheme (http://).

I only have "<proxy_host>:<proxy_port>". Nevertheless adding "http://" in front of it solved the issue for me.

Would be really nice if this was documented somewhere (apologizes if it is , but I couldn't spot it)..