Wrong internal IP address reported by PLEX - QNAP. Plex not reachable.

Plex Media Server NAS & Devices
1

Have Plex installed and running on QNAP directly. Has been working swimmingly.

made network changes

Now Plex reports the wrong internal IP address of virtual switches… forever.

Yes, I have reviewed.
https://support.plex.tv/hc/en-us/articles/204059436-Finding-an-authentication-token-X-Plex-Token

I found my token. Indeed the first two entries are of the XML are the IP address that I do not want and are no longer active.

Things I have done to attempt to correct.

  1. Uninstalling and reinstalling Plex
  2. Generating a new token while PLEX as uninstalled
  3. Allowing the range of local IPs to connect without authentication
  4. Allow Fallback to Insecure Connections - On same network as server = failure

This is what the xml reports on plex.tv.

<Connection protocol="http" address="10.0.5.1" port="32400" uri="http://10.0.5.1:32400" local="1"/>
<Connection protocol="http" address="10.0.3.1" port="32400" uri="http://10.0.3.1:32400" local="1"/>
<Connection protocol="http" address="192.168.0.115" port="32400" uri="http://192.168.0.115:32400" local="1"/>
<Connection protocol="http" address="192.168.0.207" port="32400" uri="http://192.168.0.207:32400" local="1"/>

I am aware that I can browse to the plex directly via browser and play whatever. That is great, does not work for smart TVs built in apps!

Gui reports the IP address as 10.0.5.1.

Is there anyway possible to fix this as I cannot edit the xml directly at plex.tv?

Severely frustrated,
Brian

2

having the same problem…
Plex is picking the internal address from virtual switch which used for container / linux
station and not the right one…
Or there is an issue with openVPN server when enabled

3

I have to wonder if this is not related to the way the virtual switch is configured and mapped to your NICs.

4

I ended up removing (not disabling) linux station and container station.
i then restarted PLEX and was now picking right address…

5

@scurtis said:
I have to wonder if this is not related to the way the virtual switch is configured and mapped to your NICs.

if someone can explain how PLEX picks the IP , we can figure out why the wrong address was picked…

6

similar issues :smile:

I think we should post to this for feature request:

7

Thank you all for the replies. If only you had all replied 3 days ago lol!

I have this figured out, and you guys were on the right track. It is indeed 100% related to the virtual switches.

This type of bridged virtual switch configuration yields what we want.

This is what my XML looks like today!

For token reference.
https://support.plex.tv/hc/en-us/articles/204059436-Finding-an-authentication-token-X-Plex-Token

Connection protocol=“http” address=“192.168.0.115” port=“32400” uri=“http://192.168.0.115:32400” local=“1”/
Connection protocol=“http” address=“192.168.0.116” port=“32400” uri=“http://192.168.0.116:32400” local=“1”/
Connection protocol=“http” address=“X.X.X.X” port=“32400” uri=“http://X.X.X.X:32400” local=“0”/>

This root cause I believe is a two parter.

QNAP by default created the virtual switches in the bridged with virtual DHCP server for VMs when virtualization apps (Linux Station I think) were installed because static IPs on the QNAP interfaces were set. PLEX then detects this virtual switch IP and makes it as a local interface entry into their XML.

Plex needs to enable the owner of the account to specify what IPs are used in what order or disables IPs via the plex.tv website.

Now… This how to get out of this mode.

Connection protocol=“http” address=“10.0.5.1” port=“32400” uri=“http://10.0.5.1:32400” local=“1”/
Connection protocol=“http” address=“10.0.3.1” port=“32400” uri=“http://10.0.3.1:32400” local=“1”/
Connection protocol=“http” address=“192.168.0.115” port=“32400” uri=“http://192.168.0.115:32400” local=“1”/
Connection protocol=“http” address=“192.168.0.116” port=“32400” uri=“http://192.168.0.116:32400” local=“1”/

  1. Go to your router and DHCP reserve the IP addresses that you want for your QNAP interfaces.
  2. Set QNAP interfaces to DHCP.
  3. Keep PLEX online and enabled during this process.
  4. On QNAP, Shut down the Virtualization Station, Container Station and Linux Station.
  5. In QNAP go to Control Panel → Network & Virtual Switch. Edit all virtual switches listed in your XML to an unassigned or offline port on the QNAP. Deleting the switch straight up with a live connection has issues at times. Technically deleting them is possible, but I had issues.
  6. Once Switches are assigned to down ports, delete the switches.
  7. Go to https://plex.tv/api/resources?X-Plex-Token=YOURTOKENHERE and it should be resolved.
  8. Create a virtual switch bridged and select the live port and VM adapters.
  9. Restart Virtualization Station, Container Station and Linux Station

