Further to my previous reply, I think I’ve found something that could be a bug.
In my case, I migrated Plex from an old physical machine to a VM. I copied over all my plex data and started the services.
My internal connections are not working, so I did some troubleshooting like signing out of the server, stopping services, starting it, signing in, etc. to no avail.
Then, I decided to inspect https://plex.tv/pms/resources.xml and discovered this - it still thinks I’m using my OLD internal IP address.
Again, this is after multiple stops/starts/sign-in/sign-outs. Why is it hanging on to that old IP? If you’re ignoring v* interfaces, how do I tell your backend about my new internal IP? How do I select which interface I wish for it to report?
Ignoring v* interfaces seems incredibly wrong-minded.
<MediaContainer size="4">
<Device name="Owl" product="Plex Media Server" productVersion="1.14.1.5488-cc260c476" platform="FreeBSD" platformVersion="12.0-RELEASE (FreeBSD 12.0-RELEASE r341666 GENERIC)" device="PC" clientIdentifier="e6f6fdceaaf815edc7667013f699e61a7a25accb" createdAt="1517289960" lastSeenAt="1547518501" provides="server" owned="1" accessToken="privatekeyhere" publicAddress="50.71.248.76" httpsRequired="1" synced="0" relay="1" publicAddressMatches="1" presence="1">
<Connection protocol="https" address="192.168.0.22" port="32400" uri="https://192-168-0-22.ecf1ecb9d1fd4c73a20255610fea1407.plex.direct:32400" local="1"/>
<Connection protocol="https" address="50.71.248.76" port="24400" uri="https://50-71-248-76.ecf1ecb9d1fd4c73a20255610fea1407.plex.direct:24400" local="0"/>
</Device>
.
.
.
</MediaContainer>
