Date: Tue, 25 Dec 2012 11:52:06 -0800 From: Garrett Cooper <yanegomi@gmail.com> To: Yuri <yuri@rawbw.com> Cc: freebsd-net@freebsd.org Subject: Re: Why chrome and firefox can't connect to almost any SOCKS4 proxy? Message-ID: <CAGH67wTwu7sb=JPGWK0ELj7r0PZv9gnfwECO_2aUc_hUf47vkQ@mail.gmail.com> In-Reply-To: <CAGH67wRipaHgtznXcZuTZDg9HARp37D%2Bt9zWRQNJiVvfKV__NQ@mail.gmail.com> References: <50D94D04.90302@rawbw.com> <CAGH67wRipaHgtznXcZuTZDg9HARp37D%2Bt9zWRQNJiVvfKV__NQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 25, 2012 at 11:48 AM, Garrett Cooper <yanegomi@gmail.com> wrote: > On Mon, Dec 24, 2012 at 10:51 PM, Yuri <yuri@rawbw.com> wrote: >> I tried many SOCKS4 proxies from >> http://sockslist.net/proxy/server-socks-hide-ip-address and mostly I am >> getting this error: >> Error 120 (net::ERR_SOCKS_CONNECTION_FAILED): Unknown error. >> Only one of them succeeded. >> SOCKS5 however works ok. >> >> On firefox I am getting similar symptoms, it can't connect to most SOCKS4 >> proxies and can connect to SOCKS5. >> >> What might be a problem? I was thinking that maybe some system or port >> library has some issue related to SOCKS4? Maybe libssl.so ? > > Try trussing/ktrace'ing the process to see if you can get a bit > more diagnostic information. If that doesn't yield anything helpful, > you might want to consider possibly going to the forums to ask this > question because this seems like something that is application > specific that wouldn't necessarily be well tied to -net@. > HTH, > -Garrett Also, check for firewalls/filtering being done by your ISP and hops in the middle, make sure there's support on the server end for SOCKS4, etc. -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGH67wTwu7sb=JPGWK0ELj7r0PZv9gnfwECO_2aUc_hUf47vkQ>