nextcloud/community-containers/jellyseerr/readme.md

Seerr

This container bundles Seerr and auto-configures it for you.

Notes

• Migration from Jellyseerr: Jellyseer previously ran as the root user. With the migration to Seerr, the container now runs rootless with userid 1000, meaning that if you previously used Jellyseerr, Seerr will not be able to access the config files generated by the old Jellyseerr container. To migrate, execute the following steps: 1. stop all containers using the AIO-interface, 2. run sudo docker run --rm -v nextcloud_aio_jellyseerr:/data alpine chown -R 1000:1000 /data
• This container is only intended to be used inside home networks as it uses http for its management page by default.
• After adding and starting the container, you can directly visit http://ip.address.of.server:5055 and access your new Seerr instance, which can be used to manage Plex, Jellyfin, and Emby.
• In order to access your Seerr outside the local network, you have to set up your own reverse proxy. You can set up a reverse proxy following these instructions and Seerr's reverse proxy documentation., OR use the Caddy community container that will automatically configure requests.$NC_DOMAIN to redirect to your Seerr. Note that it is recommended to enable CSRF protection in Seerr for added security if you plan to use Seerr outside the local network, but make sure to read up on it and understand the caveats first.
• If you want to secure the installation with fail2ban, you might want to check out https://github.com/nextcloud/all-in-one/tree/main/community-containers/fail2ban. Note that enabling the proxy support option in Seerr is required for this to work properly.
• The config of Seerr will be automatically included in AIO's backup solution!
• See here how to add it to the AIO stack.

Repository

https://github.com/seerr-team/seerr

Maintainer

https://github.com/Anvil5465