Version 2.0’s SOCKS 5 Proxy Not Working

[neildaniels]

I’m running version 2.0 on an iPhone 4 and iPad, both running 4.2b1. The HTTP proxy works fine, but the SOCKS 5 proxy does not work. I am not sure if this isolated to iOS 4.2 or if it is an inherent problem of iProxy 2.0. The SOCKS 5 proxy works fine on older versions of iProxy.

I did notice that the port numbers are different in 2.0 and have made the necessary changes on my Mac’s network settings to reflect that. I also made sure I turned on the SOCKS 5 proxy from the application, via the ON/OFF toggle.

Is there some additional changes or settings I should be looking at?

[tcurdt]

It appears there is still a problem with the on/off of the socks proxy. Please shut iProxy down (in the recent applications, hold, press minus) and then try again. If it works then it was the known problem with socks restart.

[neildaniels]

I tried completely quitting the application and relaunching it; no improvement. It relaunches and restores the “ON” state of the toggle for the socks proxy.

(didn’t mean to close this)

[bearmarch]

I'm getting "forked failed" message in the debugging console every time I attempt a request on the computer through the SOCKS proxy.

[thully]

I'm on iOS 4.1 on my iPhone 4, and I'm seeing the same issues as have been reported here. I can't use the SOCKS proxy at all, and restarting iProxy seems to make no difference. I made sure to update the ports and everything to match those used in 2.0. SOCKS previously worked in iProxy 1.0 on the same device/OS, and HTTP works in 2.0. Is everybody seeing this issue on all hardware revisions?

[jeromelebel]

The "forked failed" problem is fixed on my branch. But I still have a bug to turn off socks proxy. So it will be always on once you turn it on (even if the switch is off in the UI).

[freerobby]

Hey Jerome,

Would you recommend using your fork at this point? I had the same issue with SOCKS failing in 2.0.

[tcurdt]

Not all software has SOCKS support. I added it for a reason. HTTP proxy support is more common.

[Qythyx]

What about HTTPS, should that be going through the HTTP proxy (it doesn't work for me) or through SOCKS (also not working)? I'm trying this via Safari on a Mac.

Normal HTTP works, but no other protocols or HTTPS.

[sqs]

jeromelebel, I am using your fork and am still having problems with the SOCKS proxy (iPhone 4, iOS 4.2). The relevant entries of the device log are as follows. I'll try to look into the code later to fix this myself, too.

Wed Dec 15 14:23:32 sqs-iphone mDNSResponder[20] : Bad service type in sqs-iphone._iproxysocksproxy._tcp.local. Application protocol name must be underscore plus 1-15 characters. See http://www.dns-sd.org/ServiceTypes.html

Wed Dec 15 14:23:32 sqs-iphone mDNSResponder[20] : Bad service type in ._iproxysocksproxy._tcp.local. Application protocol name must be underscore plus 1-15 characters. See http://www.dns-sd.org/ServiceTypes.html

Wed Dec 15 14:23:32 sqs-iphone mDNSResponder[20] : Bad service type in sqs-iphone._iproxysocksproxy._tcp.local. Application protocol name must be underscore plus 1-15 characters. See http://www.dns-sd.org/ServiceTypes.html

Wed Dec 15 14:23:32 sqs-iphone iProxy[762] : socks proxy start

[benguild]

I can confirm that the SOCKS Proxy in this is not working for me. It's really sad because the HTTP/S proxy works great. Also, this other project works with SOCKS ... http://code.google.com/p/iphone-socks-proxy/ ... but not iProxy.

I can't even telnet to the port number for SOCKS. I've tried everything. It just rejects the connection.