This process varies between 4.2 and 4.3 instances if you are using Virtualization Station. You specify in virtualization station which interface to use.

In 4.3 you can do everything via Control Panel → Network & Virtual Switch.

Essentially what you are doing is re-configuring QNAP interfaces so PLEX detects the prefered IP first in their XML. You can refresh your token view page at anytime during this and watch PLEX move the order of IPs around.

Full disclosure, I know how to fix it in both as I upgraded from 4.2 to 4.3 hoping for a solution as I use VMs and Plex from the QNAP. The PLEX app situation was not good in 4.3 due to the trouble shooting I went through to figure this out. I rolled the QNAP back to 4.2 from 4.3 which btw is a bad idea. Deployed the nuke and factory re-inited the entire TVS-882 at 4.2.X and re-installed everything from the ground up.

Hope this helps some of you.

Not taking the wrong IP for an answer,
Brian

1 Like
8

btw…

You can make this work if you are truly dead set on it or if you cannot get a DHCP reservation

Connection protocol=“http” address=“10.0.5.1” port=“32400” uri=“http://10.0.5.1:32400” local=“1”/
Connection protocol=“http” address=“10.0.3.1” port=“32400” uri=“http://10.0.3.1:32400” local=“1”/
Connection protocol=“http” address=“192.168.0.115” port=“32400” uri=“http://192.168.0.115:32400” local=“1”/
Connection protocol=“http” address=“192.168.0.116” port=“32400” uri=“http://192.168.0.116:32400” local=“1”/

Follow the steps.

  1. Keep PLEX online and enabled during this process.
  2. On QNAP, Shut down the Virtualization Station, Container Station and Linux Station.
  3. In QNAP go to Control Panel → Network & Virtual Switch. Edit all virtual switches to an unassigned or offline port on the QNAP. Deleting the switch straight up with a live connection has issues at times. Technically deleting them is possible, but I had issues.
  4. Once Switches are assigned to down ports, delete the switches.
  5. Go to https://plex.tv/api/resources?X-Plex-Token=YOURTOKENHERE and it should be resolved.
  1. Create a virtual switch with DHCP running on it, just like the ones you deleted and associate them with live adapaters.
  1. Restart Virtualization Station, Container Station and Linux Station

Your XML will end up looking something like this

Connection protocol=“http” address=“192.168.0.115” port=“32400” uri=“http://192.168.0.115:32400” local=“1”/
Connection protocol=“http” address=“192.168.0.216” port=“32400” uri=“http://192.168.0.116:32400” local=“1”/
Connection protocol=“http” address=“10.0.5.1” port=“32400” uri=“http://10.0.5.1:32400” local=“1”/
Connection protocol=“http” address=“10.0.3.1” port=“32400” uri=“http://10.0.3.1:32400” local=“1”/

9

@m0raca said:
Deployed the nuke and factory re-inited the entire TVS-882 at 4.2.X and re-installed everything from the ground up.

ouch!! … i was that close on doing the same…
thanks for the detailed explanation and we can start pointing questions to this answer :smile: … great job!

10

Had the same problem, solved now following m0raca procedure. Thank you so much.

11

Hi, after reboot the Plex changes back to the wrong adapter?
Did anyone resolve that?

12

PMS 1.13.5 allows you to select which adapter / IP PMS listens and responds to.

Settings - Network - Show Advanced

1 Like
13

wow great!
I never thoght they would enable this, so I never checked the settings again.

Thanks!