-
Notifications
You must be signed in to change notification settings - Fork 18
Reverse Proxy and Seerr
If your server sits behind a reverse proxy (Nginx, Caddy, Traefik, and so on), make sure the proxy forwards every /Moonfin/ path through to your Jellyfin or Emby server, and passes auth headers along. Moonbase serves the web app, settings sync, and all of its APIs under /Moonfin/, so if those paths are not forwarded the web app and integrations will fail.
This matters most for Seerr. Seerr API traffic is proxied through your server at /Moonfin/Seerr/Api/ (and the legacy /Moonfin/Jellyseerr/Api/). If the proxy does not pass those paths through, Seerr requests will not reach Seerr.
Moonbase talks to Seerr from the server, not the browser. This is what makes single sign-on work: you log in once with your Jellyfin or Emby account, the server exchanges that for a Seerr session, and it stores the session server-side. Every later Seerr request rides that stored session through the proxy, so the client never handles Seerr credentials directly.
The plugin handles redirects, reverse-proxy sub-paths, and domain differences on the server side. If Seerr integration is not working, check that:
- Seerr is enabled and its URL is set in the Moonbase admin panel
- Your reverse proxy forwards
/Moonfin/paths, including/Moonfin/Seerr/Api/ - Auth headers are passed through by the proxy
Moonbase can notify users about Seerr request and issue activity. To do that, it registers a webhook in Seerr that points back at your server's /Moonfin/Seerr/Webhook endpoint. That inbound webhook is authenticated with a shared secret rather than a login, so it must be reachable through your proxy too.
From the admin panel you can view the webhook URL, its secret, and the current provisioning status, and re-register the webhook if you ever need to. Users choose what they want to be notified about in their own notification preferences.
See API Reference for the Seerr and notification endpoints.