Closed rayun56 closed 1 year ago
this only became an issue starting on February 2nd. I know it has worked until at least January 29th.
Do you use some intermediate builds of qBittorrent? v4.5.1 was released yesterday, and v4.5.0 was released more than two months ago.
Trying to download torrents from a remote HTTP link to the .torrent file (ex:
https://nyaa.si/download/1635565.torrent
) fails to download. No error message is given in the WebUI and even the WebUI API returns a200
status code. Downloading the same torrent through a magnet link works, and I am able to download the .torrent file directly from the URL on the same machine.
Cannot test it since it returns 502 - Bad Gateway
for me in any case.
even the WebUI API returns a
200
status code.
This is normal, since everything is OK with the request to the qBittorrent Web API itself, and the file download itself is started asynchronously.
- Find a remotely available .torrent file, such as https://nyaa.si/download/1635565.torrent
- Tell qBittorrent to download that URL through the WebUI's "Download from URLs" interface or the API
Works for me in 4.5.0 and 4.5.1, WebUI and GUI.
Sorry for not digging further before submitting the issue! It seems that the issue resides in my VPN setup, not in qBittorrent. Closing the issue
qBittorrent & operating system versions
qBittorrent: 4.5.1 x64 Operating system: Ubuntu Server 22.04 x64 Qt: 5.15.3 libtorrent-rasterbar: 2.0.8.0
What is the problem?
Trying to download torrents from a remote HTTP link to the .torrent file (ex:
https://nyaa.si/download/1635565.torrent
) fails to download. No error message is given in the WebUI and even the WebUI API returns a200
status code. Downloading the same torrent through a magnet link works, and I am able to download the .torrent file directly from the URL on the same machine.Strangely, I am also able to download torrents from a URL that does not directly link to the .torrent file, such as
https://archlinux.org/releng/releases/2023.02.01/torrent/
Steps to reproduce
https://nyaa.si/download/1635565.torrent
Additional context
Judging by some of my automated script logs this only became an issue starting on February 2nd. I know it has worked until at least January 29th. Issue persists across multiple reboots and an upgrade to 4.5.1
Log(s) & preferences file(s)
Relevant log file snippet:
Configuration: