SOCKS5 proxy error op:sock_read ec: End of file

xeon826 commented 1 year ago

qBittorrent & operating system versions

qBittorrent: v4.5.3 x64 Operating system: Ubuntu 22.04 jammy Qt: 5.15.2 liborrent-rasterbar:

libtorrent-rasterbar20:
  Installed: 2.0.7.git20220822.7bb4b410d7-1ppa1~22.04
  Candidate: 2.0.7.git20220822.7bb4b410d7-1ppa1~22.04
  Version table:
 *** 2.0.7.git20220822.7bb4b410d7-1ppa1~22.04 500
        500 https://ppa.launchpadcontent.net/qbittorrent-team/qbittorrent-stable/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status
libtorrent-rasterbar2.0:
  Installed: 2.0.9.git20230529.73089332ab-1ppa1~22.04
  Candidate: 2.0.9.git20230529.73089332ab-1ppa1~22.04
  Version table:
 *** 2.0.9.git20230529.73089332ab-1ppa1~22.04 500
        500 https://ppa.launchpadcontent.net/qbittorrent-team/qbittorrent-stable/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status
     2.0.5-5 500
        500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages

What is the problem?

When using a SOCKS5 proxy I get the following error in the execution log: 6/14/23 5:12 PM - SOCKS5 proxy error. Message: "SOCKS5 error. op: sock_read ec: End of file ep: 165.234.220.168:1080 I could be wrong but I have a feeling it's to do with an incompatible version of rasterbar because everything was working fine before I installed a different version of it then this error started occurring.

Steps to reproduce

In preferences > Connection > Proxy Server > Type choose "SOCKS5"
Use appropriate host and port settings for your SOCKS5 proxy in this section
Check "Use proxy for peer connections"
Uncheck "Use proxy only for torrents"
Check "Use proxy for hostname loopups"
Check "Authentication" and fill out accordingly

Additional context

I have a feeling it's to do with my libtorrent-rasterbar version, what version is appropriate for qbittorrent 4.5.3? What steps should I take to install the correct version and does it involve purging any config files or things of that nature?

Log(s) & preferences file(s)

No response

Balls0fSteel commented 1 year ago

I get this too at times, but it doesn't affect proxy usage whatsoever. I get to seed, download, etc.

These are my "errors":

2023. 06. 19. 11:59 - SOCKS5 proxy error. Message: "SOCKS5 error. op: handshake ec: The semaphore timeout period has expired ep: "
2023. 06. 19. 11:59 - SOCKS5 proxy error. Message: "SOCKS5 error. op: sock_read ec: The semaphore timeout period has expired ep: "

So I think it's completely safe to ignore these. (I am on Windows 11, it happened on pretty much any version, lt20 build, and dante proxy.)

EnderofGames commented 1 year ago

New user, I get these errors, and my download and upload all screech to a halt, and never startup again. I just recently started using qbittorrent, moved from always using utorrent.

After five to ten errors, it just stops attempting to do anything. Sometimes the errors take hours to arrive, sometimes they are here from the getgo. I just restart qbittorrent over and over to get anything to work.

2023-09-25 4:13 PM - SOCKS5 proxy error. Message: "SOCKS5 error. op: sock_read ec: End of file ep: 185.184.228.137:1080"
2023-09-25 4:09 PM - SOCKS5 proxy error. Message: "SOCKS5 error. op: sock_read ec: End of file ep: 185.184.228.137:1080"
2023-09-25 4:08 PM - SOCKS5 proxy error. Message: "SOCKS5 error. op: sock_read ec: End of file ep: 185.184.228.137:1080"
2023-09-25 4:07 PM - SOCKS5 proxy error. Message: "SOCKS5 error. op: sock_read ec: End of file ep: 185.184.228.137:1080"
2023-09-25 4:06 PM - SOCKS5 proxy error. Message: "SOCKS5 error. op: sock_read ec: End of file ep: 185.184.228.137:1080"

Changing the proxy address hasn't helped. Windows 10.

Seeing other instances of this error online leads to NordVPN, also the VPN/Proxy I am using. I contacted them for help. They instructed me to:

In connections, uncheck the Use UPnP / NAT-PMP port forwarding from my router
In connections, enable Use different port on each startup
In speed, uncheck the Apply rate limit to uTP protocol

I did the first and third, but couldn't find the second option. I don't know if it was an old option, or if it would help, but I will assume not. This did not remove the issue.

According to the tech support rep:

Some torrents may not work with NordVPN proxies, or proxies in general, simply because Trackers, not seeders themselves, will block any connection when the torrent client reports that it is using proxies. We cannot circumvent this block, as it is impossible to hide the fact that a torrent client is using proxies.

I'm not sure how true this is, I thought the point of DHT and PeX allowed you to find peers and ignore trackers (both of which I have enabled, and I see peers and leeches, but have no upload/download).

The easy and obvious way around this is to use the normal NordVPN app/connection on my computer. The app killswitch is a minor safety, obviously not as good as using the proxy. The P2P servers also supposedly work faster... a minor convinience for a potential ip leak if the killswitch doesn't work.

I'm also not certain in the end if this is a qbittorrent issue, or a NordVPN issue. It's been a while since I've used uTorrent, the last application I used to use for torrenting, and I don't recall having any similar issues with trackers.

tippetta commented 1 month ago

I'm running into the exact issue as EnderofGames. Support provided me with the same instructions--hasn't helped. Something seems broken on NordVPN's end.

qbittorrent / qBittorrent