Skip to main content

Integration diagnostics guide

Common method​

For every integration, check in this order:

  1. The external service works independently.
  2. Its URL is reachable from the PlexSub container.
  3. Credentials or API keys are valid and have sufficient permissions.
  4. The module is enabled and configuration was saved.
  5. PlexSub diagnostics and logs report a healthy result.
  6. A test user sees only expected data in the Customer Portal.

Plex, Jellyfin, and Emby​

Check the server URL, token/API key, container connectivity, reachable libraries, and certificate/proxy configuration. For history or usage, also verify the relevant analytics provider.

Seerr, Overseerr, and Jellyseerr​

Check the API key, internal URL, user mapping, webhook secret, request permissions, and whether native Requests is also active. Avoid two competing request sources.

Radarr and Sonarr​

Confirm the API key, URL, profiles, root folders, and manual add flow in Arr. Then create a test request and verify its resulting metadata, profile, and queue state.

qBittorrent​

Confirm Web UI access from PlexSub, login credentials, queue visibility, and customer ownership mapping. Re-save credentials if its session is rejected.

Bazarr​

Confirm Bazarr can see Radarr/Sonarr, its API key is valid, and its language preferences match the desired result.

Tautulli​

Confirm it receives Plex activity, its API key works, and the affected user is correctly mapped. Allow time for synchronisation before treating history as missing.

Maintainerr​

Confirm its URL/API key, active rules, Plex dependency, and that scheduled-deletion data is suitable for customer visibility.

SMTP email​

Confirm host, port, TLS mode, sender, credentials, and delivery to an external mailbox. Review domain authentication when messages land in spam.

Payments​

Confirm provider credentials and webhook secrets, then compare the provider's authoritative state with PlexSub's derived access state using a safe test account.