Automating Your Media Server with Unraid

Why automate your media server?

A modern Unraid media server can do far more than just store files. With the right stack of Docker containers, you can automate the entire lifecycle of your media:

• Requests: Users ask for movies or shows through a friendly web UI.
• Acquisition: Indexers and download clients grab the content automatically.
• Organization: Media managers rename, sort, and move files into your library.
• Streaming: Plex, Jellyfin, or Emby serve it to any device.

The goal of this article is to show you how to wire these pieces together on Unraid so that your server quietly takes care of everything in the background.

Prerequisites on Unraid

Before you start building an automated stack, make sure your Unraid server has a few basics in place:

• Docker enabled: Go to Settings > Docker and ensure the Docker service is turned on.
• Appdata share: A cache‑preferred share (often called appdata) for container configs.
• Media shares: For example, /mnt/user/Media/Movies and /mnt/user/Media/TV.
• Community Apps plugin: This is the easiest way to find and install containers.

The core automation stack

There are many ways to build a media stack, but a popular, battle‑tested combination looks like this:

• Media server: Plex, Jellyfin, or Emby
• Request front‑end: Overseerr or Jellyseerr
• TV automation: Sonarr
• Movie automation: Radarr
• Download client: qBittorrent, Deluge, or NZBGet/SABnzbd
• Optional extras: Prowlarr for indexer management, Bazarr for subtitles

Unraid’s Docker support makes it easy to run each of these as a container, all sharing the same media directories and talking to each other over your LAN.

Designing your folder structure and Docker mappings

Consistent paths are the backbone of a stable media stack. If Plex, Sonarr, Radarr, and your download client all see your files at the same paths, everything “just works.”

Example Unraid shares

• Media share: /mnt/user/Media/Movies, /mnt/user/Media/TV
• Downloads share: /mnt/user/Downloads/Incomplete, /mnt/user/Downloads/Complete

Example container mappings

For each container, you might use something like:

• Media: Host /mnt/user/Media → Container /media
• Downloads: Host /mnt/user/Downloads → Container /downloads

Then, in Sonarr/Radarr, you point your root folders to /media/TV and /media/Movies, and your download client to /downloads. Every container speaks the same “path language.”

Setting up your media server (Plex/Jellyfin/Emby)

Start with the piece you and your users will interact with the most: the media server.

Key steps

1. Install the container: Use Community Apps to search for Plex, Jellyfin, or Emby.
2. Map volumes: Point your media paths to /media and config to /mnt/user/appdata/<app>.
3. Create libraries: Add libraries for Movies and TV, pointing to /media/Movies and /media/TV.
4. Enable remote access (optional): Configure port forwarding or a reverse proxy for secure external access.

Once your media server is up, you can verify that it correctly scans and plays any existing files before layering automation on top.

Automating TV and movies with Sonarr and Radarr

Sonarr and Radarr are the brains of your automation. They monitor your wanted list, talk to indexers and download clients, and move finished files into your library.

Basic configuration flow

1. Install Sonarr and Radarr: Grab them from Community Apps as Docker containers.
2. Set root folders: In each app, configure:
   • Sonarr → /media/TV
   • Radarr → /media/Movies
3. Connect download client: Add qBittorrent/Deluge/NZB client under Download Clients, using the container’s internal address and port.
4. Configure indexers: Add your torrent or Usenet indexers (or use Prowlarr to centralize them).
5. Set quality profiles: Define what “good enough” looks like (e.g., 1080p WEB‑DL, HEVC, etc.).

How the automation loop works

1. You add a show or movie to Sonarr/Radarr.
2. They search indexers for matching releases.
3. The download client grabs the file into /downloads.
4. On completion, Sonarr/Radarr import, rename, and move it to /media.
5. Your media server scans and makes it available to stream.

Adding a request system with Overseerr or Jellyseerr

If you share your server with friends or family, a request front‑end keeps your inbox clean and your library aligned with what people actually want to watch.

Core features

• Search TMDB/TVDB: Users can search for titles directly.
• Approval workflows: You can auto‑approve or manually approve requests.
• Integration: Overseerr/Jellyseerr talk directly to Sonarr, Radarr, and Plex/Jellyfin.

Setup outline

1. Install Overseerr/Jellyseerr via Community Apps.
2. Connect your media server (Plex/Jellyfin) so it can see what you already have.
3. Connect Sonarr and Radarr using their API keys and internal URLs.
4. Configure user access and notifications (Discord, email, etc.).

From that point on, a typical flow is: user requests a title → Overseerr sends it to Sonarr/Radarr → download client grabs it → media server serves it.

Dialing in your download client

Your download client is the workhorse of the stack. A few small tweaks can make it more reliable and automation‑friendly.

Best‑practice settings

• Use categories/tags: Configure separate categories for tv and movies so Sonarr/Radarr can match them.
• Set the completed folder: Point completed downloads to /downloads/Complete.
• Limit active downloads: Avoid saturating your disk or network; a few concurrent jobs are usually enough.
• Enable proper seeding rules (for torrents): Respect ratio/time requirements while avoiding endless seeding.

Nice‑to‑have extras

Once the core loop is stable, you can add some polish and resilience.

Prowlarr for indexer management

Prowlarr acts as a central hub for indexers and syncs them to Sonarr/Radarr. Instead of configuring each indexer multiple times, you manage them in one place.

Bazarr for subtitles

Bazarr integrates with Sonarr/Radarr and automatically downloads subtitles in your preferred languages, keeping them in sync with your library.

Reverse proxy and HTTPS

Tools like SWAG or Nginx Proxy Manager on Unraid let you expose your services via subdomains with HTTPS, making remote access more secure and user‑friendly.

Keeping your automated stack healthy

Automation doesn’t mean “set and forget forever.” A little light maintenance goes a long way.

• Back up appdata: Use the CA Backup/Restore plugin to protect your container configs.
• Monitor disk health: Check SMART reports and Unraid notifications regularly.
• Update carefully: Update containers one at a time and verify things still work.
• Review failed downloads: Sonarr/Radarr logs will tell you why something didn’t grab or import.

Over time, you can refine quality profiles, indexers, and paths so that your Unraid media server feels less like a hobby project and more like a reliable home service.

Bringing it all together

An automated media server on Unraid is really just a set of well‑connected pieces: a media server, automation tools like Sonarr/Radarr, a download client, and a request front‑end. Once they share consistent paths and can talk to each other, the system becomes surprisingly hands‑off.

Start small—get your media server stable, then add Sonarr/Radarr, then a request app, and finally polish with extras like Prowlarr, Bazarr, and a reverse proxy. Each step makes your Unraid box feel a little more like your own personal streaming platform.