Open GoogleCodeExporter opened 9 years ago
Did you select the proxy profile "Tunnel" from Switchy menu?
Original comment by Mohamma...@gmail.com
on 19 May 2010 at 2:42
Yes, I did. Doesn't help.
Original comment by igor.rya...@gmail.com
on 20 May 2010 at 6:13
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
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
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
Sam.Mellor's suggestion worked for me.
Original comment by Justin.R...@gmail.com
on 15 Oct 2010 at 1:30
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
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
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
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
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
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
http://www.assoass.com/
Original comment by vipsv...@gmail.com
on 15 Dec 2011 at 3:34
Original issue reported on code.google.com by
igor.rya...@gmail.com
on 19 May 2010 at 2:06Attachments: