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

Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více
Vyřešeno Archivováno

Removing firefox proxy settings does not work until a restart?

Dimpl

When I transfer from my work network (with a proxy server) to my home network (no server), I have to restart the browser before it realizes that there is no proxy server that it has to authenticate with. Until I do this, (re)loading pages gives me an error.

However, when going the other way, it smoothly recognises that there is a server, and no restart is required to continue browsing

I have automatic proxy settings enabled. I have tried selecting 'no proxy server', but I still need to restart firefox for this to work.

When I transfer from my work network (with a proxy server) to my home network (no server), I have to restart the browser before it realizes that there is no proxy server that it has to authenticate with. Until I do this, (re)loading pages gives me an error. However, when going the other way, it smoothly recognises that there is a server, and no restart is required to continue browsing I have automatic proxy settings enabled. I have tried selecting 'no proxy server', but I still need to restart firefox for this to work.

Všechny odpovědi (3)

hello, is this only affecting secure pages (starting with https://) and does it work when you press ctrl-shift-r after the change in order to reload the page?

Zvolené řešení

Please update to the current Firefox 22.0 release.

  • Help > About Firefox

The Firefox 21 version that you currently run is no longer supported with security updates.

  • It is important to update Firefox and add-ons to the latest version to get all security fixes.

Thanks cor-el,

I believe my firefox autoupdated this morning, and the bug is gone :)