Pirate bay torrents stuck at downloading metadata

When you reach the Pirate Bay site, you can search for the file you are looking for. After this, the download process is the same. Find your file, click download, and drag it to your Bittorrent Client. When the file is finished downloading, you can click out of your VPN and enjoy the torrent. Vuze is another popular client torrent app. It comes in two different versions: a free one, and a paid version. Here we will focus on the free one. The paid version has some extras advantages, such as been ad free, but for the purposes of using Vuze with the Pirate Bay, the free app is good enough.

The latest link to thepiratesbay. This link is still working! You will be directed to the download site, and asked to save the installer on your machine.

Attempting to access ThePirateBay. Step-by-step instructions inside. Step 3: now that you have the installer ready on your machine, open it. Wait for all the items of the program to download. Step 4: confirm that you are 18 years or older, and that you agree to the terms of service and privacy policy. 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. 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 Alright, I occasionally stil get this Downloading metadata and sometimes, after like 1 Minute, it starts downloading and other times it just stucks at this.

I think it happens with older torrents more often that with newer ones. Twice or three times I tried Get Torrent File like suggested by SectorVector and it worked but not sure if it happened by chance. Anyway, if this happens again I would like to give you the link just to see if you get the same message or not.

Aug 10, , pm Cov Wrote: Alright, I occasionally stil get this Downloading metadata and sometimes, after like 1 Minute, it starts downloading and other times it just stucks at this. Thanks Functionally there is NO difference between the magnet link and the "get torrent file" link. One gets the torrent metadata from the swarm, the other comes in a file. The latter will always work, when it is available.

It is available for smaller swarm because sometimes it is difficult to connect to a peer that can reliably deliver the metadata. Wow hey, sorry but that's like rocket science to me I'm a total noob in networking stuff. The short short version is that it doesn't matter which link you click - the end result is the same. It will always work - so long as the torrent file server is available, and torrent file downloads aren't blocked.

Even for smaller swarms it should still work, but it may take a little longer to connect to a peer that can and will share the metadata. 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. It shows many seeds and peers but it is not fetching the torrent file. Both uTorrent and Tixati is able to download the torrent file.

Which qbt version and OS are you using? I do not use ipfilter. Can you update to v3. How are you connected to the internet? I am willing to try it. The longer you wait, the less likely I can reproduce the bug.

How did you get that stacktrace?