Hi
Plex used to work fine but recently having trouble finding my library every 1-2 days (yellow triangle! next to it). After a restart its fine for a while, but after about a day eventually stops and needs restart.
Installed Emby is on same server and works fine. So, seems to be a Plex issue?
Have seen several similar posts on-line, but never seem to point to a discernable problem or fix.
I have posted the logs from both the server and Plex in case anyone can see anything. Plex Version 1.26.0.5715 Plex Synology Logs.zip (2.0 MB)
The log files are from Plex Media Server on Windows.
Apr 18, 2022 09:57:21.822 [7460] INFO - Plex Media Server v1.25.4.5487-648a8f9f9 - Microsoft PC x64 - build: windows-x86 windows - GMT -07:00
Apr 18, 2022 09:57:21.822 [7460] INFO - Windows version: 10.0 (Build 19044), language en-US
It seems problem is with networking or DNS. The server cannot resolve host names.
I am running Plex on Synology (where my libraries are), but the logs come from Plex and Synology on my PC browser. If there is something else I need, please let me know.
Anyway to resolve this? Why does the Network/NDS have a problem with Plex and not with Emby? Also, just FYI, when it has trouble finding my library it is the same across mobile, PC, and TV(hardwired).
Hi,
Hoping that someone can help out here. Seen this same problem on the forums before but seems that no one has solved it yet.
Any and all help greatly appreciated.
Thanks
gleiche seit ca 1 Monat bei mir auch - man wartet auf das Update und leider immer wieder unkontrolliertes Anhalten des Severs - der sich nicht wieder alleine Startet sondern manuell gestartet werden muss.
IT seems this bug was introduced around the 1.26 update in April/May time frame at least for DSM6. I used to run my nas 24/7 for months without any connection issues to plex then it started doing this randomly not finding server issue. I did recently once updating to 1.27 lose my server connection and had to “claim” my server again at about the 1yr mark of setting up the nas sort of like some “lease” ended for the initial setup. Now when I get this loss of connection to plex server I reboot my nas and it finds it ok no issues. I just updated to 1.27.0.5897 today but the release notes don’t say anything about this issue or other connection issues.
Now when I know I will be using plex, I just go ahead and reboot the nas beforehand so I know its ready to go when everybody sits down to watch a movie.
shouldnt the IP be set to 192.168.1.117? I dont believe .0. is even possible unless user has some really custom networking going on, Also this is a pretty old NAS.
One recommendation is that once plex player is set up initially, to bind the IP of server to config that way it doesnt have to “look” for the server it already connected to and claimed in the first place (not sure if you are already doing that). Highly unlikely that the local IP would change unless user sets up a new router or totally resets a router in which case you can handle with additional checks to continue PMS ip searching on the network as usual. It’s always recommended to bind the PMS ip on the router anyway so that it can’t ever change unless the user does one of the above manual changes. Might want to add that to the setup instructions for PMS.
Thanks!
Not using a VPN
Just updated to 1.27.0.5897, but will take a day or so to see if that helps.
Think your comments are to BigWheel, but my network interface is set to “any.” Have not set-up anything else.
0 as a third octet for a local IP range is pretty standard. Router brands will often use a 0 or a 1. Lots of people like myself change the third octet manually for a tad bit of security by way of obscurity.
@bus275 I do need to wait for someone that knows more about Synology than me to ask a few question but please let me know if the update helps
For good practice, you should login to your router and bind the IP or mac of your PMS to its ipv6 address ( in your case 192.168.0.117) and label that device. IIRC DSM also lets you do this through the UI web page in the networking tab of control center. I don’t think it’s related to your issue but will help rule out any future ip related issues especially if you set up remote connection to the pms.