Manual proxy and Proxy settings

[Rigido71]

Hi, I had to search and read a lot before it was clear that to make Proxy Switcher work FF internal settings for proxy must be set to "Use System Proxy", I think you should make it more clear to users. Now, I use NetSetMan Pro to switch between customer profiles and change (with others settings) System/IE Internet settings, but it looks like something doesn't work on FF. It looks like FF doesn't read/apply ALL of the settings. I could use NSM Pro to set FF settings too, but I'm tryng to understand what's wrong and I will skip this for now.. The problem is with SOCKS HOST setting, some sites (i.e. web.whatsapp) do not work until I set the option in FF itself (looks like a Fixed bug: https://bugzilla.mozilla.org/show_bug.cgi?id=624837), no matter if I used NSM Pro to set systemwide Internet Settings or I used Proxy Switcher manual setting.

[jianhuiz]

I don't have the problem you described, for me the "Manual Proxy" always work as expected.

However I found that "Direct" and "System Proxy" behaves the same as Proxy Switcher was off.

1. In my Firefox proxy setting, I configured a PAC file, and I use 'System Proxy" in Proxy Switcher.
2. Sometimes I want to always use a proxy and "Manual Proxy" works well
3. other times I want to not use proxy at all, but switching to "Direct" in Proxy Switcher doesn't prevent Firefox from using the PAC file I set, I had to change it into "No Proxy" in Firefox to have a direct connection.

[Rigido71]

Hi, I wrote on Bugzilla as it seems that FF had the "SOCKS bug" and I hope they will dig it to see if it is really solved on Nightly too. BTW I think there is something "strange" with Proxy-Switcher as sometimes it looks like it doesn't change settings at all and you have to change it manually on FF settings (as jianhuiz wrote)

[rNeomy]

However I found that "Direct" and "System Proxy" behaves the same as Proxy Switcher was off.

"System Proxy" unregisters the custom PAC script and hence it is like browser does not have any proxy extension. "Direct" means the PAC script returns "DIRECT" to all network requests.

These will work as expected soon when the actual "Direct" proxy is implemented in the API. There are two open bugs in Bugzilla I am waiting for them to be resolved!

BTW I think there is something "strange" with Proxy-Switcher as sometimes it looks like it doesn't change settings at all and you have to change it manually on FF settings (as jianhuiz wrote)

Use the IP tool in the popup to confirm this. Also I need to somehow be able to reproduce this in order to fix the bug!

[Rigido71]

Hi, I'm sorry I was not clear...but the problem was not clear for me too!

First, let me say that I still think that bug 624837 is not solved. After web.whatsapp.com I found that even Keepa plugin doesn't work until I put the right values for the SOCKS server/port of the FF PROXY section, no matter what I set on Windowss "Internet Settings".

Said that, I could live with just "Direct" and "Manual" settings, but sometimes I have to set values for all of the protocols (HTTP, SSL, FTP and SOCKS) but I didn't understand where I should put settings for SOCKS protocol on "Manual Proxy" tab. Is it "Fallback server" section?

Thanks.

[rNeomy]

I didn't understand where I should put settings for SOCKS protocol

There is no SOCKS protocol for web requests. You can only have http://.., https://... and ftp://.. right? That SOCKS setting in the Firefox preferences page is just confusing. For each of above schemes, you can either have HTTP, HTTPS, or SOCKS server type.

So in your case since the server is SOCKS, for all http and https and ftp requests write IP and PORT of your SOCKS server and make sure to change the server type to SOCKS.

[rNeomy]

no matter what I set on Windowss "Internet Settings".

For Firefox to detect IE's settings, you need to select the "System Proxy" which is not currently supported in FF! The above image is for the Chrome version of the extension.

After web.whatsapp.com I found that even Keepa plugin doesn't work until I put the right values for the SOCKS server/port of the FF PROXY section,

If you set the extension in the manual mode with the right values for the SOCKS server (make sure the "Use remote DNS" is checked). This should work as expected.

[Rigido71]

Ok, I will try to explain all of my isseus.

Windows setup:

Firefox setup::

Everything works but I found two sites (keepa.com and web.whatsapp.com) don't, no matter the browser I use, But if I add proxy settings in Windows settings:

Internet Explorer/Edge start to work but FF still doesn't (and it looks like this is the bug I wrote before, FF doesn't read SOCKS configuration from systems settings). So I have to change FF settings to manual:

Now everything works on FF too. I don't know the proxy software and I can't use it just as a SOCKS. Can you help me to understand IF and HOW can I use your extension to switch from SYSTEM to MANUAL?

Thanks for your time.

[rNeomy]

So if you change the FF setting to "Use system proxy" and turn windows proxy off while having these value set in the manual tab of the extension, still you cannot access those sites?