![Seerr]()
Seerr
Container
Request manager for Jellyfin, Plex and Emby, where people ask for films and shows and Sonarr and Radarr fetch them. It's the merged successor to Overseerr and Jellyseerr. Source: https://github.com/seerr-team/seerr
Image details
Source details
Configuration
TypeContainerlinuxghcr.io/seerr-team/seerr:v35055:5055/tcp/app/configTZ=UTCunless-stoppedTemplate by NotAFlightRisk
Report issueNotes
http://<your-host>:5055 and the setup wizard walks you through connecting your media server, then Sonarr and Radarr. Settings and the request database live in the /app/config volume. Coming from Overseerr or Jellyseerr? Seerr can take over their config, see the docs for how.Standalone Install
Select an install method, to see config/commands for deploying Seerr
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select Seerr, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
More install options in our documentation, or see seerr-team/seerr for app-specific guidance.
Seerr is a free and open source software application for managing requests for your media library. It integrates with the media server of your choice: Jellyfin, Plex, and Emby. In addition, it integrates with your existing services, such as Sonarr, Radarr.Current Features
With more features on the way! Check out our issue tracker to see the features which have already been requested.
Getting Started
Check out our documentation for instructions on how to install and run Seerr:https://docs.seerr.dev/getting-started/
Preview
Migrating from Overseerr/Jellyseerr to Seerr
Read our release announcement to learn what Seerr means for Jellyseerr and Overseerr users.Please follow our migration guide for detailed instructions on migrating from Overseerr or Jellyseerr.
Support
- Check out the Seerr Documentation before asking for help. Your question might already be in the docs!
- You can get support on Discord.
- You can ask questions in the Help category of our GitHub Discussions.
- Bug reports and feature requests can be submitted via GitHub Issues.
API Documentation
You can access the API documentation from your local Seerr install at http://localhost:5055/api-docsCommunity
You can ask questions, share ideas, and more in GitHub Discussions.If you would like to chat with other members of our growing community, join the Seerr Discord server!
Our Code of Conduct applies to all Seerr community channels.
Contributing
You can help improve Seerr too! Check out our Contribution Guide to get started.Contributors ✨
Serve Seerr on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying seerr.example.com to http://seerr:5055
Add this to your Caddyfile
seerr.example.com {
reverse_proxy http://seerr:5055
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs seerr - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:5055 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :5055 - Stop the other service, or pick a different host port. In
5055:5055only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:5055. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, seerr can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 5055
Image won't pull
Test the pull directly on the host: docker pull ghcr.io/seerr-team/seerr:v3
- "manifest unknown" means the tag no longer exists.
- "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64, arm64 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect seerr --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue on seerr-team/seerr
- Template not working: Open an issue on NotAFlightRisk/portainer-templates-extras
- This website not working: Open an issue on lissy93/portainer-templates
A single container
Seerr runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.
The app image
An image is the app packed up ready to go, everything Seerr needs bundled into one download. This template pulls ghcr.io/seerr-team/seerr:v3, which Docker fetches once (about 239 MB) and then starts your own copy from.
Where the image comes from
Docker pulls its images from registries, public libraries of ready-built apps. Seerr's comes from the GitHub Container Registry, published by seerr-team.
Version tags
The bit after the colon in the image name is the version tag. This one pins v3, so every redeploy gives you that exact build until you bump it yourself.
Which machines it runs on
Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.
Ports
A port is the door the app answers on. A mapping like 5055:5055 means it's reachable on port 5055 of your server, where the left number is yours to change and the right one belongs to the app. It opens:
5055:5055
Volumes
A volume is where Seerr keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/app/configas a volume Docker manages for you
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Seerr takes 1 of them, all with defaults you can leave alone or tweak:
TZ, defaults toUTC. Like Europe/London
Restart policy
The restart policy here is unless-stopped, so Docker restarts Seerr after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).
Networking
Nothing custom is set, so Seerr sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.
Container name
Once it's deployed, Portainer names the container seerr. That's what you'll spot in the containers list and use in commands like docker logs seerr.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Open source license
Seerr is open source, released under the MIT license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Seerr up. Add the template list to Portainer once, then deploying Seerr is a click rather than a wall of config.