Failed connection to Jellyfin server - cookie 'connect.sid' required

[timkolloch]

Hey guys,

I am trying to get Jellyseerr running behind a reverse proxy also using ssl in private network but I cannot reach the Jellyfin server.
Based on the error I can see in the browser console I think that the problem lies in my Jellyseerr/Proxy configuration and does not even reach Jellyfin.

When I first access Jellyseer (I am on the setup page where I have to chose the media server) I can already see the following error in the browser console:

GET https://jellyseerr.example.com/api/v1/auth/me
Status 401
Version HTTP/2
Referrer Policy strict-origin-when-cross-origin

Request Headers:
GET /api/v1/auth/me HTTP/2
Host: jellyseerr.example.com
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br, zstd
Referer: https://jellyseerr.example.com/setup
Connection: keep-alive
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-origin
Priority: u=4
TE: trailers

Response Headers:
HTTP/2 401 
server: openresty
date: Wed, 08 Jan 2025 16:13:35 GMT
content-type: application/json; charset=utf-8
content-length: 123
x-powered-by: Express
etag: W/"7b-7+mc+t2aR975jcHVAOp1Gztt4z8"
X-Firefox-Spdy: h2

When I look at the response body this is the content:

{"message":"cookie 'connect.sid' required","errors":[{"path":"/api/v1/auth/me","message":"cookie 'connect.sid' required"}]}

Maybe someone already has an idea how to help but to give some more reference I will lay out my setup as well:

Setup explanation

General Setup

Everything is dockerized and all containers are in the same docker network.
I have a pihole as my private DNS and nginx proxy manager (NPM) as my reverse proxy.
I also have a domain, example.com, and a wildcard ssl certificate for it.

Pi Hole setup

In my pihole I have a private DNS entry for npm.internal that resolves to the IP of my server, where all docker containers are running on.
Furthermore I have CNAME entries for jellyfin.example.com and jellyseerr.example.com both directed at npm.internal

NPM setup

Then in NPM I have the following proxies:

1. jellyfin.example.com: Redirecting to https://jellyfin:8920, blocking common exploits and websocket support enabled. It uses the wildcard certificate and forces SSL
2. jellyseerr.example.com: configured according to the example, also using the wildcard certificate.

Jellyfin settings (Networking)

• Server Address Settings
  • Local HTTP port: 8096
  • Enable HTTPS
  • Local HTTPS port: 8920
• HTTPS Settings
  • Require HTTPS
  • Custom SSL certificate path: I exported my *.example.com certificate to a cert.pfx and mapped it into the container, this is the path to it
• IP Protocols
  • Enable IPv4

All other fields are empty and all other checkboxes are unchecked.

Let me know if I can provide more/different information or I should try anything different.

Best wishes!

[Fallenbagel]

/auth/me is not related. You should be looking for /auth/jellyfin

/auth/me is just a check to see if you're logged in and is not an issue.
Please hop onto discord for support requests.

[timkolloch]

Alright, will do that, thank you!