Service configuration

Initial recommendation

Start with the smallest useful set: one media server, one request flow, and email/notifications if needed. Add modules only after validating the previous layer.

Media servers

Configure Plex first, or Jellyfin/Emby where appropriate. Use a URL reachable from the PlexSub container and credentials with the required permissions.

Requests

Choose Seerr/Overseerr/Jellyseerr or native Requests as the primary flow. Test user mapping, request creation, duplicate handling, and Customer Portal visibility.

Library automation

Radarr and Sonarr manage movies and series. Configure profiles, root folders, and quality settings in Arr before connecting PlexSub.

Downloads

Connect qBittorrent or another supported provider only when its web interface is reachable and secure. Confirm that customers can see only their relevant downloads.

Subtitles and indexers

Bazarr depends on healthy Arr integrations. Configure preferred languages and test missing-subtitle data before exposing it.

Analytics and maintenance

Tautulli, Tracearr, Jellystat, and Maintainerr provide optional history, activity, or cleanup data. Treat beta and experimental modules as features to validate with test users.

Payments and email

Configure payment and SMTP providers separately from media integrations. Keep their secrets protected and verify the resulting customer messages and access state.

Support

Enable support and Knowledge Base content only when the information is current and safe for customers.

Unused services

Pause or disable unused modules. Do not show a portal section that appears available when its integration is not configured.

Security

Keep credentials encrypted through Settings where available, do not share secrets, and run diagnostics after every significant service change.