搜尋 Mozilla 技術支援網站

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

Learn More

The proxy server is refusing connections

  • 14 回覆
  • 166 有這個問題
  • 9496 次檢視
  • 最近回覆由 bigdavemojo

more options

I am using FF 4.0.1 and have been a FF user since the earliest version released - never really had any issues UNTIL FF 4.0.1.

Every time I start up FF now, I get the error message: "The proxy server is refusing connections". I am not using a proxy server.

I have to go to Tools>Options>Connection Settings to select the "No Proxy" option EVERY TIME I start up FF. It does not remember this setting and keep resetting itself to think I'm using a proxy server. This must a be bug and I've seen many others post about this issue but haven't really found a workable solution as yet.

I have tested with Chrome and Explorer and don't have this problem with those browsers.

If there is a fix for this incredibly annoying, time-wasting problem, please share it.

Thanks

被選擇的解決方法

Create a new profile as a test to check if your current profile is causing the problems.

See:

There may be extensions and plugins installed by default in a new profile, so check that in "Tools > Add-ons > Extensions & Plugins" in case there are still problems.

If that new profile works then you can transfer some files from the old profile to that new profile (be careful not to copy corrupted files)

See:

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

所有回覆 (14)

more options

Thanks for the link.

My prefs.js file properties show it is not a read-only file, so that's not the issue; and the file is not corrupted since I can make and save other settings changes in FF that are 'remembered' when I next start up a new FF session. Its only the 'no proxy' setting that is not being saved.

But I went ahead and did the recommended procedure in the article anyways to test; that was to rename prefs.js to prefs.jsOLD and close/restart FF, but same problem. However I had about 8 tabs open and when FF restarted, I noticed that only my home page tab was displaying the "The proxy server is refusing connections" error message. That home page is my iGoogle page. The other tabs all loaded fine as they should have. This makes the problem even more strange.

Ultimately I still had to manually open Tools>Options>Connection Settings to select the "No Proxy" option to get my iGoogle home page to load properly.

由 bigdavemojo 於 修改

more options

Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).

more options

I tried starting FF in Safe Mode as suggested, and the proxy issue/error message did not show up. iGoogle page (and other tabs) opened normally as they are supposed to.

When I restart FF normally without safe mode, the proxy warning message reappears.

I use the default theme by default, and I'm not sure which other add on I'm using would be causing this recurring proxy error problem.

more options

If it does work in Safe-mode then disable all extensions and then try to find which is causing it by enabling one at a time until the problem reappears.

more options

I have tried safe-mode again, disabling all extensions several times, but the problem is reoccurring. I'm getting "The proxy server is refusing connections" error message on my iGoogle home page and sometimes other tabs that are open, such as Yahoo. I am not using a proxy server and have fixed my settings in FF accordingly, but FF resets the settings every time I start a new FF session causing the error to occur again and again. I still have no idea why FF keep resetting the settings to 'with a proxy server'.

more options

選擇的解決方法

Create a new profile as a test to check if your current profile is causing the problems.

See:

There may be extensions and plugins installed by default in a new profile, so check that in "Tools > Add-ons > Extensions & Plugins" in case there are still problems.

If that new profile works then you can transfer some files from the old profile to that new profile (be careful not to copy corrupted files)

See:

more options

Well that did it! I created a new profile, copied over my settings from my old profile, and FF starts with no more proxy error messages.

Problem solved completely.

Thanks so much....greatly appreciate your assistance with solving this issue.

more options

You're welcome

more options

Just a PS:

The problem has now re-occurred, 2 days after the profile change seemed to fix the problem.

Any further suggestions on fixes appreciated.

Thanks.

more options

Did you try to delete the file prefs.js in the Firefox Profile Folder another time?

If you see other pref-##.js files then delete those as well

Do you have security or cleanup software that might corrupt that prefs.js file?

more options

I have deleted prefs.js file again; on restarting FF, this actually magnified the problem, since before, only my iGoogle home page tab would display the proxy error message; now all open tabs display this message.

The only security software running on this Win & PC is Microsoft Security Essentials.

I have tried disabling all add ins and still the problem occurs on FF start up every time. I have the same FF add ins and setup on my Thinkpad and it runs just fine - no incorrect proxy warning messages.

more options

Did you try to change the connection setting to No proxy?

You can find the connection settings in Tools > Options > Advanced : Network : Connection


Did you try Save mode?

Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).

more options

I have to change the connection setting to No proxy EVERY TIME I start a new FF session - that's the problem here. FF is not saving those settings. I have no proxy, but it thinks I do every time I have to start a new FF session. The only way to connect is manually go in and change the setting to No Proxy.

And yes I already did the safe mode start on default theme just as you described more than once - no solution there for me either.

Thanks for your suggestions.

I think I see Chrome in my future.