I'm currently running Ubuntu Server Sonarr grabs the show, passes the magnet url to qbittorrent, and qbittorrent downloads the show.
First test worked fine, except that after download, Sonarr could not access the download location So to possibly fix this, I created a folder in a publically accessible location, and changed permissions so everyone and their grandmother could access it I am NOT using a proxy.
But if I enable proxy without giving it any real proxy info, it will go away from the 'metadata' thing, and go into 'downloading' but does nothing. Once I switch back to 'none' for proxy, it then downloads a few bytes of data, then nothing. Still says "downloading" but nothing is actually being downloaded. At this point, the people going "this is an upstream issue" need to actually think about what's going on I remember I used to use it on windows as my main torrent downloader, but moved away from it ages ago and couldn't remember why I did, but figured that whatever made me want to move away must have been fixed by now Check your rate limits.
If your rate limits for upload are set to 0, then change them to something reasonable. After doing this, everything immediately started downloading, and all the stalled downloads restarted. Now though, I'm not sure if this is what they're referring to as an 'upstream issue', as I was under the impression that when they kept saying 'upstream issue' they were talking about the code being uploaded to the PPA and thus being what gets 'downloaded' to the community Although, with all this said, I do seem to still have an issue with a single download, as the download speed is unusually slow compared to everything else I'm not sure if this is just because out of all the files I've tested, this one happens to be the 'newest' as it was just uploaded today I was having the same problem here, but as you commented before about changing ports I looked for on qb and found the option to use a different port every time it initializes and it worked for me!
Hope it was helpful! I just got this problem again, and i notice this warning at the bottom of the window. But i click and goes to the Connection Tab but i don't know what to change there. It's hard to fix a bug that no one within the team is able to replicate and also seems to affect users upstream too. Just thought I'd add: I'm using qBittorrent-nox 4. Enabling "Use Random Port on Startup" fixed my issues. Also drastically improved my speeds which is a plus.
I did not have to adjust my rate limits; they are still set to 0. This isn't Docker-specific anyway. The client or the underlying lib is pretty pathetic. I'm sticking with 4. Sometimes I'll restart it after a download completes if the remaining ones are still "downloading metadata. No torrents download, hence not really usable.
I am also on windows 10, not docker. Going to lock this issue for now as it's obvious that the problem is upstream. If this does ever get fixed upstream and needs repairing in our container, please open a new issue. Skip to content. Star New issue. Jump to bottom.
Copy link. Hey, When adding new magnet torrents via webui they get stuck in "downloading metadata".. Before port modification Right after port change not even 10s So port change needs to be done every time new torrent is added to trigger the download.. I am also having this issue. This comment has been minimized. Thanks for the input. Go to NATsettings on your router - portforwarding - add new rule - fill in your port from Qbittorrent, ip address make sure TCP is enabled.
Start qbittorrent again and you should able to seed. I do not think that is the torrent in question, i only have 1 torrent in the list which must be this one "4b09etorrent' resumed. I have tried almost everything, and I'm not getting any upload speed. The only thing will be the ISP is blocking my seeding part. I have port forward enabled and tested, encryption set to enabled, not required, tracker status is working.
Sign in to your account. This is a new issue as I have used qBittorrent for several years with no problems. Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. The text was updated successfully, but these errors were encountered:.
Had the same issue. Go to settings and try another Port. EDIT: on Mojave you can use uTorrent not the web, but the normal version had never problems with that.
Sorry, something went wrong.
0コメント