Spletno mesto bo delovalo z omejenimi zmožnostmi, medtem ko na njem izvajamo vzdrževalna dela za vas. Če članki ne rešijo vaše težave in želite zastaviti vprašanje, naša skupnost za podporo čaka na vas na @FirefoxSupport na Twitterju in na /r/firefox na Redditu.

Avatar for Username

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

Ta tema je arhivirana. Postavite prosim novo vprašanje, če potrebujete pomoč.

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

  • 2 odgovora
  • 33 ima to težavo
  • 41 ogledov
  • Zadnji odgovor od 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.

Vsi odgovori (2)

JWTVI
JWTVI Lastnik vprašanja
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.