Thanks for flagging this, and thanks bi85qad for the clear description, and ianfontinell for pointing at the default categories, that was exactly the right lead.

You were both right about the cause. A change had crept in where typing a search term would quietly limit your results to your default categories (the ones set at My > Content). So if the thing you searched for lived outside those categories, you would get few or no results, and picking a category manually was the only way around it. Not what anyone expects when they just type a word into search.

That is now fixed: a keyword search looks across all categories again, like it used to. Your default categories still apply to the plain browse/landing view (that is what they are for), and if you deliberately pick categories for a search, those are still honoured.

No action needed on your end, just give search another try. Shout here if anything still looks off.

Staff note: thanks for all the testing in this thread, it was genuinely useful. The concrete points raised here (seeder columns, uploader name display, list contents, .torrent creation date, download issues after the switch) have been picked up into our internal tracking, and several are already fixed. Closing the triage entries for this thread; anything still broken for you today, just open a fresh thread or a helpdesk ticket.

Staff here. Your site account is fine and not blocked, so nothing is wrong on that side. Two questions so we can pin it down: are you trying to log in on the website itself, or inside the GUU tool? And what exactly happens, an error message or just a bounce back to the login form? If the website works but GUU does not, the tool may need an update since logins got stricter recently, and that would be good for vancer to know. If the website itself rejects you, do the forgot-password reset MrMazda suggested and check that you log in with your username, not your email.

Staff here. This is how visibility works: a fresh upload stays non-visible until our tracker sees the first seeder, there is no approval queue. The usual fix when uTorrent says seeding but the site disagrees: delete the torrent you created locally from the client, download the .torrent file from your own upload page here, add that one to uTorrent pointing at your original files, then force a re-announce. That version carries your personal announce key, which the self-made one does not. It should flip to visible within a minute or two of the tracker seeing you. If it still stays invisible after that, tell me the torrent name and I will check the tracker side directly.

No worries on this one: using a VPN or a dedicated IP is completely fine and does not get an account terminated. Cheating detection is about behaviour, not about what IP you connect from, and plenty of members seed from dedicated servers or seedboxes. Just keep your account to yourself as usual and you have nothing to worry about.

Quick pointers on this. The six-digit code only exists if you turned on two-factor authentication yourself at some point: it's the rotating code inside the authenticator app (Google Authenticator, Aegis, etc.) you scanned the QR code with back then. If you never set that up, the site won't ask you for one. If you couldn't log in over the last days without ever enabling 2FA, that was most likely a site-side login issue we fixed yesterday, so please just try again. And if you're genuinely locked out (lost the app or the recovery code), contact the helpdesk from the email address registered to your account and we'll sort it out there.

ianfontinell has it exactly right. Nothing is being deleted within minutes. A torrent only shows in browse and search while the tracker sees at least one seeder, and that check runs every minute. So if the uploader's client stalls or closes, the upload drops out of the listings a minute later, but it still exists on the tracker and comes right back the moment they seed again. Actual removal only happens when an upload never gets its initial seed for more than 3 days. So if your fresh upload vanished: start or fix the seeding in your client and it will reappear on its own.

The six-digit code is the one-time code from the authenticator app (Google Authenticator, Authy, etc.) that you set up when you enabled two-factor login under Settings > Security. If you've lost access to that app, just message the Helpdesk and we'll turn two-factor off for you so you can sign in with your username and password again (and you can re-enable it later if you like). If you never turned on two-factor, you don't need a code at all. Sorry for the hassle!

Just to set minds at ease: the tracker and downloads are healthy across the site right now, there's no outage on our end. We had a brief server hiccup on the 24th that mostly affected uploads, but that's been sorted for a while now.

ianfontinell has this spot on, what's happening here is a VPN/client thing rather than the site. A few things that usually fix it:

• Open https://tracker.gaytor.rent/stmdd in a browser. If that page loads for you, the tracker is reachable and the issue is between your client and us.
• In qBittorrent, bind it to your VPN's network adapter (Options > Advanced > Network Interface) so it stops announcing your other IPs. Out of the box qB lists every address, and the ones not routed through the VPN show as "not working", which is expected.
• Make sure split-tunneling is off so all torrent traffic actually goes through the VPN, and that your VPN allows P2P on the endpoint you're connected to.
• If your VPN puts you on CGNAT or IPv6-only, try an endpoint that gives you a normal IPv4 address.

Give that a go and let us know if anything is still stuck, with your torrent and client details, and we'll dig in.

Welcome aboard. 0 kB/s upload usually means your torrent client can't accept incoming connections, so other peers can't reach you to pull data from you. Two things fix it most of the time: make sure your client's listening port is open/forwarded in your router (or turn on UPnP / NAT-PMP in the client settings), and if you're on a VPN, use one that supports port forwarding. Also double-check the client is actually seeding the completed files. Once peers can connect to you, your upload will pick up. Let us know if it's still stuck after that.

Quick update from the team — this is fixed now.

Uploading torrents and adding pictures were failing for a few hours because of a technical problem on our side (nothing to do with your torrents or your accounts). It is sorted and everything is back to normal — new uploads are flowing again.

Sorry for the disruption, and thanks for the reports, they helped us pin it down fast.

Quick update from the team — this is fixed now.

Uploading torrents and adding pictures were failing for a few hours because of a technical problem on our side (nothing to do with your torrents or your accounts). It is sorted and everything is back to normal — new uploads are flowing again.

Sorry for the disruption, and thanks for the reports, they helped us pin it down fast.

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.

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.

Welcome aboard. Short version: ratio is how much you share back versus what you download. New accounts get a bit of starting buffer, and the trick is to keep seeding what you grab and look out for freeleech torrents (those don't count against your download). The folks above gave you good tips too. Shout if you get stuck.

Thanks for the kind words. Copy buttons for title and tags on the grid would be handy, noted.

Solid one, saving the form as you go so a failed submit doesn't wipe it. Noted, and we're fixing the upload failures that make it sting in the first place.

Thanks for the screenshots. That "slow down" page when you click a picture isn't meant to happen, our bot-protection is being too trigger-happy on the image viewer. I'm looking into it. A refresh usually clears it for now. I'll report back once it's sorted.

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.