The only way to work around this is to reboot the NAS device. I have started and stopped the service and it DOES NOT do anything. My experience with PLEX is getting worse and worse! 
is that the cost of growing too big too fast? PLEASE HELP!
When the basic stuff stops to work, then you question things.
Appreciate your detailed response! Thanks
RESPONSES BELOW
No, that is not a problem of growing too fast, it is often a lack of understanding of how Plex and networks work.
I could claim I have a good idea of how networks and NAS work. But how PLEX work - I would definitely not know!
The most obvious thing to check is your network and it’s settings.
Resp below
Are all of your devices on the same subnet?
YES
Have you rebooted the modem/router and everything connected to it, including any wireless devices?
NOPE
Do you have proper connection to the internet?
YEP 1GB up and 1GB Down - Fiber
Is Plex still running on the NAS when you lose contact with it?
YEP it is
Do you have a static IP address for your NAS or are you using DHCP Reservation?
Neither, I have 3 LAN Adapters that are connected to a Cisco Giga Switch.
Are you using a VPN?
NO
Do you have more than one router connected to your network?
NO
Have you added a lot of media recently?
NO
Have you checked your media files for damage? That can cause Plex to crash or become unresponsive in some circumstances.
Nope - How do I go about doing this? I had @ChuckPA say that for my photo’s which are ridiculously slow! I can write PowerShell Scripts, what am I checking for? just the extension is no good, I need to be able to look into the file for its checksum or something, and then also have a way to either delete/move/fix so they are all Clean…
Have you performed any drive maintenance and error checks on your NAS?
Yes every often Synology reminds me to Scrub the raid DB and I do it.
What NAS … make/model do you have?
What PC OS do you use, Windows, OS X or Linux?
Open Plex settings > server > help and click on the Download Logs button. Attach the .zip file to your post, thanks.
If you are unable to open Plex settings, then see the link and gather them manually. Please include ALL log files, thanks.
Not comfortable posting this information in a public forum. Are you PLEX employee? I can then PM you that info. Hope you understand.
Regarding @trumpy81 question:
Do you have a static IP address for your NAS or are you using DHCP Reservation?
Neither, I have 3 LAN Adapters that are connected to a Cisco Giga Switch.
His question was not answered.
How are LAN IP addresses assigned: DHCP or manually (static) assigned?
Do you have a static IP address for your NAS or are you using DHCP Reservation?
Neither! All the 3 lan adapters have dhcp addresses… they have been this way for years.
Does your Cisco switch have LACP and LAG?
I’d say neither, these switches are unmanaged switches and you cannot do advanced settings like creating VLAN’s, link aggregation, etc. Model SG100-16
https://www.cisco.com/c/en/us/support/switches/sg100-16-16-port-gigabit-switch/model.html#~tab-documents
http://www.excitingip.net/420/cisco-small-business-unmanaged-gigabit-network-switches/
oh no, I can see the problem from here…
I have the same issue, where sometimes it says Plex is unreachable, and I have to try a 2nd time or 3rd. I’ll throw this out there, I have Emby running on the same server and I never have an issue with Emby. I also noticed recently that when the latest version I am using (Version 1.9.6.4429 on FreeBSD 11.1-RELEASE) the login sequence has subtly changed. I always log into my Plex server using https://my-public-ip-address:32400/web. I have never used https://plex.tv. Anyway, I notice now with this version that if you login using public IP address, and watch the URL address bar, you will see that it momentarily changes to plex.tv and then back to public IP address. So, it seems to me, the issue with Plex is its connection back to mothership; it seems to get ‘stale’ and requires a 2nd or 3rd login attempt to wake it up. Emby does not have this, and I never have an issue logging into Emby.
@trumpy81 I removed the other 2 GB connections to the switch. Are you able to help me understand why this started becoming a problem only now? I have been running this setup since 2013 without any problems so it worked for about 4 years and in the last 2-3months it started having problems. I will keep you posted on how stable it is.
Thanks
@CrazyDiamond698 my access always uses the plex.tv link.
They are generally correct. Everything is good on my end and there can be some bottle neck in the process. Poorly configured router, your hardware, if your running it in a virutal machine. Have you tried baseline testing. Like deploy a test server, different machine, and wire everything. Sounds cheesy, but I’ve done stuff like this before and found out root causes such as not running a bridge on a VM that caused hit and misses on my server being up.
@trumpy81 said:
Like krishnaniyer, if you have multiple connections and they are not connected to a managed network switch with LACP and LAG, then that will be the source of your issue.
If that is not the case, then you need to look at other areas within your network. I can’t tell you what to look at because I have no idea what your setup looks like.
So why do I not have any issues with Emby then, if my network is the issue, which I know is not the issue. I have zero issues with any other programs/apps running on my network, only Plex login is failing. Emby is rock solid.
