Plex errors after 0.113 update

Configuration
1

After updating to HA 0.113 I’m seeing these errors in the log. I have Plex setup and working fine, but the IP address in the error is not even part of my network which is on a totally different subnet 192.168.10.x

Any ideas ?

Logger: plexapi
Source: /usr/local/lib/python3.8/site-packages/plexapi/myplex.py:1281
First occurred: 22:13:31 (2 occurrences)
Last logged: 22:13:31

http://192.168.1.5:32500: HTTPConnectionPool(host='192.168.1.5', port=32500): Max retries exceeded with url: /resources (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x694ae130>, 'Connection to 192.168.1.5 timed out. (connect timeout=3)'))
http://192.168.1.5:32500: HTTPConnectionPool(host='192.168.1.5', port=32500): Max retries exceeded with url: /resources (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x68477898>, 'Connection to 192.168.1.5 timed out. (connect timeout=3)'))

HA 0.113.0
HassOS 4.11
Supervisor 229
Raspberry Pi 3B+

2

There’s a new way to discover controllable Plex clients that gets the client IP address from plex.tv and tries to connect to it. There must be a client linked to your account with that local IP.

3

Ok, so there could be a client on a remote system with this IP eg. my mum’s house, but it would connect to my server via the public IP address of my mum’s router., so still don’ understand why the discovery service would try and contact a server on a private IP address not in the same address range as the server.

I have a bunch of other clients connected remotely and it looks like the discovery service doesn’t try to contact them…

4

This is HA attempting to connect to the client to enable media_player controls (play/seek/play specific media/etc). Could this remote client be logged into Plex under your account while other users have their own login?

5

I have just one Plex account (mine) plus two managed users which can be selected once logged in under the main account. So, every instance is logged onto the main account.

All the IP addresses it tries to contact are in the 192.168.x.x range i.e. private IP’s. The local network where the Plex server is located is on 192.168.10.x/24 so these must be remote instances on other private networks, so it makes no sense for the server to try and contact them. A simple host lookup for the IPs it’s trying to contact would return NXDOMAIN.

6

I see you created an issue on github (thanks!), let’s continue there.