Organizr / Overseerr / Sonarr / Radarr / Bazarr / Readarr / Jackett / Deluge / NordVPN / Plex / TraktSync / Portainer / Traefik / Truenas
TV shows and movies download, sort, with the desired quality and subtitles, behind a VPN (optional), ready to watch, in a beautiful media player. All automated.
- HTPC Download Box
This is what I have set up at home to handle TV shows, movies and books automated download, sort and play.
Disclaimer: I'm not encouraging/supporting piracy, this is for information purpose only.
How does it work? I rely on several tools integrated together. They're all open-source, and deployed as Docker containers on my Truenas Scale node Linux server.
The common workflow is detailed in this first section to give you an idea of how things work.
Overseerr helps you find media you want to watch. With inline recommendations and suggestions. It presents you and your users with a request interface that is incredibly easy to understand and use. Users can select the exact seasons they want to watch. Advanced users can use the “Advanced Requests” options to change destination folders and quality profiles.
Using Sonarr Web UI, search for a TV show by name and mark it as monitored. You can specify a language and the required quality (1080p for instance). Sonarr will automatically take care of analyzing existing episodes and seasons of this TV show. It compares what you have on disk with the TV show release schedule, and triggers download for missing episodes. It also takes care of upgrading your existing episodes if a better quality matching your criterias is available out there.
Sonarr triggers download batches for entire seasons. But it also handle upcoming episodes and seasons on-the-fly. No human intervention is required for all the episodes to be released from now on.
When the download is over, Sonarr moves the file to the appropriate location (my-tv-shows/show-name/season-1/01-title.mp4), and renames the file if needed.
Radarr is the exact same thing, but for movies.
Sonarr and Radarr can both rely on two different ways to download files:
- Usenet (newsgroups) bin files. That's the historical and principal option, for several reasons: consistency and quality of the releases, download speed, indexers organization, etc. Often requires a paid subscription to newsgroup servers. (I don't use this personnaly)
- Torrents. That's the new player in town, for which support has improved a lot lately.
I'm using torrents only, which work really fine.
Files are searched automatically by Sonarr/Radarr through a list of indexers that you have to configure. Indexers are APIs that allow searching for particular releases organized by categories. Think browsing the Pirate Bay programmatically. This is a pretty common feature for newsgroups indexers that respect a common API (called Newznab).
However this common protocol does not really exist for torrent indexers. That's why we'll be using another tool called Jackett. You can consider it as a local proxy API for the most popular torrent indexers. It searches and parse information from heterogeneous websites.
The best release matching your criteria is selected by Sonarr/Radarr/Readarr (eg. non-blacklisted 1080p release with enough seeds). Then the download is passed on to another set of tools.
Sonarr and Radarr are plugged to a downloader for our system:
- Deluge handles torrent download. (Transmission is a good alternative)
It is a daemon coming with a nice Web UI, making them perfect candidate for being installed on a server. Sonarr & Radarr already have integration for it, meaning it relies on each service API to pass on downloads, request download status and handle finished downloads.
It is a standard and popular tool. I'm using it for their integration with Sonarr/Radarr but also as standalone downloader for everything else.
For security and anonymity reasons, I'm running Deluge behind a VPN connection. All incoming/outgoing traffic from deluge is encrypted and goes out to an external VPN server. Via the proxy configuration in the web UI. Other service stay on my local network. This is done through Docker networking stack (more to come on the next paragraphs).
Plex Media Server organize all your medias as libraries. You can set up one for TV shows and another one for movies. It automatically grabs metadata for each new release (description, actors, images, release date).
Plex keeps track of your position in the entire library: what episode of a given TV show season you've watched, what movie you've not watched yet, what episode was added to the library since last time. It also remembers where you stopped within a video file. Basically you can pause a movie in your bedroom, then resume playback from another device in your bathroom.
Plex comes with clients in a lot of different systems (Web UI, Linux, Windows, OSX, iOS, Android, Android TV, Chromecast, PS4, Smart TV, etc.) that allow you to display and watch all your shows/movies in a nice Netflix-like UI.
The server has transcoding abilities: it automatically transcodes video quality if needed (eg. stream your 1080p movie in 480p if watched from a mobile with low bandwidth).
I have a home made nas with decent specs, running Truenas scale. The containers are running on a Debian Linux VM on the server and the files are store via a mounted network share on the server itself. The softwares configurations are stored in the VM itself. SQLlite doesn't like to be in a network folder, give a lot of database locked errors.
I also had this running on a Raspberry PI 4 before wit ha different plex image because the official one didn't work.
Downloaders:
- Transmission: torrent downloader with a web UI
- Deluge: torrent downloader with a web UI
- Jackett: API to search torrents from multiple indexers
- Flaresolverr: Proxy server to bypass Cloudflare and DDoS-GUARD protection
- Bazarr: A companion tool for Radarr and Sonarr which will automatically pull subtitles for all of your TV and movie downloads
Download orchestration:
- Overseerr: request management and media discovery tool built to work with your existing Plex ecosystem, Radarr & Sonarr
- Sonarr: manage TV show, automatic downloads, sort & rename
- Radarr: basically the same as Sonarr, but for movies
- Lidarr (not currently in the stack): basically the same as Radarr, but for songs
- Readarr: basically the same as Lidarr, but for books
VPN:
Media Center:
- Plex: media center server with streaming transcoding features, useful plugins and a beautiful UI. Clients available for a lot of systems (Linux/OSX/Windows, Web, Android, Chromecast, Android TV, etc.)
- PlexTraktSync: free two-way-sync between trakt.tv and Plex Media Server
- Ofelia scheduler: modern and low footprint job scheduler for docker environments. Triggers
PlexTraktSync - Bazarr: manage TV show and movies subtitles
Other:
- Organizr: allows you to setup "Tabs" that will be loaded all in one webpage. You can then work on your server with ease
- Traefik: reverse proxy and load balancer that makes deploying microservices easy
- Portainer: manage docker containers with ease
- Watchtower: a container-based solution for automating Docker container base image updates
The idea is to set up all these components as Docker containers in a docker-compose.yml file.
We'll reuse community-maintained images (special thanks to linuxserver.io for many of them).
I'm assuming you have some basic knowledge of Linux and Docker.
A general-purpose docker-compose.yml file is maintained in this repo here.
The stack is not really plug-and-play. You'll see that manual human configuration is required for most of these tools. Configuration is not fully automated (yet?), but is persisted on reboot. Some steps also depend on external accounts that you need to set up yourself (torrent indexers, vpn server, plex account, etc.). We'll walk through it.
Optional step described below that you may wish to skip:
- Using a VPN server for Transmission and/or Deluge incoming/outgoing traffic.
See the official instructions to install Docker.
Then add yourself to the docker group:
sudo usermod -aG docker myuser
Make sure it works fine:
docker run hello-world
Also install docker-compose (see the official instructions).
For each of these images, there is some unique coniguration that needs to be done. Instead of editing the docker-compose file to hardcode these values in, we'll instead put these values in a .env file. A .env file is a file for storing environment variables that can later be accessed in a general-purpose docker-compose.yml file, like the example one in this repository.
Here is an example of what your .env file should look like, use values that fit for your own setup.
SQLlite use by sonarr and radarr doesn't like to be on a network folder so I separated the config folders env variable to keep them in the Pi.
Content of .env.example
# Your timezone, https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
TZ=Europe/Paris
# UNIX PUID and PGID, find with: id $USER
PUID=1000
PGID=1000
# Local network mask, find with: ip route | awk '!/ (docker0|br-)/ && /src/ {print $1}'
NETWORK=192.168.1.0/24
# Servername for outside redirection with traefik
SERVERNAME=test.com
# The directory where data will be stored.
ROOT=/exhdd/share
# The directory where configuration will be stored.
CONFIG=/config
[email protected]
#NordVPN informations
PRIVATE_KEY=xxxxxxxxxxxxxx
VPN_COUNTRY=FRThings to notice:
- TZ is based on your tz time zone.
- The PUID and PGID are your user's ids. Find them with
id $USER. - This file should be in the same directory as your
docker-compose.ymlfile so the values can be read in. - You local network mask to make Transmission and/or Deluge accessible in your local network, more infos
- Your NordVPN password/login and VPN server country
This is the instructions for Truenas and Synology but should be pretty much the same for any NAS.
Instructions Truenas Instructions Synology
mkdir /mnt/nas-share
Add in /etc/fstab where:
<ip.of.your.server>is the ip of your nas machine (the VM has a diferrent ip)<your-username>is the username to log into the server<Your-Password!@#$%>is the password of the user
//<ip.of.your.server>/smb /mnt/nas-share cifs username=<your-username>,password=<Your-Password!@#$%>,_netdev,uid=1000,gid=1000,iocharset=utf8 0 0
Re mount
sudo mount -a
We'll use deluge Docker image from linuxserver, which runs both the deluge daemon and web UI in a single container.
version: "3"
services:
deluge:
container_name: deluge
image: linuxserver/deluge:latest
restart: always
network_mode: service:vpn # run on the vpn network
environment:
- PUID=${PUID} # default user id, defined in .env
- PGID=${PGID} # default group id, defined in .env
- TZ=${TZ} # timezone, defined in .env
volumes:
- ${ROOT}/downloads:/downloads # downloads folder
- ${ROOT}/deluge:/config # config filesThings to notice:
- I use the host network to simplify configuration. Important ports are
8112(web UI) and58846(bittorrent daemon).
Then run the container with docker-compose up -d.
To follow container logs, run docker-compose logs -f deluge.
You should be able to login on the web UI (localhost:8112, replace localhost by your machine ip if needed).
The default password is deluge. You are asked to modify it, I chose to set an empty one since deluge won't be accessible from outside my local network.
The running deluge daemon should be automatically detected and appear as online, you can connect to it.
You may want to change the download directory. I like to have to distinct directories for incomplete (ongoing) downloads, and complete (finished) ones. Also, I set up a blackhole directory: every torrent file in there will be downloaded automatically. This is useful for Jackett manual searches.
You should activate autoadd in the plugins section: it adds supports for .magnet files.
You can also tweak queue settings, defaults are fairly small. Also you can decide to stop seeding after a certain ratio is reached. That will be useful for Sonarr, since Sonarr can only remove finished downloads from deluge when the torrent has stopped seeding. Setting a very low ratio is not very fair though !
Configuration gets stored automatically in your mounted volume (${ROOT}/deluge) to be re-used at container restart. Important files in there:
authcontains your login/passwordcore.confcontains your deluge configuration
You can use the Web UI manually to download any torrent from a .torrent file or magnet hash.
You can also use the web UI to set the proxy in the parameters to your VPN.
The goal here is to have an OpenVPN Client container running and always connected. We'll make Deluge incoming and outgoing traffic go through this OpenVPN container.
This must come up with some safety features:
- VPN connection should be restarted if not responsive
- Traffic should be allowed through the VPN tunnel only, no leaky outgoing connection if the VPN is down
- Deluge Web UI should still be reachable from the local network
Lucky me, someone already set that up quite nicely.
Point 1 is resolved through the OpenVPN configuration (ping-restart set to 120 sec by default).
Point 2 is resolved through iptables rules
Point 3 is also resolved through iptables rules
Configuration is explained on the project page, you can follow it. However it is not that easy depending on your VPN server settings. I'm using a privateinternetaccess.com VPN, so here is how I set it up.
Put it in the docker-compose file, and make transmissionand/or Deluge use the vpn container network:
vpn:
image: bubuntux/nordlynx:latest
container_name: vpn
restart: unless-stopped
cap_add: # required to modify network interfaces
- NET_ADMIN
- NET_RAW
devices:
- /dev/net/tun
environment:
- PRIVATE_KEY=${PRIVATE_KEY}
- NET_LOCAL=${NETWORK}
- TZ=${TZ} # timezone, defined in .env
sysctls:
- net.ipv6.conf.all.disable_ipv6=1
expose:
- "8112"
deluge:
container_name: deluge
image: linuxserver/deluge:latest
restart: unless-stopped
network_mode: service:vpn # run on the vpn network
environment:
- PUID=${PUID} # default user id, defined in .env
- PGID=${PGID} # default group id, defined in .env
- TZ=${TZ} # timezone, defined in .env
volumes:
- ${ROOT}/downloads:/downloads # downloads folder
- ${CONFIG}/deluge:/config # config filesNotice how transmission and/or Deluge is now using the vpn container network, with Transmission and/or Deluge web UI port exposed on the vpn container for local network access.
You can check that Transmission and/or Deluge is properly going out through the VPN IP by using torguard check. Get the torrent magnet link there, put it in Transmission and/or Deluge, wait a bit, then you should see your outgoing torrent IP on the website.
Jackett translates request from Sonarr and Radarr to searches for torrents on popular torrent websites, even though those website do not have a sandard common APIs (to be clear: it parses html for many of them :)).
No surprise: let's use linuxserver.io container !
jackett:
container_name: jackett
image: linuxserver/jackett:latest
restart: unless-stopped
network_mode: host
environment:
- PUID=${PUID} # default user id, defined in .env
- PGID=${PGID} # default group id, defined in .env
- TZ=${TZ} # timezone, defined in .env
volumes:
- /etc/localtime:/etc/localtime:ro
- ${ROOT}/downloads/torrent-blackhole:/downloads # place where to put .torrent files for manual download
- ${CONFIG}/jackett:/config # config filesNothing particular in this configuration, it's pretty similar to other linuxserver.io images.
An interesting setting is the torrent blackhole directory. When you do manual searches, Jackett will put .torrent files there, to be grabbed by your torrent client directly (Deluge for instance).
As usual, run with docker-compose up -d.
Jackett web UI is available on port 9117.
Configuration is available at the bottom of the page. I chose to disable auto-update (I'll rely on the docker images tags myself), and to set /downloads as my blackhole directory.
Click on Add Indexer and add any torrent indexer that you like. I added 1337x, cpasbien, RARBG, The Pirate Bay and YGGTorrent (need a user/password).
You can now perform a manual search across multiple torrent indexers in a clean interface with no trillion ads pop-up everywhere. Then choose to save the .torrent file to the configured blackhole directory, ready to be picked up by Deluge automatically !
Luckily for us, Plex team already provides a maintained Docker image for pms.
We'll use the host network directly, and run our container with the following configuration:
plex-server:
container_name: plex-server
image: plexinc/pms-docker:latest
restart: unless-stopped
environment:
- TZ=${TZ} # timezone, defined in .env
network_mode: host
volumes:
- ${CONFIG}/plex/db:/config # plex database
- ${CONFIG}/plex/transcode:/transcode # temp transcoded files
- ${ROOT}/complete:/data # media libraryLet's run it !
docker-compose up -d
Plex Web UI should be available at localhost:32400/web (replace localhost by your server ip if needed).
Note: If you are running on a headless server (e.g. Synology NAS) with container using host networking, you will need to use ssh tunneling to gain access and setup the server for first run. (see https://forums.plex.tv/t/i-did-something-stupid-please-plex-forums-your-my-only-hope/328481/11)
You'll have to login first (registration is free), then Plex will ask you to add your libraries. I have two libraries:
- Movies
- TV shows
Make these the library paths:
- Movies:
/data/movies - TV:
/data/tv
As you'll see later, these library directories will each have files automatically placed into them with Radarr (movies) and Sonarr (tv), respectively.
Now, Plex will then scan your files and gather extra content; it may take some time according to how large your directory is.
A few things I like to configure in the settings:
- Set time format to 24 hours (never understood why some people like 12 hours)
- Tick "Update my library automatically"
You can already watch your stuff through the Web UI. Note that it's also available from an authentified public URL proxified by Plex servers (see Settings/Server/Remote Access), you may note the URL or choose to disable public forwarding.
Plex clients are available for most devices. I use it on my Android phone, my wife uses it on her iPhone, we use it on a Chromecast in the bedroom, and we also use Plex Media Center directly on the same computer where the server is running, close to the living room TV. It also works fine on the PS4 and on my Raspberry Pi. Nothing particular to configure, just download the app, log into it, enter the validation code and there you go.
On a Linux Desktop, there are several alternatives. Historically, Plex Home Theater, based on XBMC/Kodi was the principal media player, and by far the client with the most features. It's quite comparable to XBMC/Kodi, but fully integrates with Plex ecosystem. Meaning it remembers what you're currently watching so that you can pause your movie in the bedroom while you continue watching it in the toilets \o/. Recently, Plex team decided to move towards a completely rewritten player called Plex Media Player. It's not officially available for Linux yet, but can be built from sources. A user on the forums made an AppImage for it. Just download and run, it's plug and play. It has a very shiny UI, but lacks some features of PHT. For example: editing subtitles offset.
If it does not suit you, there is also now an official Kodi add-on for Plex. Download Kodi, then browse add-ons to find Plex.
Also the old good Plex Home Theater is still available, in an open source version called OpenPHT.
Personal choice: after using OpenPHT for a while I'll give Plex Media Player a try. I might miss the ability to live-edit subtitle offset, but Bazarr is supposed to do its job. We'll see.
Guess who made a nice Sonarr Docker image? Linuxserver.io !
Let's go:
sonarr:
container_name: sonarr
image: linuxserver/sonarr:latest
restart: unless-stopped
network_mode: host
environment:
- PUID=${PUID} # default user id, defined in .env
- PGID=${PGID} # default group id, defined in .env
- TZ=${TZ} # timezone, defined in .env
volumes:
- /etc/localtime:/etc/localtime:ro
- ${CONFIG}/sonarr:/config # config files
- ${ROOT}/complete/tv:/tv # tv shows folder
- ${ROOT}/downloads:/downloads # download folderdocker-compose up -d
Sonarr web UI listens on port 8989 by default. You need to mount your tv shows directory (the one where everything will be nicely sorted and named). And your download folder, because sonarr will look over there for completed downloads, then move them to the appropriate directory.
Sonarr should be available on localhost:8989. Go straight to the Settings tab.
Enable Ignore Deleted Episodes: if like me you delete files once you have watched them, this makes sure the episodes won't be re-downloaded again.
In Media Management, you can choose to rename episodes automatically. This is a very nice feature I've been using for a long time.
In profiles you can set new quality profiles, default ones are fairly good. There is an important option at the bottom of the page: do you want to give priority to Usenet or Torrents for downloading episodes? I'm keeping the default Usenet first.
Indexers is the important tab: that's where Sonarr will grab information about released episodes. Nowadays a lot of Usenet indexers are relying on Newznab protocol: fill-in the URL and API key you are using. You can find some indexers on this subreddit wiki. It's nice to use several ones since there are quite volatile. You can find suggestions on Sonarr Newznab presets. Some of these indexers provide free accounts with a limited number of API calls, you'll have to pay to get more. Usenet-crawler is one of the best free indexers out there.
For torrents indexers, I activate Torznab custom indexers that point to my local Jackett service. This allows searches across all torrent indexers configured in Jackett. You have to configure them one by one though.
Get torrent indexers Jackett proxy URLs by clicking Copy Torznab Feed in Jackett Web UI. Use the global Jackett API key as authentication.
Download Clients tab is where we'll configure links with our two download clients: NZBGet and Deluge.
There are existing presets for these 2 that we'll fill with the proper configuration.
NZBGet configuration:
Deluge configuration:
Enable Advanced Settings, and tick Remove in the Completed Download Handling section. This tells Sonarr to remove torrents from deluge once processed.
In Connect tab, we'll configure Sonarr to send notifications to Plex when a new episode is ready:
Let's add a series !
Note: You may need to chown -R $USER:$USER /path/to/root/directory so Sonarr and the rest of the apps have the proper permissions to modify and move around files. This Docker image of Sonarr uses an internal user account inside the container called abc some you may have to set this user as owner of the directory where it will place the media files after download. This note also applies for Radarr.
Enter the series name, then you can choose a few things:
- Monitor: what episodes do you want to mark as monitored? All future episodes, all episodes from all seasons, only latest seasons, nothing? Monitored episodes are the episodes Sonarr will download automatically.
- Profile: quality profile of the episodes you want (HD-1080p is the most popular I guess).
You can then either add the serie to the library (monitored episode research will start asynchronously), or add and force the search.
Wait a few seconds, then you should see that Sonarr started doing its job. Here it grabed files from my Usenet indexers and sent the download to NZBGet automatically.
You can also do a manual search for each episode, or trigger an automatic search.
When download is over, you can head over to Plex and see that the episode appeared correctly, with all metadata and subtitles grabbed automatically. Applause !
Radarr is a fork of Sonarr, made for movies instead of TV shows. For a good while I've used CouchPotato for that exact purpose, but have not been really happy with the results. Radarr intends to be as good as Sonarr !
Radarr is very similar to Sonarr. You won't be surprised by this configuration.
radarr:
container_name: radarr
image: linuxserver/radarr:latest
restart: unless-stopped
network_mode: host
environment:
- PUID=${PUID} # default user id, defined in .env
- PGID=${PGID} # default group id, defined in .env
- TZ=${TZ} # timezone, defined in .env
volumes:
- /etc/localtime:/etc/localtime:ro
- ${CONFIG}/radarr:/config # config files
- ${ROOT}/complete/movies:/movies # movies folder
- ${ROOT}/downloads:/downloads # download folderRadarr Web UI is available on port 7878.
Let's go straight to the Settings section.
In Media Management, you can choose whether or not to enable automatic renaming. Previously I used the sub-zero plugin to find subtitles which functioned better with the original filenames. But now with Bazarr, it's hooked directly into Radarr and Sonarr which means it will look at the original filenames anyway. I enable Ignore Deleted Movies to make sure movies that I delete won't be downloaded again by Radarr. I disable Use Hardlinks instead of Copy because I prefer to avoid messing around what's in my download area and what's in my movies area.
In Profiles you can set new quality profiles, default ones are fairly good. There is an important option at the bottom of the page: do you want to give priority to Usenet or Torrents for downloading episodes? I'm keeping the default Usenet first.
As for Sonarr, the Indexers section is where you'll configure your torrent and nzb sources.
Nowadays a lot of Usenet indexers are relying on Newznab protocol: fill-in the URL and API key you are using. You can find some indexers on this subreddit wiki. It's nice to use several ones since there are quite volatile. You can find suggestions on Radarr Newznab presets. Some of these indexers provide free accounts with a limited number of API calls, you'll have to pay to get more. Usenet-crawler is one of the best free indexers out there. For torrents indexers, I activate Torznab custom indexers that point to my local Jackett service. This allows searches across all torrent indexers configured in Jackett. You have to configure them one by one though.
Get torrent indexers Jackett proxy URLs by clicking Copy Torznab Feed. Use the global Jackett API key as authentication.
Download Clients tab is where we'll configure links with our two download clients: NZBGet and Deluge.
There are existing presets for these 2 that we'll fill with the proper configuration.
NZBGet configuration:
Deluge configuration:
Enable Advanced Settings, and tick Remove in the Completed Download Handling section. This tells Radarr to remove torrents from deluge once processed.
In Connect tab, we'll configure Radarr to send notifications to Plex when a new episode is ready:
Let's add a movie !
Enter the movie name, choose the quality you want, and there you go.
You can then either add the movie to the library (monitored movie research will start asynchronously), or add and force the search.
Wait a few seconds, then you should see that Radarr started doing its job. Here it grabed files from my Usenet indexers and sent the download to NZBGet automatically.
You can also do a manual search for each movie, or trigger an automatic search.
When download is over, you can head over to Plex and see that the movie appeared correctly, with all metadata and subtitles grabbed automatically. Applause !
I like the discovering feature. When clicking on Add Movies you can select Discover New Movies, then browse through a list of TheMovieDB recommended or popular movies.
On the rightmost tab, you'll also see that you can setup Lists of movies. What if you could have in there a list of the 250 greatest movies of all time and just one-click download the ones you want?
This can be set up in Settings/Lists. I activated the following lists:
- StevenLu: that's an interesting project that tries to determine by certain heuristics the current popular movies.
- IMDB TOP 250 movies of all times from Radarr Lists presets
- Trakt Lists Trending and Popular movies
I disabled automatic sync for these lists: I want them to show when I add a new movie, but I don't want every item of these lists to be automatically synced with my movie library.
In previous versions of this guide, I used the sub-zero plugin for plex. Based on someone's suggestion on this project I tried out Bazarr which hooks directly into Radarr and Sonarr and makes the process more effective and painless. If you don't care about subtitles go ahead and skip this step.
Believe it or not, we will be using yet another docker container from linuxserver! Since this is made to be a companion app for Sonarr and Radarr, you will notice that the configuration is very similar to them, just point it at the directories where you store your organized movies and tv shows.
bazarr:
container_name: bazarr
image: linuxserver/bazarr
restart: unless-stopped
network_mode: host
environment:
- PUID=${PUID} # default user id, defined in .env
- PGID=${PGID} # default group id, defined in .env
- TZ=${TV} # timezone, defined in .env
- UMASK_SET=022 #optional
volumes:
- ${CONFIG}/bazarr:/config # config files
- ${ROOT}/complete/movies:/movies # movies folder
- ${ROOT}/complete/tv:/tv # tv shows folder
ports:
- 6767:6767The Web UI for Bazarr will be available on port 6767. Load it up and you will be greeted with this setup page:
You can leave this page blank and go straight to the next page, "Subtitles". There are many options for different subtitle providers to use, but in this guide I'll be using Open Subtitles. If you don't have an account with them, head on over to the Registration page and make a new account. Then all you need to do is tick the box for OpenSubtitles and fill in your new account details.
You can always add more subtitle providers if you want, figure out which ones are good for you!
Next scroll to the bottom of the screen where you will find your language settings. I am interested in French as well as English subtitles so I will add both of them for enabled languages. However I am primarily interested in French so I will turn on "Default Enabled" for both TV and movies and finally set French to be that default.
Click next and we will be on the Sonarr setup page. For this part we will need our Sonarr API key. To get this, open up sonarr in a separate tab and navigate to Settings > General > Security and copy the api key listed there.
Head back over Bazarr and check the "Use Sonarr" box and some settings will pop up. Paste your API key in the proper field, and you can leave the other options default. If you would like, you can tick the box for "Download Only Monitored" which will prevent Bazarr from downloading subtitles for tv shows you have in your Sonarr library but have possibly deleted from your drive. Then click "Test" and Sonarr should be all set!
The next step is connecting to Radarr and the process should be identical. The only difference is that you'll have to grab your Radarr API key instead of Sonarr. Once that's done click Finish and you will be brought to your main screen where you will be greeted with a message saying that you need to restart. Click this and Bazarr should reload. Once that's all set, you should be good to go! Bazarr should now automatically downlaod subtitles for the content you add through Radarr and Sonarr that is not already found within the media files themselves.
If you have any problems, check out the wiki page for Bazarr and you should probably find your answer.
docker stop $(docker ps -a -q)
docker rm $(docker ps -a -q)
docker rmi $(docker images -q)
docker logs --tail 50 --follow --timestamps deluge
docker exec -ti vpn bash
ncdu # excellent command-line disk usage analyser
df -h