Jellyfin, Seerr, and JellyBridge are not three parts of one ZimaOS app. The June 2026 IceWhale Community thread became easier to understand once the stack was separated into layers: Jellyfin is the media server, Seerr is a standalone media-request application, and JellyBridge is a Jellyfin plugin that connects Jellyfin discovery and request actions to Seerr.
The original poster already had Jellyfin running from the ZimaOS App Store but could not get the rest of the stack working. Community replies recommended diagnosing each layer independently instead of changing everything at once. A later user confirmed that they had Jellyfin and Seerr running successfully on a ZimaBoard 2 while their Sonarr/Radarr stack ran on a separate Raspberry Pi, showing that these services do not need to live in the same container or even on the same machine as long as the URLs, API credentials, and network routes are correct.
Understand the Jellyfin → Seerr → JellyBridge Stack First
The cleanest way to think about the setup is:
- Jellyfin: serves and manages your existing movie and TV libraries.
- Seerr: provides discovery and media requests, then sends approved requests to Sonarr and Radarr.
- Sonarr/Radarr: handle TV-series and movie acquisition workflows.
- JellyBridge: runs inside Jellyfin as a plugin and talks to Seerr so discovery or favorites in Jellyfin can create requests.
Current Seerr documentation describes Seerr as a media-request and discovery manager for Jellyfin, Plex, and Emby with native Sonarr and Radarr integration. Seerr normally runs as its own Docker container and exposes its web interface on port 5055. See the current Seerr getting-started guide.
Seerr Is the Current Successor to Jellyseerr and Overseerr
One community reply noted that Seerr had replaced the older Jellyseerr application. Current Seerr project documentation confirms that Seerr is the combined successor path for Jellyseerr and Overseerr users.
This matters because older JellyBridge documentation, screenshots, environment variables, or container names may still say Jellyseerr. The current JellyBridge project states that Seerr 3.x uses a compatible API for the integration it tested, while retaining Jellyseerr terminology in parts of its documentation.
If you are building this stack now, start with current Seerr rather than intentionally installing an obsolete Jellyseerr release unless a specific plugin version explicitly requires it.
Step 1: Get Seerr Running Before Installing JellyBridge
Do not troubleshoot JellyBridge until Seerr itself is healthy. Install Seerr as a separate ZimaOS Docker application or using the supported app source available on your current system.
After installation, verify the Seerr web interface directly:
http://ZIMAOS_LAN_IP:5055The host port can be different if your ZimaOS container mapping uses another external port. Use the host-side port shown in the actual app settings.
If Seerr does not open, check the container before touching Jellyfin:
docker ps
docker images
docker logs SEERR_CONTAINER_NAME --tail 100Those commands were the first troubleshooting checks suggested in the community thread. If Docker commands require elevated host permissions on your ZimaOS build, use the authorized terminal workflow rather than weakening Docker socket permissions.
Step 2: Connect Seerr to Jellyfin
During Seerr setup, configure Jellyfin using an administrative Jellyfin account. Current Seerr documentation says the Jellyfin settings page is responsible for server connection and library synchronization.
Confirm the following before continuing:
- Seerr can reach the Jellyfin URL you entered.
- The Jellyfin account used during setup has the required administrative access.
- Your Jellyfin libraries appear in Seerr after synchronization.
- A manual library scan completes successfully.
See the Seerr media-server settings guide for the current Jellyfin connection workflow.
Step 3: Connect Seerr to Sonarr and Radarr
Seerr does not download media by itself. It sends approved requests to Sonarr and Radarr, which then coordinate the rest of the automation stack.
Sonarr and Radarr may run:
- on the same ZimaOS host;
- in separate Docker containers;
- on another home server;
- or, as one community user described, on a separate Raspberry Pi.
The important requirement is reachability. Seerr must use an address that works from the Seerr container or host context. A browser URL that works on your laptop is not automatically the correct container-to-container address.
Do Not Assume ZimaOS App Store Containers Share the Same Docker Network
The most useful networking warning in the community reply was that a Jellyfin container installed from the ZimaOS App Store may not automatically see a manually installed Seerr container by container name.
If both containers are on the same user-defined Docker network, a service name such as:
http://seerr:5055may work. If they are on different Docker networks, use a reachable host address and published port instead, for example:
http://ZIMAOS_LAN_IP:5055Do not use localhost casually between containers. Inside the Jellyfin container, localhost refers to the Jellyfin container itself, not to a separate Seerr container.
Step 4: Install JellyBridge Inside Jellyfin
JellyBridge is a Jellyfin plugin, not another ZimaOS app that needs to replace Jellyfin. The project's current installation method recommends adding its plugin repository through the Jellyfin administration interface.
In Jellyfin:
- Open Dashboard > Plugins.
- Open repository management.
- Add the JellyBridge plugin repository URL supplied by the project.
- Open the plugin catalog.
- Install the JellyBridge build that matches your Jellyfin version.
- Restart Jellyfin.
The current JellyBridge repository documents version-specific plugin builds for Jellyfin 10.10 and 10.11. Check the compatibility notes before choosing a package. See the JellyBridge project documentation.
Step 5: Configure JellyBridge to Reach Seerr
After Jellyfin restarts, open the JellyBridge plugin configuration and provide:
- the Seerr URL reachable from Jellyfin;
- the Seerr API key required by the plugin;
- a dedicated directory for JellyBridge library data;
- the synchronization behavior you want to use.
Use the plugin's Test Connection function before importing discover content. If the test fails, do not create more libraries yet. Fix the Seerr URL, Docker network, or API key first.
Step 6: Create the JellyBridge Discover Library
JellyBridge creates placeholder and discovery content that Jellyfin can display as a library. The current plugin documentation includes an in-plugin setup workflow for generating and configuring that library.
Keep this library separate from your actual movie and TV media paths. JellyBridge discovery items are not substitutes for the real files managed by Sonarr, Radarr, and Jellyfin.
When users favorite supported discover items in Jellyfin, JellyBridge can send the corresponding request to Seerr. Seerr then handles approval and forwards the request to Sonarr or Radarr according to your configuration.
The Community ZimaBoard 2 Example
A later participant said they had Jellyfin and the newer Seerr application working together on a ZimaBoard 2, while their ARR stack ran on a Raspberry Pi 4. That is useful evidence that the architecture can span multiple systems.
The current product path for ZimaBoard hardware is the ZimaBoard 2 single-board server.
The reply did not provide the user's exact Docker Compose files or network settings, so it should not be treated as a verified copy-and-paste configuration. Its value is architectural: the services can be separated as long as each integration endpoint is reachable.
Troubleshoot the Stack in This Order
- Confirm Jellyfin works independently.
- Confirm the Seerr container stays running.
- Open the Seerr Web UI directly.
- Confirm Seerr can authenticate to Jellyfin and synchronize libraries.
- Confirm Seerr can connect to Sonarr and Radarr.
- Install the JellyBridge version compatible with your Jellyfin version.
- Confirm JellyBridge can test its connection to Seerr.
- Create the JellyBridge discovery library only after the connection test passes.
- Test one request from Jellyfin and confirm it appears in Seerr.
- Then verify that Seerr forwards the request to the correct Sonarr or Radarr instance.
Jellyfin, Seerr and JellyBridge FAQ
Does Seerr need its own Docker container?
Yes. Seerr is a standalone request-management application. JellyBridge is the Jellyfin plugin that communicates with it.
Should JellyBridge appear as a ZimaOS App Store application?
Not necessarily. The current JellyBridge project distributes it as a Jellyfin plugin installed through Jellyfin's plugin repository system.
Why does localhost:5055 fail from JellyBridge?
If Jellyfin and Seerr are separate containers, localhost inside Jellyfin points back to the Jellyfin container. Use a shared Docker-network service name or a host/IP address that the Jellyfin container can actually reach.
Should I install Jellyseerr or Seerr?
For a new current deployment, Seerr is the maintained successor path. JellyBridge documentation still contains Jellyseerr terminology and compatibility notes because the transition is recent, so verify your JellyBridge release against the Seerr version you install.
Can Sonarr and Radarr run on another server?
Yes. A community user described exactly that layout. Seerr only needs network access to the Sonarr/Radarr API endpoints and valid API keys; the applications do not need to share the same physical server.
