tyler

If you’re in the U.S. you can use Privacy.com. No need to ever give name, address, or real credit card info ever again. It’s pretty nice.

Let me know if you have any trouble!

Tailscale is incredibly easy. Install, start, sign in on both devices. Boom. Jellyfin from anywhere

Spoil it for us, what’s so eye opening?

absolutely do not do that. I can almost guarantee that any sort of AI will try to open a port that shouldn’t be open or in general expose you to a massive security vulnerability.

Ah ok this is the comment that needs to be in the main post. First things first:

You aren’t ‘installing’ radarr, sonarr, etc into any directories. They are containers, essentially entire operating systems located in a hidden folder on your server. You don’t ever touch these things directly, you only use docker commands to interface with them. There’s two ways to do that. Either directly running docker (docker run linuxserver:radarr -p blah blah blah) or with a docker compose (docker compose up). The docker compose way is the ‘easy’ way to do it (actually the easiest is just using unraid and clicking install, but we’ll ignore that since so many people are telling you a billion ways to do things). Docker compose means you can specify all of your applications in a single file, and how they interact with each other. You will run one command to start all of them at once. And then they will read from whatever folders you configure in the service. This might be a bit confusing because up above you might see other people’s docker compose files and they specify things like this:

  sonarr:
    container_name: sonarr
    network_mode: "service:gluetun"
    image: ghcr.io/hotio/sonarr:latest
    volumes:
      - /mnt/drive/volumes/sonarr/config:/config
      - /mnt/nas/TV:/mnt/TV
      - /mnt/nas/Downloads:/downloads
      - /etc/localtime:/etc/localtime:ro
    depends_on:
      - gluetun
    restart: 'unless-stopped'

and you would think that they’re configuring the sonarr locations for their tv and downloads, etc. But that is not what is happening. They are simply mapping a local path /mnt/nas/TV to a path inside of the sonarr operating system /mnt/TV. This means that in Sonarr, in the web interface, you would configure the path /mnt/TV, NOT the path /mnt/nas/TV. You still have to configure EVERYTHING in the services themselves. All that docker is doing is setting up the operating system. Think of it like this, on a regular computer you can map network drives to letters like A, B, C, etc right? Well that’s exactly what you’re doing in docker, mapping ‘network’ (actually your main operating system) folders, to folders in the remote operating system (the one running in docker).

In regards to having radarr rename things, you can have it do that, but you have to get the directory structure set up first, and you can run scripts to have nzbget or sabnzbd move things around for you. The experts on discord would be a much better help than most of us here I think, since they are all the devs on the project.

You shouldn’t be manually moving anything, though sometimes it is necessary. But when you’re first getting started I really just recommend following the TRaSH guides and then redownloading a few things to make sure it works properly. It explains a lot and it’s exactly what the people on the discord will tell you to do for all of this before going any further.

I’m very confused what it was that they moved into individual folders. And also configuring the naming of movies and shows is done in radarr and sonarr, not in docker compose.

I highly recommend Trash Guides for configuring these services. trash-guides.info

Sue over what?

When was the last time you replaced your nozzle? Could be a clogged nozzle. Your first layer is quite bad. There’s a lot that could be going wrong. Have you followed Elliot’s tuning guide?

lol yeah. I agree with that too.

No… because more people would be working on it.

They are not marked as resolved.

That only works if the plugins are somehow accessible through an api controller, which as far as I’m aware, is not how jellyfin plugins work. So no, it wouldn’t increase your attack surface at all.

Aside from most of those being “potential issues”, which weren’t proven, the rest are GETs of things that do not need to be secret, things like album art and list of installed plugins. Besides the one plugin issue, which was an actual security issue, which was fixed over a year and a half ago. github.com/jellyfin/jellyfin/pull/11436

Contrast that with Plex which has numerous high severity CVEs that include things like remote code execution, directory traversal, and more.

Please do explain or link sources to what you think are “security holes”.