saulutions.ca

// blog post

Part 2: Exposing Jellyseerr with a Domain

2 min read
#jellyseerr #reverse-proxy #domain

OIDC requires Jellyseerr to be accessible via a proper domain with HTTPS. You can’t just use http://192.168.1.50:5055 because the OIDC redirect flow needs a real URL that your identity provider can redirect back to.

This is a short one. If you’re already running a homelab with services behind domains, you probably know the drill. I’m not going to write a full reverse proxy tutorial, just the Jellyseerr-specific bits.

Your options

Pick whichever you’re already using:

Nginx Proxy Manager / NPM Plus - Add a new proxy host pointing to your Jellyseerr container’s IP on port 5055. Enable SSL with Let’s Encrypt. This is what I use.

Caddy - Add a reverse proxy block in your Caddyfile:

requests.yourdomain.com {
    reverse_proxy <jellyseerr-ip>:5055
}

Caddy handles SSL automatically.

Cloudflare Tunnel - Create a new public hostname in your tunnel config pointing to http://<jellyseerr-ip>:5055. No port forwarding needed.

Traefik - Add labels to your config or a file provider entry. You know the drill if you’re already using Traefik.

What matters

Whatever method you choose, make sure:

  1. HTTPS is enabled - OIDC redirects won’t work over plain HTTP
  2. The domain resolves - Test by visiting https://requests.yourdomain.com (or whatever you picked) in your browser
  3. WebSocket support - Some reverse proxies need this enabled explicitly for Jellyseerr’s real-time features

Once you can access Jellyseerr through your domain and see the setup wizard or login page, you’re good. Head to Part 3 where we connect everything to Pocket ID.

Comments