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.

Avatar for Username

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

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

I do not have a proxy server but firefox changes to use one everytime I load firefox

  • 2 biyano
  • 33 eza na bankokoso oyo
  • 41 views
  • Eyano yasuka ya user470992

JWTVI
JWTVI
more options

Everytime I open Firefox I get the following:

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

When I go to options/network/connection settings/ it is set to: manual proxy configurations HTTP Proxy 127.0.0.1 Port 60263 use this proxy server for all protocols

I have tried selecting: no proxy and auto-detect proxy settings for this network but when I load Firefox the next time it is back to manual proxy.

Everytime I open Firefox I get the following: The proxy server is refusing connections. Firefox is configured to use a proxy server that is refusing connections. When I go to options/network/connection settings/ it is set to: manual proxy configurations HTTP Proxy 127.0.0.1 Port 60263 use this proxy server for all protocols I have tried selecting: no proxy and auto-detect proxy settings for this network but when I load Firefox the next time it is back to manual proxy.

All Replies (2)

JWTVI
JWTVI Nkolo motuna
more options

I found an add-on called Foxy Proxy that you can use to replace the standard proxy settings. This solved my problem, although one should not have to use an add on to fix a bug in Firefox.

user470992
user470992
more options

Having the same problem and I found out, by deactiviating add-ons one-by-one that the problem comes (at least in my case) through the Xmarks-Plugin.

However, have not found a solution yet.