From aeb3b7b71e27597916f3e80f3c9fe85320974372 Mon Sep 17 00:00:00 2001 From: enoch85 Date: Fri, 21 Aug 2026 06:07:49 +0000 Subject: [PATCH] docs: document connecting to Plex in a separate Docker stack Plex running in its own Docker Compose stack advertises the address of the network it sits on, which nothing outside that network can reach. Maintainerr authenticates fine and may even list the server, but every connection to it fails, and the cause is invisible from Maintainerr's side. This is a subsection with its own heading rather than another admonition. The Plex section already carries three notes, and the report was specifically that the fix is unfindable, so a sidebar entry is worth more than a fourth callout. It sits after the collapsible blocks so neither of them falls under it. The existing "Server list is empty" block covers a different symptom, where Plex publishes no reachable connection at all and the dropdown stays empty. --- docs/Configuration.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/Configuration.md b/docs/Configuration.md index f07cc862c..357f9fef7 100644 --- a/docs/Configuration.md +++ b/docs/Configuration.md @@ -89,6 +89,12 @@ If you want Maintainerr to connect securely in manual mode, use your `*.plex.dir +### Plex in a separate Docker stack + +If Plex and Maintainerr sit on different Docker networks, for example because each has its own Compose stack, Plex advertises an address that only exists inside its own network. Authentication succeeds and the server may even be listed, but connecting to it always fails. + +Add your server's LAN address, such as `http://192.168.1.10:32400`, to `Custom server access URLs` under `Settings → (your server) → Network` in Plex Web (click **Show Advanced** to reveal the field), then press the **Refresh icon** next to the server selector in Maintainerr. + ## Jellyfin Jellyfin can also be used as your media server connection.