usenet was used before the world wide web really took on. Nowadays it's mainly used to host & download movies, shows, games, etc. etc. It's basically like one of those direct download hosts where you simply download a file. So unlike torrent it is NOT peer to peer and you don't have to hope someone still seeds it.

But unlike direct downloaders the whole system is split into two parts. You have your "Usenet Providers" which are the host servers where all the files are stored. You cannot interact with those files directly however. They are all encrypted and fragmented and completely randomly named. What you need to actually download those files are Indexers. Those are sites like Drunkenslug, nzbgeek, etc. They will provide you with tiny little "textfiles" that contain a list of decryption keys and a list of filenames corresponding on the host server.

You then put those "textfiles" into a usenet download program, here i used SABnzbd, and it will take this list + keys, go to the usenet provider and starts to download those random files. After that it will unpack them, put them all together and ét voilá you have your fully assembled media file.

Most usenet providers are incredibly fast and can match your gigabit internet if you have it. The one i use for example goes up to 950Mbit/s. That combined with the fact that the files are either there or not, but nothing in between like it could be on torrent is a really really reliable and fast way to download stuff.

I'd make a little test run if i were you.

Add something via Jellyseer, take a note on what exact release it grabbed and stop the download and remove the whole job. Then add it via *arr again but don't do a interactive search. Let it do it's thing and take a note what exact release it grabs. If it takes the same release it did when using jellyseer, then you know somethings not good with your *arr profile here. Because jellyseer basically just prompts *arr to automatically search for something.

Interactive search is a manual process. If *arr's automatical search result is bad, there are ways to finetune it. Though i don't use *arr with torrents so i don't know exactly where / how.

Sounds like it, because jellyseer itself does NOT search for anything. All it does is tell sonarr/radarr that something was added and they should start the search.

However you also have to select your sonarr/radarr profile inside Jellyseer. So if you maybe have an old profile that is set to default on jellyseer it might be it.

Just a random guy on the internet ;)

I have tried it like that before writing the guide and it didn't cause issues. But yes, if it does one could simply mount the whole base folder and navigate from there

1. Thank you :)
2. I like to keep them seperate. Makes it easier to troubleshoot if some path goes haywire or what not. Also makes it easier to update one without stopping the other
3. Yeah i will go through them and remove the version

You're welcome!

After we learned that disney can kill your husband / wife and you're not even allowed to take them to court because you signed up for a disney+ trial years ago, i am more than happy for every single person that is able to rip as much of their (most of the time) shitty content

Glad you find it well-written :)

Well it isn't really that hard techznically, but you have to be really sure it actually works and that's the hard part.

You can look into "Gluetun". It is a small docker service that supports PIA. You will have to put this and the rest of the ARR stack into the same "docker network" and configure it so that radarr, etc. go through Gluetun and use it's VPN.

You can then open a terminal for the radarr container for example and run curl ipinfo.io for example to check the IP adress that container has to the outside world.

I didn't do that whole gluetun setup in quite a while so i'm not really in the position to give a proper guide on how to route your docker containers through it. But there are guides out there that will definetely help.

Testing that it's failproof would be for example run while sleep 5; do clear && curl ipinfo.io; done which shows your outside world IP for that container once per 5 seconds. Then stopping that gluetun container and look if the radarr container stops the ping and / or suddenly shows your real IP.

EDIT: found a quick readme for the gluetun container that shows how to route other containers through it

The are stack itself is so low power that you absolutely can run it on a NAS like synology for example... I mean you can run a Plex server on a NAS and it actually works so...

In my case I have it seperated. I have a NAS that does absolutely nothing else besides being a NAS. I then have my mediaserver for the are stack and jellyfin.

So that could be your Pi, and the you get an old used Synology for example.

You're right, but introducing .env files would be an extra step for each and every docker process here.

This was meant as an absolutely fundamental basic setup. If you know your way around docker you also know what to improve from those guides.

Everyone who does not know this, can get the services up and running without extra steps.

It's a fork of it specifically for jellyfin instead of Plex, so yes 👍

Nice heads up