Home › Forums › Bugs

all proxies enabled on startup (doesn't remember preference)

Fri, 01/22/2010 - 06:53 — vexingv

Afte upgrading to 2.18, when Firefox starts up, FoxyProxy enables all proxies regardless of the preference assigned in the previous session. This bug is very inconvenient for me as I have my previous tabs restored on each startup. However, my SSH proxy rule, which I do not always need enabled and therefore usually don't have the tunnel connected, prevents the pages from loading and I must manually uncheck "enabled" each time and reload all tabs. I never had this issue prior to the upgrade. FoxyProxy does however remember/respect the setting to completely disable able it between startup sessions. Still, I notice that all individual proxies are reenabled. I'm running FF 3.6 on OS 10.5.8 with the following extensions:

Help? Thanks.

‹ Firefox don't start because of foxyproxy.xml Firefox 3.6 ›
Fri, 01/22/2010 - 16:48 — ericjung

Hi, Do you get this with

Hi,

Do you get this with Firefox 3.5.x and FoxyProxy 2.18?

Fri, 01/22/2010 - 17:27 — vexingv

issue present in FF 3.5.7 w/ FoxyProxy 2.18 as well

I just tried it on FF3.5.7 and the issue is there as well. Right now I've resorted to disabling FoxyProxy entirely...

Fri, 01/22/2010 - 18:46 — ericjung

Can you tell me more about

Can you tell me more about the proxies you have configured? Are you using manual, PAC, or direct (no proxy)?

thanks,
eric

Fri, 01/22/2010 - 19:36 — vexingv

I have configured the

I have configured the proxies manually. One proxy connects through a university network so I can get access to professional journals and tools while offsite. The other proxy I have set up is for an SSH tunnel that connects to my home router so I can browse securely/privately. The university proxy is configured to catch/match various journal websites. The SSH tunnel proxy is set to catch all sites (using the * wildcard) except for those above, which require connections via the university proxy. What I usually do is leave FoxyProxy to use proxies based on matched rules/patterns and at the same time I disable the SSH tunnel proxy rule. When I want to browse securely, I enable the SSH tunnel rule. Thus, for the most part, all the connections are direct connections to the network and the proxies are only triggered by some sites and when I want to browse over the SSH tunnel (and I do this by manually enabling that proxy). The problem now is that the SSH tunnel proxy always starts up enabled and when I restart a browsing session none of the pages load (because I the SSH tunnel is not connected) until I disable that proxy rule and reload the tabs.
I hope this explanation clears up my configuration a bit.

Sat, 01/23/2010 - 09:42 — shadyzay

Same Issue

A friend just called me after having the very same issue. He is using FF 3.5.7 with FP 2.18 on Vista-32b
He has a long list of rules with different patterns out of which just 2 or 3 are enabled ( depending on his location ).  All configured proxies are http proxies except for one socks proxy and three rules for direct connections.
He is describing exactly the same issue: All proxies are enabled by default whenever FF restarts. I can perform some tests on his computer later .. what kind of information would you need for debugging?

Sat, 01/23/2010 - 12:44 — mortimar

same issue - FF 3.5.7, FP standard 2.18, XPPro SP2

I have set up 5 proxies. I use proxies based on pre-defined patterns. After Update to new version all proxies are enabled. Disabling 2 proxies, restart FF but and all proxies enabled again.
In older versions disabling doesn't work for me with right click in the status line. I had have to open the FP options menu to disable a proxy succesfully.

Sat, 01/23/2010 - 14:45 — vexingv

didnt work...

OK, so I'm not alone here (I was worried that I might have some esoteric setup/configuration).
As suggested in the previous post, I tried to disable the proxy via the main options window instead of the status bar context menu---still, the same result: all proxies were reenabled upon a new session.

Sun, 01/24/2010 - 02:14 — jackieku

same situation

I have 3 SOCKS, 2 HTTP, and 1 PAC configured. All of them become enabled when Firefox startup.

Sun, 01/24/2010 - 02:25 — ericjung

Thank you everyone for the

Thank you everyone for the information. I am researching it and expect to have a fix in a day or two as version 2.18.1.

Kind regards,
Eric Jung

Tue, 01/26/2010 - 01:23 — ericjung

Hi, I cannot for the life of

Hi,

I cannot for the life of me reproduce this. Can someone with the problem please send me their foxyproxy.xml file? My email address is eric dot jung at yahoo dot com.

Thank you,
Eric

Tue, 01/26/2010 - 15:24 — mortimar

disabledDueToBadPAC="true" --> must be false 4 all but Default

Hi Eric,

I had set up a new proxy and all was fine.
Comparing of old and new foxyproxy.xml shows a difference in 'disabledDueToBadPAC' of the autoconf section in every proxy.

If you still need my foxyproxy.xml let me know.

Bye morT

Thu, 01/28/2010 - 15:53 — g2flyer

Thanks!

Indeed, I can confirm that switching all disabledDueToBadPAC from true to false solved the issue for me.  Note that i've never even used a PAC-based entry in my configuration in all its lifetime!
-michael-

Tue, 01/26/2010 - 02:14 — Ananasnonym

where to get this?

I have 4 proxies, one for my school, one for Direct access to the internet and one for my default Proxy...
Addons: Adblockplus, CookieCuller, NoScript, RefControl, FlashGot, Ctrl-Tab, Personas, Speed-Dial, Java Console, all on the newest version...
How can I help you? Where can I find the .xml file?

Tue, 01/26/2010 - 11:51 — Snuleyman

same problem with no addons (besides foxyproxy) active

I've disabled (not uninstalled) all addons and the problem persists (FF 3.5 Linux/i386)

Edit: disabling a proxy does work for a firefox session. The foxyproxy.xml is properly being written (enabled="false" after firefox shutdown). The problem arises when firefox starts, the attribute enabled of the element proxy is being ignored at that very time.

Wed, 01/27/2010 - 15:59 — arober11

Same issue

Hi
Hit the same issue, running Firefox 3.6.
On exit the foxyproxy.xml has the correct vales, see below, but on load all all proxies are enabled the the xml is updated with "enabled="true":
<proxy name="test proxt 1" id="4229521963" notes="Proxy1" enabled="false" mode="manual" selectedTabIndex="0"  astresort="false" animatedIcons="false" includeInCycle="true" color="#65BAD7" proxyDNS="true">
<proxy name="test proxy 2" id="4109426172" notes="Proxy2" enabled="false" mode="manual" selectedTabIndex="2"  lastresort="false" animatedIcons="false" includeInCycle="true" color="#65BAD7" proxyDNS="true">
<proxy name="test proxy 3" id="1566412977" notes="Proxy3" enabled="true" mode="manual" selectedTabIndex="1" lastresort="false" animatedIcons="true" includeInCycle="true" color="#65BAD7" proxyDNS="true">
Regards, Andy

Wed, 01/27/2010 - 16:30 — mortimar

Workaround, as I wrote some posts before

you have to look at the complete proxy element!
You stoped before 'matches' and 'autoconf' section of every proxy section.

All my proxies had have the variable 'disabledDueToBadPAC="true"'.
A new test proxy was set up this variable to "false". So I switched all values of 'disabledDueToBadPAC' to false. All but Default.

proxy>
...
autoconf url="" loadNotification="true" errorNotification="true" autoReload="false" reloadFreqMins="60" disabledDueToBadPAC="false"/>
...
/proxy>

Hope that helps

Wed, 01/27/2010 - 17:48 — spartacus90210

Similar problem

Foxy Proxy worked great for me up until the 2.18 update, now it is routing everything to the wrong proxy.  I disabled foxproxy and it didn't route any through the proxy.  I have shut it down for now, and routed everything through a different method instead.
I am sure that there is a resolution coming soon :)

Thu, 01/28/2010 - 04:26 — p14c3vo290gha9q...

Extremely annoying

I have 11 proxies which are used for various sites and testing purposes. At any time I wish to have complete control over what is disabled or not. The latest release has changed the default behaviour, which is a terrible programming practice - re-enabling all the proxies as they 'may have been disabled due to a bad PAC': pardon? Rather let the user decide if it's a bad PAC that's causing the issue than assume this is a problem. ie: keep the functionality but allow the user to select the automatic re-enabling option as an exception rather than a rule.
Is there a GUI option to modify this setting?
 

Thu, 01/28/2010 - 16:43 — ericjung

This bug is fixed in

This bug is fixed in FoxyProxy 2.18.1, just released. Please upgrade.

Sorry for the inconvenience.

Eric