09:22:48 INFO (SyncWorker_1) Connecting to Resource: 09:22:48 INFO (SyncWorker_1) Resource connection ERR (0s): 09:22:48 INFO (SyncWorker_1) Resource connection OK (2s): 09:22:48 INFO (SyncWorker_1) Resource connection OK (0s): 09:22:46 ERROR (Thread-5) : ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 09:22:46 ERROR (Thread-4) : ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 09:22:46 INFO (SyncWorker_1) Testing 4 resource connections. The Home Assistant instance has docker internal address 10.0.3.2:8123 and is exposed on my LAN with address 192.168.1.xx:327yy. I've a clean fresh installation of Home Assistant v0.107.7 as a docker container on a QNAP NAS (firmware version: 4. Link to integration documentation on our website:.Operating environment (Home Assistant/Supervised/Docker/venv): Docker.Last working Home Assistant Core release (if known):.

Home Assistant Core release with the issue: 0.107.7.Nevertheless, if I connect to Home assistant from 'inside' the docker network, the redirect to 10.0.3.2 is ok, but the authentication attempt fails (see logs). I would expect instead, after a successful Plex login, to be redirected to my Home Assistant instance LAN IP 192.168.1.xx (from which I started the process) and to successfully complete the Plex integration setup. Notice that on my Plex Server instance the new integration token appears correctly (so it is not a Plex login problem). So the integration process on Home Assistant stays waiting for a callback forever (see picture 05). I'm redirected to the docker internal IP (10.0.3.2, not visible from the LAN) and not to the HASS LAN IP I've started from (192.168.1.xx) - see picture 04, When I try to add a Plex Server integration from the Home assistant UI (see picture 01)Ī new window is opened to authenticate to Plex (see picture 02),īut after I authenticate on Plex (see picture 03),

Plex media server setup taking forever