Connect to Seerr

[bimmer1977]

Now Seerr has been updated, can you see to integrade to it. I have tried to connect, but is don't work.

[bimmer1977]

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

[guillevc]

Thanks for reporting this! I looked into the error message and here's what I found:

The error cookie 'connect.sid' required is a bit misleading. Seerr's API supports two authentication methods (cookie auth or API key via X-Api-Key header). When neither is present in the request, the OpenAPI validator reports the first scheme's failure — hence the cookie error, even though the real issue is that the API key is also missing.

Listseerr does send the X-Api-Key header correctly when configured, so this likely points to a configuration issue on your end. Could you check the following?

1. API key configured in Listseerr — Make sure you've entered your Seerr API key in the Listseerr settings. You can find your API key in Seerr under Settings → General.
2. Seerr URL — Verify the URL you configured in Listseerr matches your Seerr instance (including the correct port, and no trailing slash).
3. Reverse proxy — If you're accessing Seerr through a reverse proxy (e.g., Nginx, Caddy, Traefik), make sure it's not stripping the X-Api-Key header from requests.

Let me know if you're still having trouble after checking these!

[bimmer1977]

Hi Still a issue [listseerr] 2026-03-10T07:24:15.038612942Z {"level":50,"time":1773127455038,"pid":1,"hostname":"9ff06fee8d5b","module":"jellyseerr-client","error":{"code":"ConnectionRefused","path":" http://192.168.1.32:5055/api/v1/request?filter=pending&take=1000 ","errno":0},"url":"http://192.168.1.32:5055","msg":"Failed to get pending requests count from Jellyseerr"} I just put in: Internal URL: http://192.168.1.32:5055 API key And User ID 1 Best Regards Brian

…

On Tue, Mar 10, 2026 at 2:30 AM guille ***@***.***> wrote: *guillevc* left a comment (guillevc/listseerr#13) <#13 (comment)> Thanks for reporting this! I looked into the error message and here's what I found: The error cookie 'connect.sid' required is a bit misleading. Seerr's API supports two authentication methods (cookie auth *or* API key via X-Api-Key header). When *neither* is present in the request, the OpenAPI validator reports the first scheme's failure — hence the cookie error, even though the real issue is that the API key is also missing. Listseerr does send the X-Api-Key header correctly when configured, so this likely points to a configuration issue on your end. Could you check the following? 1. *API key configured in Listseerr* — Make sure you've entered your Seerr API key in the Listseerr settings. You can find your API key in Seerr under Settings → General. 2. *Seerr URL* — Verify the URL you configured in Listseerr matches your Seerr instance (including the correct port, and no trailing slash). 3. *Reverse proxy* — If you're accessing Seerr through a reverse proxy (e.g., Nginx, Caddy, Traefik), make sure it's not stripping the X-Api-Key header from requests. Let me know if you're still having trouble after checking these! — Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGEI4ZKKCMQFVIGZ7DHPWOT4P5V2DAVCNFSM6AAAAACWL76ERCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAMRXHE4TCOJYHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>