From e279cd2de12155076fd9fffb06128c6ac27e4b48 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 8 Jun 2026 19:31:58 +0000 Subject: [PATCH 1/5] docs: add Plex server-list troubleshooting guidance --- docs/Configuration.md | 19 +++++++++++++++++++ .../version-3.14.0/Configuration.md | 19 +++++++++++++++++++ 2 files changed, 38 insertions(+) diff --git a/docs/Configuration.md b/docs/Configuration.md index b98e1308..e6bd447e 100644 --- a/docs/Configuration.md +++ b/docs/Configuration.md @@ -54,6 +54,25 @@ Proper DNS is preferred. Plex discovery and failover can depend on resolvable Pl `Test Connection` is disabled until you are authenticated and have either selected a discovered server or enabled manual override with saved settings. ::: +
+Server list is empty (VPS, cloud host, or custom networking) + +Maintainerr only lists Plex servers that publish a **reachable** connection to plex.tv. If authentication succeeds but the server dropdown stays empty, Plex is most likely publishing only a `local` connection that Maintainerr (running elsewhere) cannot use. This is common when Plex runs on a **VPS / cloud host** or behind unusual networking, where Plex's automatic Remote Access cannot detect a public connection. + +Fix it on the Plex side by publishing a reachable address: + +1. In Plex, open `Settings -> Network -> Custom server access URLs`. +2. Add a reachable **HTTPS** URL **including the port** — for example your server's `*.plex.direct` address: `https://..plex.direct:32400`. Using the `.plex.direct` host keeps a valid certificate; a reverse-proxied domain with its own valid certificate works too. You can usually copy the correct address from Seerr if that service is already connected to the same Plex server. +3. Save and restart Plex. (On some Docker images this setting is an environment variable instead — for example `PLEX_ADVERTISE_URL` on the hotio image.) + +Back in Maintainerr, press the **Refresh icon** next to the server selector — the server now appears in the list. + +:::tip +If Maintainerr and Plex share a Docker network, you can instead skip discovery and point Maintainerr at Plex's **internal** address (e.g. `http://plex:32400`) with manual connection override below. +::: + +
+
Advanced: manual connection override diff --git a/versioned_docs/version-3.14.0/Configuration.md b/versioned_docs/version-3.14.0/Configuration.md index 5fb37d0a..a6642e51 100644 --- a/versioned_docs/version-3.14.0/Configuration.md +++ b/versioned_docs/version-3.14.0/Configuration.md @@ -54,6 +54,25 @@ Proper DNS is preferred. Plex discovery and failover can depend on resolvable Pl `Test Connection` is disabled until you are authenticated and have either selected a discovered server or enabled manual override with saved settings. ::: +
+Server list is empty (VPS, cloud host, or custom networking) + +Maintainerr only lists Plex servers that publish a **reachable** connection to plex.tv. If authentication succeeds but the server dropdown stays empty, Plex is most likely publishing only a `local` connection that Maintainerr (running elsewhere) cannot use. This is common when Plex runs on a **VPS / cloud host** or behind unusual networking, where Plex's automatic Remote Access cannot detect a public connection. + +Fix it on the Plex side by publishing a reachable address: + +1. In Plex, open `Settings -> Network -> Custom server access URLs`. +2. Add a reachable **HTTPS** URL **including the port** — for example your server's `*.plex.direct` address: `https://..plex.direct:32400`. Using the `.plex.direct` host keeps a valid certificate; a reverse-proxied domain with its own valid certificate works too. You can usually copy the correct address from Seerr if that service is already connected to the same Plex server. +3. Save and restart Plex. (On some Docker images this setting is an environment variable instead — for example `PLEX_ADVERTISE_URL` on the hotio image.) + +Back in Maintainerr, press the **Refresh icon** next to the server selector — the server now appears in the list. + +:::tip +If Maintainerr and Plex share a Docker network, you can instead skip discovery and point Maintainerr at Plex's **internal** address (e.g. `http://plex:32400`) with manual connection override below. +::: + +
+
Advanced: manual connection override From cb5dab8e0c5420a86cb1191425f48ff40c381a6d Mon Sep 17 00:00:00 2001 From: enoch85 Date: Mon, 8 Jun 2026 21:33:36 +0200 Subject: [PATCH 2/5] Delete versioned_docs/version-3.14.0/Configuration.md --- .../version-3.14.0/Configuration.md | 197 ------------------ 1 file changed, 197 deletions(-) delete mode 100644 versioned_docs/version-3.14.0/Configuration.md diff --git a/versioned_docs/version-3.14.0/Configuration.md b/versioned_docs/version-3.14.0/Configuration.md deleted file mode 100644 index a6642e51..00000000 --- a/versioned_docs/version-3.14.0/Configuration.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -id: configuration -slug: /configuration -description: Information on how to get Maintainerr up and running. -title: Configuration ---- - -All configuration is done inside the application. No extra config files are required. - -When you first access the web UI, you should be redirected to the settings page. If that does not happen, try refreshing the page. - -:::note -All Base URL settings are to be entered without the leading slash. - -- Right: `tautulli` -- Wrong: `/tautulli` - -::: - -## General - -These settings are OK for most installations. - -| Setting | Description | -| -------- | --------------------------------------------------------------- | -| Hostname | The hostname or IP address of the host running Maintainerr | -| API key | Maintainerr's API key. It is currently reserved for future use. | - -## Media Server - -You need to configure one media server: Plex, Jellyfin, or Emby. Multiple media servers are not supported simultaneously. - -## Plex - -Plex can be used as your media server connection. - -When using a local Plex instance, make sure Plex's `Secure connections` network setting is set to `Preferred` instead of `Required`. - -Maintainerr's normal Plex setup uses Plex authentication and server discovery instead of a manual host/port form. - -After you authenticate with a Plex **admin** account, Maintainerr validates the token, loads the servers available to that account, and lets you choose from discovered connection candidates. This is the recommended setup because Maintainerr can use the discovered server details directly and keep automatic reconnection behavior enabled. - -:::tip -Proper DNS is preferred. Plex discovery and failover can depend on resolvable Plex endpoints, and Docker users in particular may run into intermittent connection or discovery problems when container DNS is unstable. If possible, make sure your environment has working DNS resolution for Plex-related hostnames and service names. -::: - -| Setting / Control | Description | -| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| Authentication | Authenticate with Plex using an **admin** account. Until this succeeds, the Plex server controls stay disabled. | -| Server | Shows the currently selected discovered server, or lets you choose one from the discovered server list. | -| Refresh icon | Re-runs Plex server discovery for the authenticated account. Use this if the server list is stale or discovery failed the first time. | - -:::tip -`Test Connection` is disabled until you are authenticated and have either selected a discovered server or enabled manual override with saved settings. -::: - -
-Server list is empty (VPS, cloud host, or custom networking) - -Maintainerr only lists Plex servers that publish a **reachable** connection to plex.tv. If authentication succeeds but the server dropdown stays empty, Plex is most likely publishing only a `local` connection that Maintainerr (running elsewhere) cannot use. This is common when Plex runs on a **VPS / cloud host** or behind unusual networking, where Plex's automatic Remote Access cannot detect a public connection. - -Fix it on the Plex side by publishing a reachable address: - -1. In Plex, open `Settings -> Network -> Custom server access URLs`. -2. Add a reachable **HTTPS** URL **including the port** — for example your server's `*.plex.direct` address: `https://..plex.direct:32400`. Using the `.plex.direct` host keeps a valid certificate; a reverse-proxied domain with its own valid certificate works too. You can usually copy the correct address from Seerr if that service is already connected to the same Plex server. -3. Save and restart Plex. (On some Docker images this setting is an environment variable instead — for example `PLEX_ADVERTISE_URL` on the hotio image.) - -Back in Maintainerr, press the **Refresh icon** next to the server selector — the server now appears in the list. - -:::tip -If Maintainerr and Plex share a Docker network, you can instead skip discovery and point Maintainerr at Plex's **internal** address (e.g. `http://plex:32400`) with manual connection override below. -::: - -
- -
-Advanced: manual connection override - -Most users should leave this closed and use the normal Plex authentication and discovery flow. - -If discovery does not give you the connection you want, open `Advanced Settings` and enable `Manual connection override`. That lets you enter the hostname, port, and TLS mode directly. - -Manual mode is a fallback option: - -- Plex authentication is still required. -- It overrides the discovered Plex connection. -- It disables automatic reconnection for that Plex entry until you switch back. - -If you want Maintainerr to connect securely in manual mode, use your `*.plex.direct` URL as the hostname and enable TLS. You can usually copy the correct address from Seerr if that service is already connected to the same Plex server. - -
- -## Jellyfin - -Jellyfin can also be used as your media server connection. - -| Setting | Description | -| ------------ | ---------------------------------------------------------------- | -| Jellyfin URL | The domain name or local IP address of the host running Jellyfin | -| API key | A Jellyfin API key generated from your Jellyfin server | -| Admin User | Test Connection to load the available admin users | - -## Streamystats - -:::note -Streamystats is only available for Jellyfin users -::: - -The separate `Settings -> Streamystats` page only appears when Jellyfin is the active media server. Maintainerr reuses your saved Jellyfin API key for authentication, so you only need to provide the Streamystats base URL. - -| Setting | Description | -| ------- | ----------------------------------------------------------------------------------------------------------------- | -| URL | The base URL of your Streamystats instance, such as `http://localhost:3000` or `https://streamystats.example.com` | - -## Emby - -Use your Emby server URL directly. Maintainerr supports either entering an API key manually or using `Sign in with Emby` to authenticate with an admin username and password and let Maintainerr populate the API key for you. Emby Connect is not supported because Maintainerr uses direct server authentication and does not implement Emby's cloud-based Connect flow. - -| Setting | Description | -| ---------- | -------------------------------------------------------------------------------------------------------------------------------------- | -| Emby URL | The domain name or local IP address of the host running Emby | -| API key | An Emby API key generated from `Dashboard -> Advanced -> API Keys`, or the token returned by `Sign in with Emby` | -| Admin User | Test Connection to load the available admin users, or use `Sign in with Emby` to populate the saved admin-user selection automatically | - -## Seerr - -Seerr configuration is required if you want to use Seerr-related rule parameters or remove Seerr requests. - -| Setting | Description | -| ------- | ------------------------------------------------------------- | -| URL | The domain name or local IP address of the host running Seerr | -| API key | The API key from Seerr settings | - -## Radarr - -Radarr's configuration is required to use its parameters in rules and to remove or unmonitor movies. - -| Setting | Description | -| -------------- | -------------------------------------------------------------- | -| Server Name | A friendly name to help identify the server | -| Hostname or IP | The domain name or local IP address of the host running Radarr | -| Port | The port Radarr runs on | -| Base URL | The URL base configured in Radarr, if one is set | -| API key | The API key from Radarr settings | - -## Sonarr - -Sonarr's configuration is required to use its parameters in rules and to remove or unmonitor shows. - -| Setting | Description | -| -------------- | -------------------------------------------------------------- | -| Server Name | A friendly name to help identify the server | -| Hostname or IP | The domain name or local IP address of the host running Sonarr | -| Port | The port Sonarr runs on | -| Base URL | The URL base configured in Sonarr, if one is set | -| API key | The API key from Sonarr settings | - -## Metadata - -Maintainerr has a separate `Settings -> Metadata` page for poster, backdrop, and metadata-provider settings used across the UI. - -This page is mainly useful when you want better artwork fallback, more reliable cross-provider ID resolution, or more control over which metadata source Maintainerr prefers. - -| Setting | Description | -| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| TMDB API key | Optional. If you leave this empty, Maintainerr uses its built-in shared TMDB key. Add your own key if you want an isolated quota or your own TMDB account access. | -| TVDB API key | Optional. Enables TVDB as an additional metadata source and fallback for ID cross-references. TVDB cannot be selected as primary until it is configured. | -| Primary | Chooses whether Maintainerr prefers TMDB or TVDB first when resolving posters, backdrops, and related metadata lookups. | -| Refresh metadata | Clears cached metadata for that provider and asks your media server to refresh matching items that already have provider IDs stored. | - -Typical usage: - -- Leave TMDB on its default setup if you just want Maintainerr to work out of the box. -- Add a TVDB key if you want another source for artwork and metadata cross-references. -- Switch the primary provider if you prefer one source's results over the other. -- Use `Refresh metadata` after changing provider settings, when testing a new provider, or when provider artwork and IDs look stale. - -The metadata refresh action runs in the background. It clears Maintainerr's cached provider responses first, then asks your configured media server to refresh items that are already linked to that metadata provider. - -In practice: - -- changing the API key or primary provider affects future metadata lookups -- `Refresh metadata` is the manual "re-check existing linked items" action -- refresh may take longer on larger libraries because Maintainerr asks the media server to refresh existing items that already have matching provider IDs - -## Tautulli - -:::note -Tautulli is only available for Plex users -::: - -Tautulli's configuration is required to use its parameters in rules. - -| Setting | Description | -| ------- | ---------------------------------------------------------------- | -| URL | The domain name or local IP address of the host running Tautulli | -| API key | The API key from Tautulli settings | From ac01e04effa7dbd104c21b0a4a547489fa984259 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 8 Jun 2026 19:37:58 +0000 Subject: [PATCH 3/5] docs: restore versioned configuration file --- .../version-3.14.0/Configuration.md | 197 ++++++++++++++++++ 1 file changed, 197 insertions(+) create mode 100644 versioned_docs/version-3.14.0/Configuration.md diff --git a/versioned_docs/version-3.14.0/Configuration.md b/versioned_docs/version-3.14.0/Configuration.md new file mode 100644 index 00000000..a6642e51 --- /dev/null +++ b/versioned_docs/version-3.14.0/Configuration.md @@ -0,0 +1,197 @@ +--- +id: configuration +slug: /configuration +description: Information on how to get Maintainerr up and running. +title: Configuration +--- + +All configuration is done inside the application. No extra config files are required. + +When you first access the web UI, you should be redirected to the settings page. If that does not happen, try refreshing the page. + +:::note +All Base URL settings are to be entered without the leading slash. + +- Right: `tautulli` +- Wrong: `/tautulli` + +::: + +## General + +These settings are OK for most installations. + +| Setting | Description | +| -------- | --------------------------------------------------------------- | +| Hostname | The hostname or IP address of the host running Maintainerr | +| API key | Maintainerr's API key. It is currently reserved for future use. | + +## Media Server + +You need to configure one media server: Plex, Jellyfin, or Emby. Multiple media servers are not supported simultaneously. + +## Plex + +Plex can be used as your media server connection. + +When using a local Plex instance, make sure Plex's `Secure connections` network setting is set to `Preferred` instead of `Required`. + +Maintainerr's normal Plex setup uses Plex authentication and server discovery instead of a manual host/port form. + +After you authenticate with a Plex **admin** account, Maintainerr validates the token, loads the servers available to that account, and lets you choose from discovered connection candidates. This is the recommended setup because Maintainerr can use the discovered server details directly and keep automatic reconnection behavior enabled. + +:::tip +Proper DNS is preferred. Plex discovery and failover can depend on resolvable Plex endpoints, and Docker users in particular may run into intermittent connection or discovery problems when container DNS is unstable. If possible, make sure your environment has working DNS resolution for Plex-related hostnames and service names. +::: + +| Setting / Control | Description | +| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------- | +| Authentication | Authenticate with Plex using an **admin** account. Until this succeeds, the Plex server controls stay disabled. | +| Server | Shows the currently selected discovered server, or lets you choose one from the discovered server list. | +| Refresh icon | Re-runs Plex server discovery for the authenticated account. Use this if the server list is stale or discovery failed the first time. | + +:::tip +`Test Connection` is disabled until you are authenticated and have either selected a discovered server or enabled manual override with saved settings. +::: + +
+Server list is empty (VPS, cloud host, or custom networking) + +Maintainerr only lists Plex servers that publish a **reachable** connection to plex.tv. If authentication succeeds but the server dropdown stays empty, Plex is most likely publishing only a `local` connection that Maintainerr (running elsewhere) cannot use. This is common when Plex runs on a **VPS / cloud host** or behind unusual networking, where Plex's automatic Remote Access cannot detect a public connection. + +Fix it on the Plex side by publishing a reachable address: + +1. In Plex, open `Settings -> Network -> Custom server access URLs`. +2. Add a reachable **HTTPS** URL **including the port** — for example your server's `*.plex.direct` address: `https://..plex.direct:32400`. Using the `.plex.direct` host keeps a valid certificate; a reverse-proxied domain with its own valid certificate works too. You can usually copy the correct address from Seerr if that service is already connected to the same Plex server. +3. Save and restart Plex. (On some Docker images this setting is an environment variable instead — for example `PLEX_ADVERTISE_URL` on the hotio image.) + +Back in Maintainerr, press the **Refresh icon** next to the server selector — the server now appears in the list. + +:::tip +If Maintainerr and Plex share a Docker network, you can instead skip discovery and point Maintainerr at Plex's **internal** address (e.g. `http://plex:32400`) with manual connection override below. +::: + +
+ +
+Advanced: manual connection override + +Most users should leave this closed and use the normal Plex authentication and discovery flow. + +If discovery does not give you the connection you want, open `Advanced Settings` and enable `Manual connection override`. That lets you enter the hostname, port, and TLS mode directly. + +Manual mode is a fallback option: + +- Plex authentication is still required. +- It overrides the discovered Plex connection. +- It disables automatic reconnection for that Plex entry until you switch back. + +If you want Maintainerr to connect securely in manual mode, use your `*.plex.direct` URL as the hostname and enable TLS. You can usually copy the correct address from Seerr if that service is already connected to the same Plex server. + +
+ +## Jellyfin + +Jellyfin can also be used as your media server connection. + +| Setting | Description | +| ------------ | ---------------------------------------------------------------- | +| Jellyfin URL | The domain name or local IP address of the host running Jellyfin | +| API key | A Jellyfin API key generated from your Jellyfin server | +| Admin User | Test Connection to load the available admin users | + +## Streamystats + +:::note +Streamystats is only available for Jellyfin users +::: + +The separate `Settings -> Streamystats` page only appears when Jellyfin is the active media server. Maintainerr reuses your saved Jellyfin API key for authentication, so you only need to provide the Streamystats base URL. + +| Setting | Description | +| ------- | ----------------------------------------------------------------------------------------------------------------- | +| URL | The base URL of your Streamystats instance, such as `http://localhost:3000` or `https://streamystats.example.com` | + +## Emby + +Use your Emby server URL directly. Maintainerr supports either entering an API key manually or using `Sign in with Emby` to authenticate with an admin username and password and let Maintainerr populate the API key for you. Emby Connect is not supported because Maintainerr uses direct server authentication and does not implement Emby's cloud-based Connect flow. + +| Setting | Description | +| ---------- | -------------------------------------------------------------------------------------------------------------------------------------- | +| Emby URL | The domain name or local IP address of the host running Emby | +| API key | An Emby API key generated from `Dashboard -> Advanced -> API Keys`, or the token returned by `Sign in with Emby` | +| Admin User | Test Connection to load the available admin users, or use `Sign in with Emby` to populate the saved admin-user selection automatically | + +## Seerr + +Seerr configuration is required if you want to use Seerr-related rule parameters or remove Seerr requests. + +| Setting | Description | +| ------- | ------------------------------------------------------------- | +| URL | The domain name or local IP address of the host running Seerr | +| API key | The API key from Seerr settings | + +## Radarr + +Radarr's configuration is required to use its parameters in rules and to remove or unmonitor movies. + +| Setting | Description | +| -------------- | -------------------------------------------------------------- | +| Server Name | A friendly name to help identify the server | +| Hostname or IP | The domain name or local IP address of the host running Radarr | +| Port | The port Radarr runs on | +| Base URL | The URL base configured in Radarr, if one is set | +| API key | The API key from Radarr settings | + +## Sonarr + +Sonarr's configuration is required to use its parameters in rules and to remove or unmonitor shows. + +| Setting | Description | +| -------------- | -------------------------------------------------------------- | +| Server Name | A friendly name to help identify the server | +| Hostname or IP | The domain name or local IP address of the host running Sonarr | +| Port | The port Sonarr runs on | +| Base URL | The URL base configured in Sonarr, if one is set | +| API key | The API key from Sonarr settings | + +## Metadata + +Maintainerr has a separate `Settings -> Metadata` page for poster, backdrop, and metadata-provider settings used across the UI. + +This page is mainly useful when you want better artwork fallback, more reliable cross-provider ID resolution, or more control over which metadata source Maintainerr prefers. + +| Setting | Description | +| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| TMDB API key | Optional. If you leave this empty, Maintainerr uses its built-in shared TMDB key. Add your own key if you want an isolated quota or your own TMDB account access. | +| TVDB API key | Optional. Enables TVDB as an additional metadata source and fallback for ID cross-references. TVDB cannot be selected as primary until it is configured. | +| Primary | Chooses whether Maintainerr prefers TMDB or TVDB first when resolving posters, backdrops, and related metadata lookups. | +| Refresh metadata | Clears cached metadata for that provider and asks your media server to refresh matching items that already have provider IDs stored. | + +Typical usage: + +- Leave TMDB on its default setup if you just want Maintainerr to work out of the box. +- Add a TVDB key if you want another source for artwork and metadata cross-references. +- Switch the primary provider if you prefer one source's results over the other. +- Use `Refresh metadata` after changing provider settings, when testing a new provider, or when provider artwork and IDs look stale. + +The metadata refresh action runs in the background. It clears Maintainerr's cached provider responses first, then asks your configured media server to refresh items that are already linked to that metadata provider. + +In practice: + +- changing the API key or primary provider affects future metadata lookups +- `Refresh metadata` is the manual "re-check existing linked items" action +- refresh may take longer on larger libraries because Maintainerr asks the media server to refresh existing items that already have matching provider IDs + +## Tautulli + +:::note +Tautulli is only available for Plex users +::: + +Tautulli's configuration is required to use its parameters in rules. + +| Setting | Description | +| ------- | ---------------------------------------------------------------- | +| URL | The domain name or local IP address of the host running Tautulli | +| API key | The API key from Tautulli settings | From 8cce2140e6857bb943f33892e92c76305d56b312 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 8 Jun 2026 19:43:25 +0000 Subject: [PATCH 4/5] docs: revert versioned 3.14 configuration edits --- .../version-3.14.0/Configuration.md | 19 ------------------- 1 file changed, 19 deletions(-) diff --git a/versioned_docs/version-3.14.0/Configuration.md b/versioned_docs/version-3.14.0/Configuration.md index a6642e51..5fb37d0a 100644 --- a/versioned_docs/version-3.14.0/Configuration.md +++ b/versioned_docs/version-3.14.0/Configuration.md @@ -54,25 +54,6 @@ Proper DNS is preferred. Plex discovery and failover can depend on resolvable Pl `Test Connection` is disabled until you are authenticated and have either selected a discovered server or enabled manual override with saved settings. ::: -
-Server list is empty (VPS, cloud host, or custom networking) - -Maintainerr only lists Plex servers that publish a **reachable** connection to plex.tv. If authentication succeeds but the server dropdown stays empty, Plex is most likely publishing only a `local` connection that Maintainerr (running elsewhere) cannot use. This is common when Plex runs on a **VPS / cloud host** or behind unusual networking, where Plex's automatic Remote Access cannot detect a public connection. - -Fix it on the Plex side by publishing a reachable address: - -1. In Plex, open `Settings -> Network -> Custom server access URLs`. -2. Add a reachable **HTTPS** URL **including the port** — for example your server's `*.plex.direct` address: `https://..plex.direct:32400`. Using the `.plex.direct` host keeps a valid certificate; a reverse-proxied domain with its own valid certificate works too. You can usually copy the correct address from Seerr if that service is already connected to the same Plex server. -3. Save and restart Plex. (On some Docker images this setting is an environment variable instead — for example `PLEX_ADVERTISE_URL` on the hotio image.) - -Back in Maintainerr, press the **Refresh icon** next to the server selector — the server now appears in the list. - -:::tip -If Maintainerr and Plex share a Docker network, you can instead skip discovery and point Maintainerr at Plex's **internal** address (e.g. `http://plex:32400`) with manual connection override below. -::: - -
-
Advanced: manual connection override From 43d9b5563fc813dc8e8b0b5ef80794faae425ca0 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 8 Jun 2026 20:12:34 +0000 Subject: [PATCH 5/5] docs: refine Plex custom URL setup steps --- docs/Configuration.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/Configuration.md b/docs/Configuration.md index e6bd447e..efe6bbb3 100644 --- a/docs/Configuration.md +++ b/docs/Configuration.md @@ -61,9 +61,9 @@ Maintainerr only lists Plex servers that publish a **reachable** connection to p Fix it on the Plex side by publishing a reachable address: -1. In Plex, open `Settings -> Network -> Custom server access URLs`. -2. Add a reachable **HTTPS** URL **including the port** — for example your server's `*.plex.direct` address: `https://..plex.direct:32400`. Using the `.plex.direct` host keeps a valid certificate; a reverse-proxied domain with its own valid certificate works too. You can usually copy the correct address from Seerr if that service is already connected to the same Plex server. -3. Save and restart Plex. (On some Docker images this setting is an environment variable instead — for example `PLEX_ADVERTISE_URL` on the hotio image.) +1. In Plex Web, open `Settings → (your server) → Network` and click **Show Advanced** (top-right) to reveal `Custom server access URLs`. +2. Into that comma-separated field, add a reachable **HTTPS** URL — e.g. your server's `*.plex.direct` address: `https://..plex.direct:32400`. The `.plex.direct` host keeps a valid certificate (a reverse-proxied domain with its own cert works too). Including the port is recommended; otherwise Plex falls back to your Remote Access port. You can usually copy the correct address from Seerr if it's connected to the same Plex server. +3. Save and restart Plex. On some Docker images this setting is an environment variable instead — e.g. `PLEX_ADVERTISE_URL` on the hotio image — in which case set it there (the in-app field is managed by that variable). Back in Maintainerr, press the **Refresh icon** next to the server selector — the server now appears in the list.