Trakt API returns 403

[hermagnussen-dotcom]

Bug: Trakt API returns 403 - Missing User-Agent header**

During onboarding, the Trakt API configuration step always fails with Trakt API returned status 403, making it impossible to complete setup.

Root Cause Maybe:
Trakt now requires a valid User-Agent header in all API requests. Without it, Cloudflare blocks the request and returns 403. The Trakt team has confirmed this in their developer communications:

Steps to reproduce:

1. Start fresh SeerrBridge setup
2. Complete DMM Config and Overseerr steps
3. Enter any valid Trakt Client ID on the Trakt step
4. Click Test & Continue
5. Always returns: Trakt API returned status 403

[geo7474]

I have the same issue

[Yatoohh]

I'm also running into this problem, any solutions so far?

[HardwareGeiler]

To fix it, just follow this:
Need to have seerrbridge in docker:

• while in SeerrBridge docker, run docker exec -it seerrbridge sh
• then, run sed -i 's/"trakt-api-key": trakt_api_key,/"User-Agent": "SeerrBridge/1.0",\n "trakt-api-key": trakt_api_key,/g' /app/.output/server/chunks/routes/api/setup-test-trakt.post.mjs to manually add User-Agent-Header
• then just restart the docker with docker restart seerrbridge
• works again, after this

[Phyks]

Seems you also have to apply the same trick to https://github.com/Woahai321/SeerrBridge/blob/f7ca993df6f874d2175ff78c871b0937094d7553/seerr/trakt.py and https://github.com/Woahai321/SeerrBridge/blob/f7ca993df6f874d2175ff78c871b0937094d7553/seerr/image_utils.py