QBittorrent stuck at downloading metadata about docker-qbittorrent HOT 42 CLOSED

Stop adding unhelpful comments of Same Issue Here.

If you wish to report an issue, open a new issue and fill in the requested details or jump over to our discord.

from docker-qbittorrent.

I am also having this issue.

from docker-qbittorrent.

Hi guys.

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!

from docker-qbittorrent.

I can confirm the proxy issue. Add magnet link: stalls at metadata downloading (usually, sometimes it works as normal). Turn off proxy, wait for metadata to download, turn on proxy and it keeps downloads.

This is using docker inside a FreeNAS VM of RancherOS. The proxy used is privateinternetaccess.

from docker-qbittorrent.

Just updating people that this is still a thing in 4.2.5.

from docker-qbittorrent.

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..

from docker-qbittorrent.

This issue is revolved by restarting the application. In my case, it won't close properly either, so I force kill it. After restarting, it will download the metadata. After some time, any new torrent will be stuck at the metadata stage again, and so one has to keep restarting it. I don't know any better solution.

from docker-qbittorrent.

I've been having this issue since like 3.6 or 3.7 on mac OS. I just updated to 4.2 to see if this bug was fixed and was pissed to see it was stalling again.

I selected "Use different port on each startup" and it the torrents immediately moved from downloading metadata to downloading.

from docker-qbittorrent.

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..

Thanks, as a fix that works for me until a proper fix comes along.... I'm using Qbittorrent-VPN docker

from docker-qbittorrent.

Tried building this image from your git repo and added 3 new torrents:

1. got stuck at stalled
2. started downloading immediately
3. got stuck at "downloading metadata"

aaaand this is right after port change - one stuck in downloading metadata recovered immediately

from docker-qbittorrent.

We ingest this directly from their PPA, I also have not been able to duplicate this.
Try network bridge mode and pull traefik out from the equation.
I do apologize for the delay , but we do not officially support windows as a platform and I do not believe there are any changes we can make in order to resolve this bug, we simply install the package provided by upstream in a Docker container.
I will be closing this issue.

from docker-qbittorrent.

