Finally on to something ! So If i setup plex from scratch (1.13.9) and disable external access I have zero problems. As soon as external access is enabled all of the connection issues start again. The web interface is showing a direct connection not indirect either.
I normally have a port forward setup in my router and I have UPnP turned off for security reasons.
If the web interface EVER shows Indirect, that means your Web client cannot see your server, even though itās on the same LAN. (FIREWALL issue or LAN subnet every time)
That seems to be the case. I just need to narrow it down. Itās still very odd that if it is really a firewall or subnet issue that one version of PMS would work and not the other. None the less I am closing in on the issue.
Thanks for all the help so far!
1.13.5 changed a whole bunch of other things.
Iām willing to bet your Synology has multiple ethernet adapters and youāve got more than one hooked up?
If so, thatās why.
Bottom line is: As of 1.13.5, it got more confused than less confused.
Now there is 1.13.9 which is supposed to be a step in the right direction.
Correct, right now I have a port bond hooked up. I even set the bond as the preferred NIC in the plex settings. I will try disabling the bond again removing all other cables and specifying the nic.
Thank you for your help Chuck!
I have the same issue - only resolved by downgrading to 1.13.4.
Been reading this thread
Mine is also a 916+
However - Only 1 NIC cabled & no bond - any more suggestions?
Many Thanks in advance
Scratch thatā¦after a number of hours itās loosing connection again. That is over 1 nic too. Reverted back to 1.13.4 for the time being.
When you had 1.13.9 installed did you try disabling remote access to see if that made a difference? For whatever reason turning remote access off fixed the server not found issue for me. The problem is that I need that enabled so I ended up reverting back.
I need the remote access as well - if i get a couple of minutes , ill reinstall 1.13.9 & test
The vast majority of Remote Access problems is rooted in what appers to be a major outage at Plex.tv
The operations team isnāt available yet to investigate, confirm, and correct.
Currently 1.13.9.5439 is working with remote accessā¦ 24 hours so farā¦
Well I am out of ideasā¦
nothing i can do until that team returns.
The plex.tv remote access issue was fixed on October 14 at about 8am GMT which affected a number of regions. If there are still issues, server logs would be needed with debug logging enabled and for the logs to be captured after loading the server remote access settings page and after doing an F5 Browser refresh on that page
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
When remote access is enabled I will still intermittently loose access to my server even when connecting via local IP.
With remote access disabled everything locally has been working perfectly fine for the past 48hrs.
Will try and get logs when I loose accessā¦
The change of subject caused me to lose track of the thread. I am now having problems again (1.13.4), but after catching up with the posts, I am suspecting it may be related to the plex.tv issue. Going to try getting things working long enough to disable remote (temporarily as I need it).
There was a regression in 1.13.3 that was fixed in 1.13.8 that related to remote access - so unless there is a specific reason for being on 1.13.4, I would suggest trying 1.13.8 or beta 1.13.9
@sa2000 The reason I am on 1.13.4 is because of the issues described above (by me) with 1.13.7. I dropped to 1.13.5 for a while and then started to have issues again and dropped to 1.13.4. This release had been fine up to a few days ago.
Since my post a short while ago, I was finally able to disable remote. It kept hanging during that process. I found that disabling a different (older) PMS on my network seemed to help and I was finally able to disable remote. Once that occured, things started to work normally again. Now I canāt say for sure that it was the disabling of the Remote or the disabling of the other PMS was the step that got me going again for sure. I have now re-enabled remote and I am still working (internally and externally). Perhaps the 2nd active PMS was confusing things somewhere.
I am going to keep that other PMS offline for a couple of days and if nothing bad occurs during that period, I will re-enable it and see if something breaks at that point.
Circling back to the 1.13.7 release, I did (as documented above) see that it was trying to use the NIC2 (which is not connected) 169.x.x.x address and then flapping back to the NIC IP address. So I suspect that the issue in .7 and .5, while similar in symptom are different in the exact cause (or so a surmise from the log entries that appeared in one version and not the other).
@ChuckPa remember from my earlier comment that the Synology is not capable of disabling NIC2. So it does always appear active with a 169.x.x.x address if set to DHCP, regardles of whether a cable is connected to it or not.
Sounds like the exact issue I am having. Two things I know for sure. Also I have a single PMS instance.
-Disabling remote access fixes my issues on 1.13.9
-Rolling back to 1.13.4 allows for remote access to work again
