That’s helpful; this sounds like a docker issue or qBit issue then. The default qBit location for torrents is /downloads, but you’d need to make sure to point it towards the container volume mapping you’re setting up in docker.

my relevant qBittorrent compose volume mapping is as follows:

    volumes:
      - /volume1/shared/torrents:/data/torrents

Personally, I don’t separate my torrent downloads by type; I use incoming & completed folders. Here’s how I set up my qBittorrent config:

This should just be part of configuring Sonarr/Radarr settings correctly. Do you have a red message in the settings that says a download client is missing, or have you filled out the download clients settings section with your torrent client info? If yes, have you checked the “auto import from client” box? and, have you set your root library folder in the media management section?

Yeah after some googling I’m kinda thinking this is a fake screenshot, idk

Damn, never seen that before. Is it a windows 11 thing? It’s looking more and more like I’ll have to move to linux on my desktop, I guess.

Edit: hard to find a source for the image; I assume if it was real there’d be a lot more reports of this online but I’m not seeing those.

Probably stating the obvious, but keep the obscure stuff around! You might not get upload immediately but the longer you seed it, the more chance someone else who wants it will come along and you get some of the upload. the most real upload I’ve ever gotten on TL (talking 1.2/1.5/1.9 ratio, absolutely insane ratio to have on a home network for a TL torrent imo) was from submitting a reseed request for several super obscure boxsets that had other leechers and no seeders.

but do watch out for downloading any more non-freeleech stuff from TL if your ratio is already poor, as that’ll dig you into a bigger hole than just letting what you’ve already grabbed seed.

Glad I could help! Most of my TL ratio comes from the seeding time point system, but all of the torrents I have real ratio on are freeleech TV boxsets (which I find TL is pretty generous about providing). Seeding large-file-size torrents gives a bonus to the points generated, so if you have the space and find yourself gaining points too slowly to bring your ratio where you want it, I’d recco nabbing a few of those boxsets to seed long term as well.

Are you getting upload on public torrents with a large number of leechers, like YTS or similar? I’d test that first.

If you are getting upload on a large public torrent, then it’s because TorrentLeech is really hard to get real upload on; your best bet is to seed your TL torrents as long as possible (ideally forever) and build your ratio by buying upload from the points store.

If you’re not able to upload to public torrents then yeah it’s probably a setup issue.

Another vote here for ProtonVPN, though it doesn’t support port forwarding via a GUI on Linux, only OpenSSL and Wireguard configs. I set it up with gluetun, qBittorrent, and qBittorrent-natmap and and it just works.

Unfortunately migration isn’t built into Lemmy yet, but I’d guess it’s on their feature wishlist.

Never heard of them, but just looking at a registrar comparison chart, their renewal costs are pretty high. eg. $20 for .wiki renewal at Porkbun and $30 at Hover. Maybe they bundle in a lot of services along with it that make the price worth it? but unless you’re taking full advantage of those (if they’re offered) then you could def get a better deal elsewhere.

Namecheap has okay starting prices but man their renewal prices aren’t great compared to other registrars.

I just transferred all my domains out of Namecheap into Porkbun. I think Porkbun is 10 to 50 cents more expensive than Cloudflare, but they seemed a bit easier to use and could hold all my TLDs. So far, a way better experience than Namecheap!

Glad to help! If you end up referencing my PDF and have any questions, feel free to shoot me a message.

Re: port forwarding, if you don’t have it, it’s kinda like a one-way mirror? Your torrent client can look out through the mirror, but no one can look in, and you’ll only be able to connect with other torrent clients that have a clear window - because your client can see them through the glass and send them a request to connect, and their connection is transparent so they can accept the message. So if there’s a lot of other people out there with one-way mirrors also, you can’t connect to them b/c you can’t see them and vice versa.

Port forwarding is basically setting your client up with a clear window instead of a mirror - it’ll be able to accept both incoming requests and make outgoing requests, increasing the number of other people you can connect to. Increased connections means more likely to find people on torrents with small amounts of seeders, and I think increased download speeds too.

I run a fairly comprehensive suite of *Arr apps off a Synology DS923+ and it was somewhat straightforward to set up. Note that there’s some setting with the 923 that doesn’t make it optimal for Plex and people prefer the 920 - I run Plex off an Nvidia Shield so that didn’t matter to me.

I wrote up a step-by-step installation guide for myself, mostly for reference / any future times I might need to make changes. tossed the PDF here in case you’d like to reference, though it’s a little out of date atm because I need to switch from Mullvad to ProtonVPN for port forwarding (which you can ignore if you don’t care about port forwarding): https://mega.nz/file/9pISRSqB#w_I-6gI8Ga2u_rvTGqTezmIk_-fxnmHfAr1FapFNpEM

Most of the guide was built using these two folks’ articles as reference:

• TRaSH Guides
• Dr_Frankenstein’s Synology Docker Tutorials