I don't personally use it but you should be able to use the gluetun docker container to connect to the VPN and then force the torrenting container to download over the network provided by gluetun
fiddlesticks
joined 2 years ago
Because of the rapid fire content, I guess?
Honestly same, I just know that the speeds were better when the port forwarding worked.
I think it just makes the service visible to devices from outside the network which helps them form a more direct connection. (That's just an educated guess though)
I can confirm that seeding with mullvad is painfully slow, if you do torrent locally get a VPN with port forwarding.
Who do i call when it stays hard for more than 4 hours?
I have no clue.
Using the *arrs is pretty convenient if you know how to use docker (or even if you dont) and then you can connect them to Plex or jellyfin to view, it won't be instant like Netflix and co but at least its free/cheaper (cost of VPN or seedbox). You can even setup overseerr or jellyseerr to simplify the movie/show requests.
Radar can track whole movie collections if that's what you mean, alternatively there is a list function which might do what you need(I've never really used it though so idk)
Funny same thing on jerboa
Yeah sure, here's my setup including my transmission client. I essentially just give the docker containers access to the whole Torrent directory, instead of having one mount for the downloads and one for the media library. You also need to make sure that the arrs are set to hardlink which should be the default
The hard linking only works of the source and destination are in the same mount, for example
/data/downloads:/downloads /data/media:/media
Will create copies and use double the storage on just hard linking, to make it hardlink you need to put the downloads and destination folders in the same directory so make the docker mount look like
/data:/data
instead. Then you just need to tell your torrent client to put the downloaded files into /data/downloads/(either sonarr or radarr) and the the arrs can look into their folders and then hardlink the files into /data/media/whatever
I have no clue if any of this is understandable, but I can post my docker compose once I get to my pc
Check your ffmpeg logs that should help find the cause