August 30, 20187 yr Hi, I am having some issues with any Plex docker showing connection timeouts & taking an hour plus to be accessible. I noticed this entry in my Plex Server Logs Replacing an old server at index 3 and address 192.168.0.33 (we just got packet from 192.168.11.33, index 2)Aug 30, 2018 09:55:54.337 [0x14f339bff700] DEBUG - NetworkServiceBrowser: SERVER updated: 192.168.11.33 (SERVER1)Aug 30, 2018 09:55:54.337 [0x14f339bff700] DEBUG - Notifying the system bundle an update to server /system/notify/serverUpdated?host=192.168.11.33Aug 30, 2018 09:55:54.337 [0x14f339bff700] DEBUG - [com.plexapp.system] Sending command over HTTP (GET): /system/notify/serverUpdated?host=192.168.11.33Aug 30, 2018 09:55:54.337 [0x14f339bff700] DEBUG - HTTP requesting GET http://127.0.0.1:40197/system/notify/serverUpdated?host=192.168.11.33 Now my confiuguration is as follows eth0 (Local LAN) 192.168.0.* eth1 (10Gbe between Main Desktop & unRAID) below are screenshots of my network config in unRAID, can anyone see anything that could be causing this please?
August 30, 20187 yr Your default gateway on interface eth1 must be in the same subnet as the interface, e.g. default gateway = 192.168.11.10 Your router must be configured with this additional IP address, and is the device which routes(!) traffic between the two subnets 192.168.0.x and 192.168.11.x
August 30, 20187 yr If eth1 is a direct 10GB link with your desktop, then there is no gateway on that interface. so keep the gateway entry blank.
August 30, 20187 yr Author Thanks Ken, I have removed that now but it seems that the problems could be Plex's own, I have downgraded to an older version and looking good so far!
August 30, 20187 yr Author 2 hours ago, bonienl said: Your default gateway on interface eth1 must be in the same subnet as the interface, e.g. default gateway = 192.168.11.10 Your router must be configured with this additional IP address, and is the device which routes(!) traffic between the two subnets 192.168.0.x and 192.168.11.x Thankyou!
August 30, 20187 yr Author Still having a nightmare with this.. made the changes as mention and still getting all these timeout errors. Plex keeps oming online, going offline, server settings are sometimes available in Plex most of the time I get "Server Settings Are Unavailable" so frustrating! I don't know why Plex is looking at 192.168.11.33? My Server is in host mode running on 192.168.0.33 DEBUG - NetworkService: Browsing on interface 192.168.11.33 on broadcast address 192.168.11.255 (index: 2) Aug 30, 2018 13:40:23.660 [0x151a443ff700] DEBUG - NetworkService: Browsing on interface 172.17.0.1 on broadcast address 172.17.255.255 (index: 3) Aug 30, 2018 13:40:23.660 [0x151a443ff700] DEBUG - NetworkService: Network change for browser (polled=1), closing 0 browse sockets. Aug 30, 2018 13:40:23.660 [0x151a443ff700] DEBUG - NetworkService: Browsing on interface 127.0.0.1 on broadcast address 127.255.255.255 (index: 0) Aug 30, 2018 13:40:23.661 [0x151a443ff700] DEBUG - NetworkService: Browsing on interface 192.168.0.33 on broadcast address 192.168.0.255 (index: 1) Aug 30, 2018 13:40:23.661 [0x151a443ff700] DEBUG - NetworkService: Browsing on interface 192.168.11.33 on broadcast address 192.168.11.255 (index: 2) Aug 30, 2018 13:40:23.661 [0x151a443ff700] DEBUG - NetworkService: Browsing on interface 172.17.0.1 on broadcast address 172.17.255.255 (index: 3) Aug 30, 2018 13:40:23.661 [0x151a443ff700] DEBUG - NetworkService: Network change for browser (polled=0), closing 0 browse sockets. Aug 30, 2018 13:40:23.661 [0x151a443ff700] DEBUG - NetworkService: Setting up multicast listener on 0.0.0.0:1901 (outbound: 0) Aug 30, 2018 13:40:23.661 [0x151a443ff700] DEBUG - NetworkService: Browsing on interface 192.168.0.33 on broadcast address 239.255.255.250 (index: 0) Aug 30, 2018 13:40:23.661 [0x151a443ff700] DEBUG - NetworkService: Browsing on interface 192.168.11.33 on broadcast address 239.255.255.250 (index: 1) Aug 30, 2018 13:40:23.661 [0x151a443ff700] DEBUG - NetworkService: Browsing on interface 172.17.0.1 on broadcast address 239.255.255.250 (index: 2) Aug 30, 2018 13:40:23.670 [0x151a443ff700] DEBUG - NetworkServiceBrowser: SERVER arrived: 127.0.0.1 (SERVER1) Aug 30, 2018 13:40:23.670 [0x151a443ff700]
August 30, 20187 yr Author OK, I have resorted to pulling my 10Gbe card and Plex is now back to normal! Lightning Fast and no connection timeout errors! Can anyone please help me as to why I cannot have this card installed anymore without interfering with Plex? they have worked together for months and the 10Gbe card has nothing to do with Plex!
August 30, 20187 yr 7 minutes ago, mbc0 said: OK, I have resorted to pulling my 10Gbe card and Plex is now back to normal! Lightning Fast and no connection timeout errors! Can anyone please help me as to why I cannot have this card installed anymore without interfering with Plex? they have worked together for months and the 10Gbe card has nothing to do with Plex! how is plex installed via docker or plug-in, post that config. Edited August 30, 20187 yr by ijuarez engrish
August 30, 20187 yr Author Hi I have tried BinHex, LinuxServerio & Now Plex (Official) Dockers (Which I am running now. These configs are with the 10Gbe Card removed and everything running as it used to!
August 30, 20187 yr Author Have restarted & updated the Plex Docker 4 times now and every time Plex is instantly back up and running! (this was taking over an hour each time and even then would be intermittant) so removing the card has 100% fixed the issue BUT as I said previously this card has been installed for a while now without issue, something must have changed (probably me!) that caused Plex to start seeing the other network?
August 30, 20187 yr from the original post it looks like it started on the 192.168.11.XXX network (10Gb), even tho it was set to host mode which means it should have been on the 192.168.0.33:32400/web. What i would do, shutdown plex delete the docker, then via command line go and rm -r the folder in the in apps folder and any other folder that has plex stuff in it just to make sure nothing is hanging. Then install your card make sure it works and then try again. I prefer LSIO but stick what you want to.
August 30, 20187 yr Author Hi, Thanks for the response, if I remove the appdata folder I would lose everything! I need to keep years and years of watched status and a custom library of Motorsport which has again taken years and years to organize (custom cover art etc) is there no other way? I have had the same issue whilst trying 3 different Plex Dockers. I am thinking the issue is more likely to be the network config in unRAID? (Hoping!!) Edited August 30, 20187 yr by mbc0
August 30, 20187 yr The card by itself should not introduces problems with Plex. You can re-insert the card and in the network settings assign NO IP address. This ensures it will not actively participate in the network. At this point Plex should still be as happy as before.
August 30, 20187 yr you can save your watched content, there a post here somewhere where it explains it or search Plex FAQ's. Save it to different location and then spin up the docker test i had similar problem ( don't have the 10gb) but plex keeping error out. pull my hair finally went deleted the config folders and boom its started to work. I can only assume something was hung up.
August 30, 20187 yr Author Just now, bonienl said: The card by itself should not introduces problems with Plex. You can re-insert the card and in the network settings assign NO IP address. This ensures it will not actively participate in the network. At this point Plex should still be as happy as before. Thanks for this, if I do not assign an IP address how would I map drives to my PC to ensure they are using the card? currently I map network drives to my Desktop using //192.168.11.33/Movies etc
August 30, 20187 yr 2 minutes ago, mbc0 said: Thanks for this, if I do not assign an IP address how would I map drives to my PC to ensure they are using the card? currently I map network drives to my Desktop using //192.168.11.33/Movies etc hold up, im confused, so you are using the 10Gb connection to map drives from your unraid to your pc so you can watch plex? or copy data to unraid so plex can index it?
August 30, 20187 yr Author Hi, I purely use the 10gb card eth1 to map drives for faster transfer to and from my Desktop PC I use standard 1GB LAN for the rest of the network Does that make sense?
August 30, 20187 yr 41 minutes ago, mbc0 said: Thanks for this, if I do not assign an IP address how would I map drives to my PC to ensure they are using the card? currently I map network drives to my Desktop using //192.168.11.33/Movies etc This is only the initial step to verify the card is working without interference. Based on your your last explanation. You need to set a subnet on the card and NO default gateway. This subnet allows direct communication between your server and your PC (which needs another IP address in the same subnet).
August 30, 20187 yr Author Right, I put the card back and first tried to let it generate its own IP (set it to Automatic) and the same Plex problems returned. I then tried setting the IP to None and then Plex reports no IP?? so it is relying on the card (when installed) even though the docker is in host mode. There must be a setting somewhere in Plex for this? Also, what is docker0? Edited August 30, 20187 yr by mbc0
August 30, 20187 yr Make sure your new card is NOT set as eth0. See settings -> Network Settings -> Interface Rules
August 30, 20187 yr Author 1 hour ago, bonienl said: Make sure your new card is NOT set as eth0. See settings -> Network Settings -> Interface Rules Hi, no it is not? cannot find interface rules but if you check my first post you can see screenshots of my network settings
August 30, 20187 yr If you are setting the Plex container to host mode, it will be able to see both interfaces. and since I don't use Plex, I don't know if it can properly work with both interfaces. Personally, I would set the Plex container in either bridge mode (and port map) which implies eth0 usage or a custom docker network on eth0, which however prevents unRAID and other bridge/host mode containers from talking to it. Then, Plex would be available on the unRAID IP, which you should be using on your PC to access (rather than the 10Gbe one) This is based on your comment that the direct 10GBe connection is purely for uploading/management of the unRAID shares
August 31, 20187 yr Author Hi, I tried bridge mode a few days ago but could find no way of mapping the ports?
August 31, 20187 yr Author I am wondering if I setup the Plex Docker to Custom br1 (10Gbe Card) is there any way I can get internet to that connection? Currently the 10Gbe Card is a single connection between my Desktop and unRAID server with no internet access. I cannot find a way to make it work in Bridge mode as I cannot find a way to port map? Thanks for all your help guys 🙂
Archived
This topic is now archived and is closed to further replies.