Skip to content

Jellyseerr in Container Manager on a Synology NAS

Important or Recent Updates
Historic UpdatesDate
Guide updated for Container Manager21/05/2023
Moved from UI setup to Project Setup which is more flexible and easier to maintain.
Added an addition element to the compose to restrict the container from gaining additional privileges.
25/10/2023
Historic updates now at the end of the guide.


What is Jellyseerr

Jellyseerr (a fork of Overseerr) is a web front end for the users of your Jellyfin Server, it allows them to request new Movies and Shows which are then passed to Radarr and Sonarr for automated download.

Let’s Begin

In this guide I am going to take you through the steps to get Jellyseerr up and running in Docker on your Synology NAS.

In order for you to successfully use this guide please follow the two steps below first.

This guide contains two parts:

  • Part 1 — Setting up the container in Container Manager
  • Part 2 — Setting up DDNS, Reverse Proxy and SSL

Part 1 — Container Set up

Folder Setup

Let’s start by getting some folders set up for the containers to use. Open up File Station create the following.

Folders
/docker/projects/jellyseerr-compose
/docker/jellyseerr

Container Manager

Next we are going to set up a ‘Project’ in Container Manager. Open up Container Manager and click on Project then on the right-hand side click ‘Create’.

In the next screen we will set up our General Settings, enter the following:

SectionSetting
Project Name:jellyseerr
Path:/docker/projects/jellyseerr-compose
Source:Create docker-compose.yml

Next we are going to drop in our docker compose configuration copy all the code in the box below and paste it into line ‘1’ just like the screenshot.

What on earth is a Docker Compose?
Docker Compose allows us to define how Docker should set up one or more containers within a single configuration file. This file is yaml formatted and Container Manager uses the Projects feature to manage them.

YAML
services:
  jellyseerr:
    image: fallenbagel/jellyseerr:latest
    container_name: jellyseerr
    user: UID:GID #YOUR_UID_AND_GID
    environment:
      - TZ=Europe/London #CHANGE_TO_YOUR_TZ
    volumes:
      - /volume1/docker/jellyseerr:/app/config
    ports:
      - 5055:5055
    network_mode: synobridge
    security_opt:
      - no-new-privileges:true
    restart: always

Environment Variables

We need to make some changes in order for the container to have the correct permissions to save its configuration files and to have access to your media.

VariableValue
user: (required) The UID and GID you obtained in the user setup guide should be entered here
TZ(required) Your timezone wikipedia.org/wiki/List_of_tz_database_time_zones

Click ‘Next’

You do not need to enable anything on the ‘Web portal settings’ screen click ‘Next’ again.

On the final screen click ‘Done’ which will begin the download of the container image and once downloaded it will be launched!

The image will now be downloaded and extracted. You should see ‘Code 0’ when it has finished.

The Project should now be running with a Green status

Firewall Exceptions

(Skip if you don’t have the Firewall configured)

If you have enabled and configured the Synology Firewall you will need to create exceptions for any containers that have a Web UI or have any incoming or outgoing connections. This section covers the basics of how to add these. (Please note this is a generic section and will not show the specific ports in this guide however it applies in the same way)

Head into the Control Panel> Security > Firewall, from here click Edit Rules for the profile you set up when you enabled the Firewall.

Next click on Create and you will see the screen below. Source IP and Action will be automatically selected to All and Allow, I will leave it up to you as to your own preference on whether you want to lock down specific Source IPs from having access. In this example we will leave as All.

You will now choose ‘Select from a list of built-in applications‘ and then the Select button

Now from the list choose the newly created Docker container (You can do more than one if you wish)

Click OK a couple of times to get back to the main screen. You will see by default the new rule is added to the bottom of the list. You must always have your Block All rule last in the list as the rules are applied top down so move your container up.

You have now completed the Firewall changes and can continue with the guide.

Container set up completed

You should now be able to access the web interface via the IP of your NAS followed by the port 5055

e.g. 192.168.0.30:5055

Part 2 – DDNS, SSL and Reverse Proxy

