How to self-host a Jellyseerr server

Friends request movies/shows for your Jellyfin/Emby; automation fetches them. Cresdock runs it on a server you own, from a catalogue, with no Docker and no reverse proxy to configure.

What Cresdock does for you with Jellyseerr

Its configuration is written before the container ever starts, so Jellyseerr comes up already set up rather than showing you a blank first-run form.
Given its own web address, with its own login seeded in advance. Jellyseerr can't live under a shared path, and apps like this are reached by clients that don't carry a browser session — so it gets a real password rather than being left open.
Jellyseerr signs people in with their Jellyfin, Emby or Plex account, so its opening setup is one only you can start — it needs your own sign-in with that server.
Once you're in, its wizard asks where Sonarr and Radarr are, and your panel shows the details to copy on their tiles — so that step is copy-and-paste rather than a hunt.

Why run Jellyseerr yourself

Streaming services remove things. A film you paid to watch last year can simply stop being there, and nothing tells you in advance. Running your own means the library is whatever you put in it, and it stays.

What kind of server Jellyseerr needs

A media server is the one category where the hardware matters. Direct play — where the app hands the file straight to your TV or phone — costs almost nothing, and 2 GB of memory is plenty. Converting on the fly for a device that can't play the original is what gets expensive; if you expect that often, a machine with hardware video support pays for itself immediately.

Cresdock itself is undemanding — it runs on a small rented server, an old desktop or a mini PC, on Ubuntu or Debian. Everything it installs shares that machine, so the honest question is not "will this app run" but "how much am I going to put on here in total".

Where to run Jellyseerr

Jellyseerr runs wherever Cresdock runs, and the choice is about the machine, not the app:

At home, on hardware you already own. A mini PC, an old desktop or a NAS that can run Debian. Cresdock works behind a home router with no port forwarding and no domain, so Jellyseerr is reachable on your own network first and from outside only if you choose.
On a rented server. A small VPS is enough for most apps and is the usual answer when Jellyseerr should be reachable from anywhere. The setup guide covers the specs and the one-command install.
Through a provider that runs Cresdock. Hosting companies deploy Cresdock workspaces for their customers, so Jellyseerr can come with a server you rent rather than one you set up — ask your provider, or see how providers offer it.

Installing Jellyseerr

Put Cresdock on a server
One line on any Ubuntu or Debian machine — a rented VPS, a spare PC, a home server. It sets itself up.
Pick Jellyseerr from the catalogue
Click Install. The panel pulls the image, writes the configuration, gets a certificate and starts it.
Open it from your dashboard
Its address and any login details are on its card. Start, stop, update, roll back or remove it from the same place, any time.

What this replaces

Doing it by hand means writing something like this, then keeping it working:

services:
  jellyseerr:
    image: fallenbagel/jellyseerr:2.7.3
    restart: unless-stopped
    ports:
      - "5055:5055"
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - ./jellyseerr/config:/config

And that is the easy half. Still to do:

Install a reverse proxy and write a server block for it
Get a TLS certificate and set up automatic renewal
Create the folders above with the right ownership, or it will not start
Point a DNS record at the server, because Jellyseerr cannot run under a shared path
Repeat all of it for the next app, and again on every server rebuild

On Cresdock, Jellyseerr is one click and none of the above exists.

Common questions

Do I need to know Docker to run Jellyseerr?

No. Cresdock installs Jellyseerr in one click from its catalogue: it pulls the image, writes the configuration, gets an HTTPS certificate and starts it. Jellyseerr gets its own web address and its own certificate, because it cannot run under a shared path.

What happens to my Jellyseerr data when it updates?

Cresdock updates the Jellyseerr image and leaves its stored data in place. Jellyseerr keeps its own files in its own folder, which survives an update, a rebuild and a reinstall — and Cresdock never writes into it.

How is Jellyseerr protected if it isn't behind the panel login?

It gets its own password, generated and set before it first starts, shown on its card in your dashboard. Apps end up here when they are reached by programs rather than a web browser, so a shared login can't be used.

Can my family use Jellyseerr too?

Yes. Cresdock is built for sharing a server: each person you add gets their own space, with their own apps and their own folders. The free plan covers one person, and adding more is what Pro is for. Jellyseerr also keeps its own accounts, so everyone signs in as themselves.

Can I run Jellyseerr at home instead of on a VPS?

Yes. Cresdock runs on a mini PC, an old desktop or anything that boots Debian, behind a normal home router with no port forwarding, and Jellyseerr is reachable on your own network first. A rented server is only needed when Jellyseerr must be reachable from anywhere without a VPN.

Can I remove Jellyseerr later?

Yes. Cresdock removes Jellyseerr in one click, and asks whether to keep its configuration for a future reinstall. Nothing else you have installed is affected.

Looking for what Jellyseerr itself can do? That lives in its own documentation — this page is only about running it.

Pairs well with: Kavita · Komga · how Jellyseerr connects to your other apps

Before you start: where to rent a server · what it needs to run · Cresdock vs CasaOS