Closed uniextra closed 1 month ago
Full About info (screenshot will do)
Check that you have the right network interface set in the advanced settings.
this is the proxy and network interface --> this one should not be the problem, as i mentioned that by removing the proxy, downloads works perfectly.
Log(s)
No response
Log(s) No response nothing shows... (N) 2024-09-11T22:10:33 - WebAPI login success. IP: ::ffff:192.168.1.166 (I) 2024-09-11T22:11:18 - Successfully listening on IP. IP: "0.0.0.0". Port: "UTP/40820" (W) 2024-09-11T22:11:18 - UPnP/NAT-PMP port mapping failed. Message: "could not map port using UPnP[0.0.0.0]: unknown UPnP error (-1)" (W) 2024-09-11T22:11:19 - UPnP/NAT-PMP port mapping failed. Message: "could not map port using UPnP[0.0.0.0]: unknown UPnP error (-1)" (N) 2024-09-11T22:12:48 - Added new torrent. Torrent: "Anatomy xx-x-x-x-x-x-x"
when not using sock5
(I) 2024-09-11T16:53:07 - Successfully listening on IP. IP: "192.168.1.145". Port: "UTP/40820" (I) 2024-09-11T16:53:07 - UPnP/NAT-PMP port mapping succeeded. Message: "successfully mapped port using UPnP. local: 192.168.1.145 external port: TCP/40820" (I) 2024-09-11T16:53:08 - UPnP/NAT-PMP port mapping succeeded. Message: "successfully mapped port using UPnP. local: 192.168.1.145 external port: UDP/40820" (N) 2024-09-11T16:53:12 - Torrent paused. Torrent: "The Marvels (2023) 720p WEBRip-LAMA"
Why you have TCP disabled? Go to Connection
> Peer connection protocol
and enable both TCP and μTP
.
Why you have TCP disabled? Go to
Connection
>Peer connection protocol
and enable bothTCP and μTP
.
its already enabled..
In that case, logs should contain something like
Successfully listening on IP. IP: "192.168.1.145". Port: "TCP/40820"
If not, something is wrong. Better post the full log.
In that case, logs should contain something like
Successfully listening on IP. IP: "192.168.1.145". Port: "TCP/40820"
If not, something is wrong. Better post the full log.
here is the full log, i have tried enabling an disabling socks5 proxy but noting, tested same torrents on windows with the same VPN and they work
(N) 2024-09-11T16:49:21 - qBittorrent v4.6.5 started (N) 2024-09-11T16:49:21 - Using config directory: /home/root/.config/qBittorrent (N) 2024-09-11T16:49:21 - Trying to listen on the following list of IP addresses: "0.0.0.0:40820,[::]:40820" (I) 2024-09-11T16:49:21 - Peer ID: "-qB4650-" (I) 2024-09-11T16:49:21 - HTTP User-Agent: "qBittorrent/4.6.5" (I) 2024-09-11T16:49:21 - Distributed Hash Table (DHT) support: ON (I) 2024-09-11T16:49:21 - Local Peer Discovery support: ON (I) 2024-09-11T16:49:21 - Peer Exchange (PeX) support: ON (I) 2024-09-11T16:49:21 - Anonymous mode: OFF (I) 2024-09-11T16:49:21 - Encryption support: ON (I) 2024-09-11T16:49:21 - Successfully listening on IP. IP: "0.0.0.0". Port: "UTP/40820" (I) 2024-09-11T16:49:21 - UPnP/NAT-PMP support: ON (N) 2024-09-11T16:49:21 - Restored torrent. Torrent: "ipleak.net torrent detection" (N) 2024-09-11T16:49:21 - Restored torrent. Torrent: "The" (N) 2024-09-11T16:49:21 - Restored torrent. Torrent: "To " (I) 2024-09-11T16:49:21 - IP geolocation database loaded. Type: DBIP-Country-Lite. Build time: Sun Sep 1 02:47:20 2024. (N) 2024-09-11T16:49:21 - Using built-in WebUI. (N) 2024-09-11T16:49:21 - WebUI translation for selected locale (en) has been successfully loaded. (N) 2024-09-11T16:49:21 - WebUI: Now listening on IP: *, port: 9080 (N) 2024-09-11T16:49:37 - WebAPI login success. IP: ::ffff:192.168.1.166 (N) 2024-09-11T16:50:11 - WebAPI login success. IP: ::ffff:192.168.1.148 (N) 2024-09-11T16:50:12 - WebAPI login success. IP: ::ffff:192.168.1.148 (N) 2024-09-11T16:50:14 - WebAPI login success. IP: ::ffff:192.168.1.148 (I) 2024-09-11T16:53:07 - Successfully listening on IP. IP: "127.0.0.1". Port: "TCP/40820" (I) 2024-09-11T16:53:07 - Successfully listening on IP. IP: "127.0.0.1". Port: "UTP/40820" (I) 2024-09-11T16:53:07 - Successfully listening on IP. IP: "192.168.1.145". Port: "TCP/40820" (I) 2024-09-11T16:53:07 - Successfully listening on IP. IP: "192.168.1.145". Port: "UTP/40820" (I) 2024-09-11T16:53:07 - UPnP/NAT-PMP port mapping succeeded. Message: "successfully mapped port using UPnP. local: 192.168.1.145 external port: TCP/40820" (I) 2024-09-11T16:53:08 - UPnP/NAT-PMP port mapping succeeded. Message: "successfully mapped port using UPnP. local: 192.168.1.145 external port: UDP/40820" (N) 2024-09-11T16:53:12 - Torrent paused. Torrent: "The M" (N) 2024-09-11T16:53:15 - Torrent resumed. Torrent: "The M" (N) 2024-09-11T16:53:31 - Torrent paused. Torrent: "The M" (N) 2024-09-11T16:53:40 - Removed torrent and deleted its content. Torrent: "To End " (N) 2024-09-11T17:13:00 - Added new torrent. Torrent: "Be-LorD]" (N) 2024-09-11T17:44:58 - Torrent download finished. Torrent: "Be.[WMAN-LorD]" (N) 2024-09-11T20:08:27 - WebAPI login success. IP: ::ffff:192.168.1.166 (N) 2024-09-11T20:08:35 - Removed torrent and deleted its content. Torrent: "The " (N) 2024-09-11T20:14:05 - Removed torrent and deleted its content. Torrent: "Be" (N) 2024-09-11T20:17:06 - Removed torrent. Torrent: "ipleak.net torrent detection" (N) 2024-09-11T22:10:33 - WebAPI login success. IP: ::ffff:192.168.1.166 (I) 2024-09-11T22:11:18 - Successfully listening on IP. IP: "0.0.0.0". Port: "UTP/40820" (W) 2024-09-11T22:11:18 - UPnP/NAT-PMP port mapping failed. Message: "could not map port using UPnP[0.0.0.0]: unknown UPnP error (-1)" (W) 2024-09-11T22:11:19 - UPnP/NAT-PMP port mapping failed. Message: "could not map port using UPnP[0.0.0.0]: unknown UPnP error (-1)" (N) 2024-09-11T22:12:48 - Added new torrent. Torrent: "Anatomy " (N) 2024-09-11T22:17:52 - Trying to listen on the following list of IP addresses: "0.0.0.0:40820" (N) 2024-09-11T22:17:58 - Torrent paused. Torrent: "Anatomy " (N) 2024-09-11T22:18:02 - Torrent resumed. Torrent: "Anatomy D" (N) 2024-09-11T22:18:21 - Trying to listen on the following list of IP addresses: "0.0.0.0:40820,[::]:40820"
Hmm, that's strange. Try the following:
If that doesn't work, post the fresh log.
Hmm, that's strange. Try the following:
- Set the connection protocol to TCP only.
- Disable UPnP / NAT-PMP port forwarding.
- Enable your proxy.
- Restart the client.
If that doesn't work, post the fresh log.
(N) 2024-09-11T22:46:26 - qBittorrent termination initiated (N) 2024-09-11T22:46:26 - qBittorrent is now ready to exit (N) 2024-09-11T22:46:33 - qBittorrent v4.6.5 started (N) 2024-09-11T22:46:33 - Using config directory: /home/root/.config/qBittorrent (N) 2024-09-11T22:46:33 - Trying to listen on the following list of IP addresses: "0.0.0.0:40820,[::]:40820" (I) 2024-09-11T22:46:33 - Peer ID: "-qB4650-" (I) 2024-09-11T22:46:33 - HTTP User-Agent: "qBittorrent/4.6.5" (I) 2024-09-11T22:46:33 - Distributed Hash Table (DHT) support: ON (I) 2024-09-11T22:46:33 - Local Peer Discovery support: ON (I) 2024-09-11T22:46:33 - Peer Exchange (PeX) support: ON (I) 2024-09-11T22:46:33 - Anonymous mode: OFF (I) 2024-09-11T22:46:33 - Encryption support: ON (I) 2024-09-11T22:46:33 - Successfully listening on IP. IP: "0.0.0.0". Port: "UTP/40820" (N) 2024-09-11T22:46:33 - Restored torrent. Torrent: "Anatomy " (I) 2024-09-11T22:46:33 - IP geolocation database loaded. Type: DBIP-Country-Lite. Build time: Sun Sep 1 02:47:20 2024. (N) 2024-09-11T22:46:33 - Using built-in WebUI. (N) 2024-09-11T22:46:33 - WebUI translation for selected locale (en) has been successfully loaded. (N) 2024-09-11T22:46:33 - WebUI: Now listening on IP: *, port: 9080 (N) 2024-09-11T22:46:48 - WebAPI login success. IP: ::ffff:192.168.1.166 (N) 2024-09-11T22:47:11 - WebAPI login success. IP: ::ffff:192.168.1.148 (N) 2024-09-11T22:47:35 - Torrent paused. Torrent: "Anatomy " (N) 2024-09-11T22:47:38 - Torrent resumed. Torrent: "Anatomy" (N) 2024-09-11T22:47:40 - WebAPI login success. IP: ::ffff:192.168.1.148 (N) 2024-09-11T22:47:44 - WebAPI login success. IP: ::ffff:192.168.1.148
Same result, cant download
Same result, cant download
Ok, you could re-enable that settings then.
The log looks fine actually. And there is no apparent proxy connectivity issues, it spits something like SOCKS5 proxy error
messages in that case. So it's unclear what's wrong.
Idk, maybe try to play around with the network interface setting. This also could be external thing like firewalls etc.
SOCKS5 proxy error
is very generic. Is there a way to make it more granular ?
Such messages show some additional info. Like "Connection refused". But the OP doesn't have anything in the logs, so it's irrelevant anyway.
OK i figure it out, the problem was with the password, i did a curl --socks5 amsterdam.nl.socks.nordhold.net:1080 - -proxy-user user:pass http://ifconfig.me and validated that worked and then added the same data to qb and tadah! working now! I think some more logging information would have helped troubleshoot
thanks for the help
qBittorrent & operating system versions
qbittorrent 4.6.5 NAS with arm32v7 installed via entware Proxy provider NordVPN
What is the problem?
I have this exact setup on the same network on 2 windows laptops and it runs perfectly, but on linux on my NAS is not working at all, it keeps torrents searching for metadata. i verified that the NAS has access to the VPN via netcat amsterdam.nl.socks.nordhold.net [213.152.176.251] 1080 open so it seams to be a problem of the program itself.
Steps to reproduce
No response
Additional context
No response
Log(s) & preferences file(s)
No response