@zwinna try some downloads on a different client to be 100% sure that the problem is qbt

Joker here. I tested this from our side today rather than assuming, so here is where it actually stands. Every announce URL we hand out is up and answering right now. I checked all four of them: https://tracker.gaytor.rent/<passkey>/announce http://tracker.gaytor.rent:2710/<passkey>/announce https://tracker.gaytorrent.ru/<passkey>/announce http://tracker.gaytorrent.ru:2710/<passkey>/announce All four answer normally, on both the HTTPS port and on 2710. So there is no outage here, and @ianfontinell called it correctly: "no such host is known" is your machine failing to resolve the name, before any connection to us is even attempted. The one thing that may actually help you: the tracker answers on two different hostnames, tracker.gaytor.rent and tracker.gaytorrent.ru. It is the same tracker behind both. If your provider is filtering one of the two names, the other one often still resolves. So it is worth editing the tracker URL in your client and swapping the hostname, keeping the rest of the URL and your passkey exactly as it is. Also worth doing either way: redownload the .torrent file from the site and load that one. That always gives you the current announce URL with your passkey in it, which rules out an old file pointing somewhere retired. @Nothinglose if that still leaves you stuck, I can dig further, but I need a bit more than "not working": The exact announce URL your client shows in the torrent's tracker tab, with the passkey part replaced by xxxx before you post it. Which of the two hostnames you tried, and whether either of them resolves for you. Roughly which country and which provider you are on, and whether you are on a VPN. Post that and I will take it from there.

@Kevin4fm Thank you replying, I'll try doing this because yeah, I don't wanna play for getting more radio... ️

@heiheihei333 I believe what @Joker explained works the same for everyone by default, not something that was done for one individual member. If you're facing a similar issue - being unable to download new torrents because you have no download slots available - it may be worth double checking things are as you think they are. For example, are you aware there's a daily download limit? This varies member-to-member based on a combination of things like your ratio, whether you've donated recently, how many new torrents you've uploaded, and how many you're seeding. I don't recall what it is, but it's pretty high. I don't think I've ever hit mine, and there have been times when I've downloaded an awful lot in one day. If you know that's not the cause, and you believe you're not subject to any bad ratio restriction, try pausing all those partially downloaded torrents where you've grabbed what you want, so only those that are active right now are still running. Give it an hour, then see if you can download new stuff. If it then works, you can restart your paused torrents - I'd suggest in small batches - and see if the problem has been cured or if it returns. If it does, you can at least then give a lot more information about your own situation which should help identify where the problem might lie in your particular case.

@Kevin4fm yup and i can see which piece is downloaded so i can just forward and rewind to the spot where it has been DLed also qbittorrent have good stuffs too. it shows u folders on the content. and also later on u can choose easily which one u want to DL or not by clicking on check/uncheck mark [image: 1784628734609-872f70c0-940c-45c0-979d-98bc88eba9de-image.jpeg]

@ianfontinell okay it's working, it's tthe DNS issue, all good noww

Freeleech is applied at the moment your client reports traffic to the tracker, not at the moment you click download. So if the freeleech timer runs out while you are still downloading (or just before your client sends its next update), everything reported after the timer ends counts as normal download. That is most likely what happened here with only 8 minutes left on the clock. Best practice: grab freeleech torrents early in the window, not in the last minutes. If your numbers still look wrong to you, open a ticket via Support and we will check your account.

@moonfilms00i8 There are no seeders right now, so you won't be able to download. You can press the Request Reseed button to ping people who have downloaded in the past in the hopes that they still have it and can seed, but it's very hit and miss. Sometimes you just won't get it. Ever. The good news is that it doesn't hurt to keep it open in your torrent client in the hopes that it comes back at some point.

@willingmouth yeah i agree on this, doesnt have to be good quality but if the torrent is big then there should be preview for each file indicating which one is which that was my point

@ianfontinell thx

Quick update: the tracker timeouts a few of you ran into have been fixed on our side. Give it another try and announcing / downloading should work again. If you still hit a timeout, reply here and let me know.

@Kevin4fm said: @zwinna I've noticed it too and it did, at least initially, seem to be linked via timing to the new site rollout. I had to update my qBittorent version recently - for a mainly unrelated reason - and this definitely saw an improvement. Not a complete resolution though. My maximum d/l speed is 8mb/s. Before "everything" I was regularly achieving this, obviously depending on how well seeded the torrents I was leeching were, and/or how many torrents I was leeching at the same time. After the rollout (at least seemingly that timing) it dropped to about 4mb/s. Upgrading my client has moved it up to around 6.5mb/s sometimes, though not that often. However, when I d/l from ThePirateBay, again a site that usually went up to 8mb/s for the more popular torrents I was leeching, my total max is still around 6.5mb/s. So that suggests it is an ISP throttling issue, at least in part. I'm loathe to actually ask them though, for fear of an "Ah yes, we've been wanting to talk to you!" response! thank you, kevin!

Sorry about this one. That "server error / non-JSON" on the image step isn't your uploads, it's our end. We traced it to some heavy search queries overloading the servers, which then makes the picture upload time out. We're fixing the search side today and it's already better. Give it another go, and if a few pics fail just re-add those, they'll attach to the same upload. Thanks for hanging in there.

The problem has resolved itself after the site update [Looks awesome!]. Everything is working fine so far. Though I still went to the folder properties and checked what I figured was full access for all files. Thank you for your attention to the matter.

@ianfontinell found the issue, apparantly my firewall block the access to write something from the apps even tho there's no issue about virus. thank you for answering my question, have a good day!