uTorrent (µTorrent) torrent client cannot connect to trackers via HTTPS when using ssf as a SOCKS proxy

[ghost]

The minimal example below is not enough to proxify uTorrent, but it suffices to demonstrate the issue.

Minimal steps to reproduce:

1. Run "ssfs" on local machine

2. Run "ssfc -D 8080 127.0.0.1"

3. Download and install uTorrent Portable: https://portableapps.com/apps/internet/utorrent_portable

4. Run uTorrent, go to Options->Preferences->Connection.

5. Set 127.0.0.1 as SOCKS5 proxy and check all boxes below, except for "Authentication", then click OK.

6. Add the following torrents via Magnet URI by pressing CTRL+U:

   ubuntu-17.04-desktop-amd64.iso torrent: magnet:?xt=urn:btih:59066769B9AD42DA2E508611C33D7C4480B3857B&dn=ubuntu-17.04-desktop-amd64.iso&tr=http%3a%2f%2ftorrent.ubuntu.com%3a6969%2fannounce&tr=http%3a%2f%2fipv6.torrent.ubuntu.com%3a6969%2fannounce

   ubuntu-17.04-desktop-i386.iso torrent: magnet:?xt=urn:btih:F1C0D78784587BD43D3DD1B2F3574063DAF0C3C1&dn=ubuntu-17.04-desktop-i386.iso&tr=https%3a%2f%2ftorrent.ubuntu.com%3a6969%2fannounce&tr=https%3a%2f%2fipv6.torrent.ubuntu.com%3a6969%2fannounce

7. For each torrent, click on it in the list and go to the "Trackers" tab. You will see that the one that uses HTTPS to connect to the tracker does not work ("Proxy connect error: offline (timed out)"), while the other one works via HTTP. Of course, both work without proxy.

In the ssfs console, the corresponding connection attempts cause errors like this:

 microservice[socks]: error reading protocol version: connection reset 108

---

I have tried multiple versions of uTorrent, without luck. I think I remember having this same problem with putty/kitty as well. I've searched around for a long time and it could be that for this particular use case, only Dante (https://www.inet.no/dante/) works, but I haven't checked.

Another thing: Attempts to send UDP packets by uTorrent result in ssfs spamming "session[socks]: UDP not implemented yet". Is this at all planned? Incoming TCP and UDP appear to work fine with remote forwarding.

I don't know if anything could be done about these things, but I'd very much appreciate any opinions on this. Thanks!

[DiagonalArg]

Me too. I've been trying sshuttle with tproxy, but I also couldn't get it to work with my torrent client. I've been hunting for alternatives.

[olachere]

microservice[socks]: error reading protocol version: connection reset 108

This error can usually be seen when an application tries to use SSF as an HTTP proxy and not as a SOCKS proxy.

session[socks]: UDP not implemented yet

Unfortunately, the SOCKS implementation in SSF does not currently support UDP. Hopefully this feature will be added soon.