mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
SOCKS5: Invalid argument #16797
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#16797
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @angrynode on GitHub (Apr 21, 2025).
qBittorrent & operating system versions
qBittorrent: 5.0.4 x64
Operating system: Endeavour OS
Qt: 6.8.2
libtorrent: 2.0.11.0
What is the problem?
When using a SOCKS5 proxy via SSH, it seems like nothing is proxied. The DHT does not find nodes and downloads don't start. I did not try with torrent files with explicit trackers.
Steps to reproduce
No response
Additional context
No response
Log(s) & preferences file(s)
My logs are filled with:
Which translates to
SOCKS5 proxy Error. Address: [::1]:1337. Message: "Invalid argument".@HanabishiRecca commented on GitHub (Apr 21, 2025):
Of course DHT doesn't work. Because DHT uses UDP, but SSH only supports TCP tunnels.
You need some other proxy solution which supports UDP.
@angrynode commented on GitHub (Jun 19, 2025):
now i understand this. But it should be visible in GUI settings to avoid confusion dont you think?
@HanabishiRecca commented on GitHub (Jun 19, 2025):
Meh, regular users don't use SSH tunnels. But ones who do should be smart enough to figure that out.
Also there could be many other protocols with the same issue, we are not a wiki division to describe them. Learning capabilities of a protocol is responsibility of ones who use it.