NeXroll Preroll Manager
NeXroll manages and schedules the preroll videos your media servers play before a movie. It supports Plex, Jellyfin, and Emby.
Enable nexroll in the Container Map. No other settings are required. The playbook will:
- Create a
prerollsfolder on your media share, next to the_libraryfolder - Mount that folder into NeXroll at the same path your media servers already use for it
- Fill in the Plex connection details if Plex is enabled
NeXroll is then available at nexroll.<domain> through Traefik, or on port 9393 if ports are exposed.
Where the prerolls live
Section titled “Where the prerolls live”NeXroll keeps its own database, settings, logs, and thumbnails in /data inside its container. That is mapped to the usual app folder, <hmsdocker_apps_path>/nexroll/config.
The preroll videos are stored on the media share instead, so that Plex, Jellyfin, and Emby can read them through the media mount they already have:
| Path | |
|---|---|
| On the host | <hmsdocker_mount_path>/<hmsdocker_primary_mount_name>/prerolls (by default /mnt/hms-docker/media_data/prerolls) |
| Inside Plex, Jellyfin, and Emby | /data/media_data/prerolls |
| Inside NeXroll | /data/media_data/prerolls (this is also set as NEXROLL_PREROLL_PATH) |
When NeXroll sets a preroll in Plex, it writes the file path into Plex’s “Movie pre-roll video” setting, and Plex plays the file from its own disk. That path has to be the path Plex uses for the file. Because the prerolls folder is mounted at the same path in NeXroll and in the media servers, the path NeXroll sends is already correct.
NeXroll needs write access to the prerolls folder, because it saves uploads, downloads, and thumbnails there and moves files into category folders. Make sure the folder is writable by the hmsdocker_container_uid/hmsdocker_container_gid user, as with the rest of your media share. NeXroll runs as that user (NEXROLL_RUN_AS_PUID=true).
Connecting your media servers
Section titled “Connecting your media servers”All containers share the proxy_net network, so NeXroll reaches the media servers by container name. Host networking, which the NeXroll docs suggest, is not needed.
If Plex is enabled, NeXroll is started with PLEX_URL=http://plex:32400 and PLEX_TOKEN set to the Plex token the playbook reads from your Plex config. The token is only available after Plex has been claimed and the playbook has run again, so you may need to run the playbook a second time after setting up Plex. You can also connect Plex by hand in NeXroll under Connect > Plex using the same URL.
Jellyfin
Section titled “Jellyfin”Jellyfin is set up in the NeXroll web UI. Under Connect > Jellyfin, use http://jellyfin:8096 as the server URL and an API key created in Jellyfin under Dashboard > API Keys.
Jellyfin plays prerolls through the NeXroll Intros plugin, which downloads them from NeXroll over the network rather than reading the folder. When the plugin asks for the NeXroll URL, use http://nexroll:9393.
Emby is set up in the NeXroll web UI, not with environment variables. Under Connect > Emby, use http://emby:8096 as the server URL and an API key from Emby’s Settings > API Keys. Like Jellyfin, Emby uses the NeXroll Intros plugin, which downloads prerolls from http://nexroll:9393. See the NeXroll Emby guide for the plugin setup.