@xaxxon yup. just encountered this as well :-(

from docker-qbittorrent.

Quick update... in case anyone else needs to know:

Check your rate limits. I THINK I figured out what's causing it. If your rate limits for upload are set to 0, then change them to something reasonable. If they are set to under 25KiB/s then set them to AT LEAST 25KiB/s from my testing...

After doing this, everything immediately started downloading, and all the stalled downloads restarted. I've tested this with 5 different downloading files so far, and every time when I have the upload set to 0 (for unlimited) nothing happens, and when under 25KiB/s nothing happens. But once I set it to 25KiB/s or higher, everything started working again.

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... but now I'm wondering if they are talking about the upload of whatever "we" are trying to download.

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... suck to around 50-100KiB/s instead of 20MiB/s... 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... but I feel some more testing is needed..

from docker-qbittorrent.

OK, it wont recover by itself.. after 2 days torrent still stuck at downloading metadata..

from docker-qbittorrent.

I dont get it.. this is some nonsense.. why host install or windows install is ok but dockerzied no?

from docker-qbittorrent.

another week.. any conclusion??

from docker-qbittorrent.

I have the same problem (Mac) anyone find a solution? Doesn't happen with torrents from anywhere else but my favorite EZTV

from docker-qbittorrent.

Same issue here

from docker-qbittorrent.

Stop being an asshole. Is THE SAME ISSUE, I won't open a new issue for the same shit. No worries, already dumped this shit for another that worked instantly. Kisses

from docker-qbittorrent.

Stop adding unhelpful comments of Same Issue Here.

If you wish to report an issue, open a new issue and fill in the requested details or jump over to our discord.

If I recall correctly issue tracker is for reporting issues.. Discord is mainly for the support - no way other people would be able to track down the solution. So if you are willing to help, address problem here. That's where the google brings users not discord..

Anyway I took some time to test it from every corner and provided you with the all data about the case and noone really cared.. thanks.

from docker-qbittorrent.

According to the GitHub thread you linked to earlier, it seems to be an upstream issue: qbittorrent/qBittorrent#5006 (comment)

But in any case, if there is one report of a potential bug with additional info it is often not enough for us to troubleshoot unless we can reproduce it ourselves.

In such cases, other people jumping on with "same issue" is not helpful unless they also add their specific info that might help us identify a common denominator and perhaps reproduce the issue.

from docker-qbittorrent.

So is there something we can do to stop the issue from happening and get the torrent started automatically and if more information is required, what is required?

from docker-qbittorrent.

anyone have a solution or found anything that works?

from docker-qbittorrent.

In may case I have found a reason for that behaviour.
It works as long as I don't use proxy. As soon as I switch over to proxy it stalls (stuck at downloading metadata). Switch off proxy and restart app and it starts to download again. Every torrent I add, regardless of interface: manually, thought RSS, Web UI.

It first appeared after update to 4.2.1. I tried to downgrade with clean install but without success. 4.1.9 and 4.1.5 acted the same way. As soon as I switch to proxy it stalls at downloading metadata.

from docker-qbittorrent.

Same behaviour as macinoshee, also on 4.2.1. Works when turning off proxy. Also works again when turning proxy on after metadata has been downloaded.

If I add new magnet links after turning proxy on again, it's stuck at same issue, downloading metadata.

from docker-qbittorrent.

Yes, true. As soon as metadata is downloaded I can switch proxy on and it continues download.

from docker-qbittorrent.

I just had this issue. Force Restarting worked for me

from docker-qbittorrent.

Same problem but not in a docker, and restarting does not fix the problem.

from docker-qbittorrent.

Having this issue on Windows 10 v4.2.1. Restarting Qbit doesn't solve the problem.

from docker-qbittorrent.

Having the same issue with proxy on windows 10. also using privateinternetaccess as the proxy. quitting the application and relaunching fixes the issue temporarily

from docker-qbittorrent.

Was working fine for me at first. I'm currently running Ubuntu Server 20.04 on physical hardware, not in a docker, nor in a vm.. bare metal.

I am using this in conjunction with Sonarr.

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...

After changing the default download directory to this new folder, I've gotten stuck on 'downloading metadata' for EVERY SINGLE thing added... 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. it can see thousands of seeds and peers, yet nothing. I tried switching back to the default qbittorrent-nox/Download directory, and still nothing happens...

At this point, the people going "this is an upstream issue" need to actually think about what's going on... because its not an upstream issue at this point... its an issue with the programming, and something is broken, so work obviously needs done to it and people are just not willing to do it... 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... but if it was fixed, seems this other issue has not been...

from docker-qbittorrent.

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.

from docker-qbittorrent.

does anyone have any new workarounds for this? as @xaxxon pointed out the behavior seems to be the same on 4.2.5. using a different port on startup doesn't work anymore for me.

from docker-qbittorrent.

Exact same issue. Client is bricked as far as I'm concerned, completely unusable.

from docker-qbittorrent.

from docker-qbittorrent.

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.

from docker-qbittorrent.

Just thought I'd add: I'm using qBittorrent-nox 4.2.5 and using Torguard's SOCKS5 proxy. 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.

from docker-qbittorrent.

This isn't Docker-specific anyway. The client (or the underlying lib) is pretty pathetic. I'm sticking with 4.2.1 and have the "use random" option selected, and eventually it usually works. Sometimes I'll restart it after a download completes if the remaining ones are still "downloading metadata."

from docker-qbittorrent.

hi!
same issue
vers 4.2.5
win 10 home 64 latest vers 2004
the port random sometimes works and sometimes not at all..
really hope that the qbit dev will fix it..it is so frustrating...
:(

from docker-qbittorrent.

@methanoid I was pointing out the severity of the issue in my case. No torrents download, hence not really usable. I am also on windows 10, not docker.

from docker-qbittorrent.

@methanoid I was pointing out the severity of the issue in my case. No torrents download, hence not really usable. I am also on windows 10, not docker.

i totally AGREE with you
the sw now for me is completely UNUSABLE...
win 10 home 64 latest vers 2004
really hope at QBittorrent take care of us and fix this very frustrating BUG

from docker-qbittorrent.

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.

from docker-qbittorrent.