Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

Avatar for Username

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Esta discussão foi arquivada. Se precisar de ajuda, por favor, coloque uma nova questão.

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

  • 2 respostas
  • 33 têm este problema
  • 41 visualizações
  • Última resposta por 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.

Todas as respostas (2)

JWTVI
JWTVI Proprietário da pergunta
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.