Does it download? Have you set an ipfilter? If yes, it probably blocks those ips. Doesn't work. Updated and tested. Still the same behavior. The ips are getting blocked several times in a row. I am directly connected to internet using ethernet. No, sorry, I am not allowed to share those magnet links. I might be able to provide you a build with libtorrent 1.
However only v3. Are you using a private proxy? Are you allowed to use v3. Why do you ask? Do not the alpha support it? Can you try my latest alpha build? Only one version is possible.
It shouldn't corrupt anything. You can backup the 2 qBittorrent folders found in Windows XP :. I have installed the alpha version but it do not work. I have a quad core cpu. I made a new build. Can you test it and tell if you have the same issues? There is high probability that you don't get any ip blocked messages now. I have disabled that. Remind me in the weekend to prepare for you a new msvc build. Then I want you to create a mini dump from process explorer.
The build you're using is build with gcc and it has different symbols and I am not sure I'll be able to get the minidump to work with gdb.
I have the same problem with version 4. On three popular torrents with over reported seeds, I was stuck at "downloading metadata" for an hour with no peers or seeds found.
I downloaded Deluge onto the same system and set up my proxy info exactly as I have it in qBittorrent, and it started downloading all torrents immediately. The log doesn't reveal anything interesting as far as I can see; just routine actions such as "torrent added. I'm on 4. I suddenly can't seem to get any to start downloading. Yea no I will just close this, it was a issue. Skip to content. Star New issue. Jump to bottom. Copy link. If I add new magnet links after turning proxy on again, it's stuck at same issue, downloading metadata.
Yes, true. As soon as metadata is downloaded I can switch proxy on and it continues download. 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. The proxy used is privateinternetaccess. I've been having this issue since like 3. I just updated to 4. I selected "Use different port on each startup" and it the torrents immediately moved from downloading metadata to downloading. Having the same issue with proxy on windows Thanks, as a fix that works for me until a proper fix comes along I'm using Qbittorrent-VPN docker.
Was working fine for me at first. 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. Sign in to view. Stop adding unhelpful comments of Same Issue Here. I just had this issue. Force Restarting worked for me.
Same problem but not in a docker, and restarting does not fix the problem. Having this issue on Windows 10 v4. Restarting Qbit doesn't solve the problem.
0コメント