I think it will work if you can tell your router that the 10Gbe subnet (192.168.11.0/24) can be reached using the unRAID IP (192.168.0.x)

Hi, I tried that by putting in the Gateway 192.168.0.10 (pfSense Router) you can see that on my first post but I still had the same issue.

never mind. i just remembered its impossible to do complex routing on a docker container.

your best bet is to put plex on br0 in bridge mode ( or custom network mode - but it can have its own can of worms...)

the port mapping settings might have been deleted/hidden away since you set it to host mode before

Can anyone else chime in with any suggestions please? 

 

I am not sure if this issue is fixable by adjusting a setting in Plex or unRAID as the two have worked together for quite a while before Plex started trying to use eth1 as well as eth0?

You may be suffering from an issue introduced with the 1.13.5.xxxx version of Plex.  They introduced the ability for the the Plex Media Server to bind to multiple network interfaces.  This has caused problems particularly with docker installations of Plex as it is confused by docker networking.

 

Your symptoms sound exactly like many are reporting (connections to server come and go, server disappearing in Plex).  Start reading here:

 

 

This is now in Plex Server Advanced settings: 

 

 

For some, the solution is to listen on all interfaces; for others, it is to specify a particular interface and for others it was to roll back to Plex Media Server version 1.13.2.xxxx before the change was introduced.

 

Here is the post that started the discussion and a reply from Plex about the issue:

 

 

Edited September 1, 20187 yr by Hoopster

Hi @Hoopster Many thanks for such a detailed post, it is really appreciated! 

 

I have already tried rolling back the version and specifying the Network interface with no success but there are a few other suggestions in that thread I will try tomorrow!

 

Many Thanks Again