Before we start, make sure you have registered for a Synology Account as we are going to be using their DDNS service. https://account.synology.com/en-uk/register/

In order to successfully use the reverse proxy you will also need to forward port 443 to you NAS IP. (You will need to check how to do this on your own router) This port is used for secure web traffic.

DDNS (Dynamic Domain Name System)

A DDNS address allows you to get external access to Jellyseerr via a subdomain provided by Synology, this is useful on home internet connections where your ISP will change your IP address on a regular basis.

Note: If you want to access DSM via this new address you will either need to create an additional Reverse Proxy for it or open port 5001 on your router.

In the DSM Control panel go to ‘External Access’ and then to the ‘DDNS’ tab

Click on ‘Add’, then fill out the following sections.

SectionValue
Service ProviderSynology
HostnameThis will be the address used to identify your NAS so make it personal to you not specific to this guide.
jellyseerr.synology.me = BAD
myawesomenas.synology,me =GOOD
Email:Log into your Synology account
External Address (IPv4)This should be filled in automatically
External Address (IPv6)This should be filled in automatically if your ISP is using IPv6
Get a Cert from Let’s EncryptTick this box
Enable HeartbeatTick this box

Now press OK, DSM will apply your settings. It can take a few moments to set up and the DSM interface will refresh. You will likely receive a certificate error which you will need to accept to get back into DSM.

You should now test that you can access your Diskstation via the hostname you requested and not receive any SSL errors.

Reverse Proxy

So you don’t have to open up additional ports on your router for Jellyseerr we are going to set up a reverse proxy subdomain. This means you and your users can access Jellyseerr without using a port number as it will route all traffic through the secure 443 port.

Go back into the Control Panel and access the ‘Login Portal’ then in the ‘Advanced’ tab click ‘Reverse Proxy’ and then click on ‘Create’.

We are now going to enter some rules, so when you or your users access the URL specified the request will automatically be sent to the Jellyseerr web UI. (Optionally you may want to use something more meaningful in the hostname section such as ‘movierequests’ instead of ‘jellyseerr’)

Use the settings below, you will need to amend the Hostname sections in line with the hostname you registered earlier, and the IP of your NAS.

SettingValue
Reverse Proxy Name:jellyseerr
Protocol:HTTPS
Hostname:jellyseerr.xxx.synology.me – change the part after ‘jellyseerr.’ to your own hostname you registered earlier.
Port:443
Protocol:HTTP
Hostname:Your NAS IP
Port:5055

On the second tab ‘Custom Header’ click on Create then WebSocket, this will add two entries which will force a https connection if you ever try to connect over http, you can now press save.

You should now be able to access the Jellyseerr initial setup by going to https://jellyseerr.xxx.synology.me (use the address you used in the reverse proxy) it will be a secure connection, and you should have no SSL errors.

As Jellyseerr has a really nice initial setup UI that takes you through the basics I won’t be covering this.

You are ready to roll 🙂


Buy Me a Coffee or Throw me some Sats

If you have found my site useful please consider pinging me a tip as it helps cover the cost of running things or just lets me get the odd beverage. Plus 10% goes to the devs of the apps I do guides for every year.

Published inDockerSearch / Indexers 7.2Synology

4 Comments

    • Dr_Frankenstein Dr_Frankenstein

      You will need to find what app you have installed using the port, do you have WebStation running? You will need 443 to use the internal Reverse Proxy.

  1. Scoop Scoop

    How do we test the Diskstation via the new DDNS hostname? Is it just putting hostname into a web-browser and getting access to DSM?

    • Dr_Frankenstein Dr_Frankenstein

      Hey

      If you want to connect to DSM it won’t be available unless you either open up port 5001. Or setup another reverse proxy address using the top level domain you registered such as scoop.synology.me and point that at port 5000/5001. You could do dsm.scoop.synology.me again pointing that to 5000/5001 in the reverse proxy screen.

      If that doesn’t make sense ping me an email via the Help Me! page.

      Thanks

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

drfrankenstein.co.uk – writing Synology Docker Guides since 2016 – Join My Discord!