FelisCatus / switchy

Automatically exported from code.google.com/p/switchy
9 stars 3 forks source link

Switchy doesn't start using my SOCKS proxy #158

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install Bitvise Tunnelier 
2. Configure it to connect to SSL server, start and establish a connection.
3. Create new entry in Switchy and configure it to connect to 
localhost:1080 (or whatever port Tunnelier listens to) Socks only 
4. Try open any url

What is the expected output?
There must be connection attempt logged in Tunnelier log (to see an example 
configure the same via IE settings)

What do you see instead?
Nothing. Chrome just doesn't use this proxy.

Operating system:
Windows XP

Error Log:
[17:33:18] [info] - Extension Info: v1.6.3
[17:33:18] [info] - Browser Info: 5.0 (Windows; U; Windows NT 5.1; en-US) 
AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.38 Safari/533.4
[17:38:41] [success] - Everything is OK
[17:50:48] [success] - Everything is OK

Original issue reported on code.google.com by igor.rya...@gmail.com on 19 May 2010 at 2:06

Attachments:

GoogleCodeExporter commented 9 years ago
Did you select the proxy profile "Tunnel" from Switchy menu?

Original comment by Mohammadhi on 19 May 2010 at 2:42

GoogleCodeExporter commented 9 years ago
Yes, I did. Doesn't help.

Original comment by igor.rya...@gmail.com on 20 May 2010 at 6:13

GoogleCodeExporter commented 9 years ago
Hi mate.
It still doesn't work for me.
Any idea?

Original comment by igor.rya...@gmail.com on 1 Jun 2010 at 9:37

GoogleCodeExporter commented 9 years ago
Having the same issue on Mac using adb to set up a SOCKS5 proxy via my Android 
phone. The tunnel works fine with Firefox and Foxyproxy; does not work with 
Chrome and Switchy.

Original comment by DEGoodma...@gmail.com on 19 Jun 2010 at 4:27

GoogleCodeExporter commented 9 years ago
Try removing everything from the "No proxy for" field in the profile 
configuration.

Original comment by Sam.Mel...@gmail.com on 21 Jul 2010 at 1:03

GoogleCodeExporter commented 9 years ago
Sam.Mellor's suggestion worked for me. 

Original comment by Justin.R...@gmail.com on 15 Oct 2010 at 1:30

GoogleCodeExporter commented 9 years ago
Unfortunately it doesn't for me. It's still not working so I switch proxies 
manually.

Original comment by igor.rya...@gmail.com on 16 Oct 2010 at 10:54

GoogleCodeExporter commented 9 years ago
I also have this problem, and have found the cause (I think!).

When a proxy profile is configured, Switchy writes out the details in a pac 
file. When the profile is active, the system internet settings are directed to 
use this pac file.

By looking at the pac file, I was able to see that even when the proxy is 
specified as 'SOCKS', Switchy uses the directive 'PROXY'. Hence a not-working 
pac file looks like this:

function FindProxyForURL(url, host) {
    if (shExpMatch(url, '*example.com*')) return 'PROXY 127.0.0.1:8111';
    return 'DIRECT';
}

When it should look like this:

function FindProxyForURL(url, host) {
    if (shExpMatch(url, '*example.com*')) return 'SOCKS 127.0.0.1:8111';
    return 'DIRECT';
}

When I modify it by hand, it works until I update the profile in Switchy. I 
hope this helps. I'd be interested to know if this is, indeed, the problem.

Original comment by and...@kember.net on 9 Nov 2010 at 3:11

GoogleCodeExporter commented 9 years ago
For me it doesn't work even if I save pac file with the following:
function FindProxyForURL(url, host) {
       return 'SOCKS 127.0.0.1:8111';
}
and reference it directly from browser. Any browser.
It's definitely somehow imposed by security policy my company has... but I 
don't understand how they manage to block this :)
Any ideas appreciated!

Original comment by igor.rya...@gmail.com on 9 Nov 2010 at 6:35

GoogleCodeExporter commented 9 years ago
I've managed to get Chrome + Switchy! running against an SSH tunnel using 
Tunnelier, something i noticed in your screenshots is the Listen Interface in 
Tunnelier set to 0.0.0.0, my working setup has this as 127.0.0.1.

Original comment by ja4...@gmail.com on 16 Nov 2010 at 9:27

GoogleCodeExporter commented 9 years ago
hi,
I have the same problem, the removing of "No proxy for" doesn't work for me 
also.
and...@kember.net, can you paste your working pac?

Original comment by mak...@gmail.com on 4 Sep 2011 at 3:43

GoogleCodeExporter commented 9 years ago
Yes, certainly. Here's the contents of my SwitchyAuto.pac file:

function regExpMatch(url, pattern) {
    try { return new RegExp(pattern).test(url); } catch(ex) { return false; }
}

function FindProxyForURL(url, host) {
    if (shExpMatch(url, '*ebay.com*')) return 'SOCKS5 127.0.0.1:8124';
    if (shExpMatch(url, '*ebay.co.uk*')) return 'SOCKS5 127.0.0.1:8124';
    return 'DIRECT';
}

Original comment by and...@kember.net on 6 Sep 2011 at 3:05

GoogleCodeExporter commented 9 years ago
http://www.assoass.com/   

Original comment by vipsv...@gmail.com on 15 Dec 2011 at 3:34