From 5f138608cfe9de8290fa39fbb0758a5d2688a94d Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Wed, 1 Dec 2021 07:32:37 +0100 Subject: [PATCH] Clarify Plex needs login as administrator (#20526) --- source/_integrations/plex.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/plex.markdown b/source/_integrations/plex.markdown index 8e9343bfeed..82867e5dd89 100644 --- a/source/_integrations/plex.markdown +++ b/source/_integrations/plex.markdown @@ -30,7 +30,7 @@ If a Plex server has been claimed by a Plex account via the [claim interface](ht {% include integrations/config_flow.md %} -During setup, the integration will check all possible ways to connect to your Plex server(s) - i.e., local or public addresses, HTTP or HTTPS, by IP or using a subdomain of `plex.direct`, or by using a Plex relay if all other methods fail. The integration will prefer local over public and secure over insecure, in that order. The selected address is shown on the Plex card on the Integrations page. +During setup, you will need to log in as a server administrator. The integration will check all possible ways to connect to your Plex server(s) - i.e., local or public addresses, HTTP or HTTPS, by IP or using a subdomain of `plex.direct`, or by using a Plex relay if all other methods fail. The integration will prefer local over public and secure over insecure, in that order. The selected address is shown on the Plex card on the Integrations page. If your router enforces DNS rebind protection, connections to the local `plex.direct` hostname may fail (see [Plex documentation](https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/#dnsrebinding)). To avoid this, configure your router to allow DNS rebinding for `plex.direct` by following the instructions in the documentation link.