Hi i have the wd my Cloud Home with 2 hdds.
I use plex with 300 movie, tv episodes and all my pics.
Since the last wd my Cloud Home Update my plex server is only available when I reboot the nas. Then it works for hours. After approx 24 hours the plex Server is not available. The wd nas it self is available and the wd app works just fine.
Then I need to Reboot and it back again.
Anyone has the same problem ? Any Tipps ?
Hi, I have the same problem, any tipps for resolve this situation?
Thanks
I have a WD MyCloudMirror Gen 2 and it always disappears. Called WD and they said it was a problem with AT&T Uverse router. Changed internet service to Spectrum and Nighthawk router and still have the same problem. Set a static IP and it still loses the connection. Only thing that works is to manually reboot the WD. Not realistic to do this every time I need it. Looking for a different NAS now. I don’t think it’s Plex because I can’t even find the WD device on my list of available IP’s.
I have a similar problem to the OP (Hendrik). I have a new My Cloud Home Duo and have been using it for about 2 weeks. I find that the plex server disappears almost every day.
To recover the server;
I access the plex server via laptop, phone and Apple TV.
When it works, the Plex system seems like a promising system, however the reliability issue making it difficult to love.
I’d appreciate knowing if this is a known issue and if it is being worked on, or if there is a configurational workaround?
Many thanks.
Yep, same here. According to my router logs, every 24hrs or so my MyCloud Home (McHome) requests an IP refresh. At the exact same time the Plex server on the McHome freezes.
I have my McHome connected to my router by cat5 cable.
Best work-around I’ve found is to physically disconnect & reconnect cat5 cable to McHome from the router. Plex becomes available again within 30secs.
No idea if it’s a Plex or WD software bug. Infuriating, though!
Had this problem myself for quite some time now. Reboot usually sorts it, but I’m getting to the point where I have to reboot every time I want to use Plex. During this time I’ve updated server app numerous times and even changed router, but the problem still remains.
I have WD PR2100 running latest firmware and latest version of Plex server. Would love a solution to this if anyone has one.
+1
Infuriating… as above.
Not much point investing €800 to get an always on Media server that needs physical intervention every 24 hours… Not fit for purpose…
I had this issue with my WD EX2 Ultra - I’ll double-check my settings and post them here as I’m no longer having this issue.
From memory I disabled auto-update and set a static IP address, I think there was an power saving mode that I disabled as well.
Checked my settings and I’ve picked out the ones that should be important:
General
Drive Sleep = Off
Power Schedule = Off
Network
IPv4 Network Mode = DHCP (I’ve reserved the address using my router instead of using static IP)
Firmware Update
Enable auto-update = On
Current version = 2.30.193
For info my current version of Plex is 11224929
Not the settings I thought but might help, let me know if you need more info.
I’m having the same issue on my PR2100.
I am not able to change the IPv4 Network Mode - it doesn’t show from the Dashboard. Is this something I’ll have to change on my router? I’ve setup port forwarding for my PMS through my router, but not sure if that matters.
I have a PR2100 and am having the same issue, although it seems I get almost a week out of it before it disappears. symptoms: 1. server goes to indirect mode and eventually becomes completely unavailable outside my home 2. tv shows stop recording after only a few seconds. Restarting the Plex server seems to briefly bring it back to life, but not for long. A complete reboot seems to fix it, temporarily, for several days. I’ve had this PR2100 about a month.
I don’t think it’s my ATT router since my previous setup, still running just fine, is a WD MyCloud EX2 as the NFS mounted storage and an Intel NUC running Linux as the Media Server and that combo has been rock solid for three to four years, including remote access. I was hoping to retire that setup but can’t until this PR2100 becomes stable.
Oh and the first time this happened, Plex got so corrupt I not only had to uninstall it, but had to SSH into the PR2100 and delete all the config files in order for the reinstall to work. Since then rebooting at least brings it back to life for a few.
Plex PR2100 Media Server 1.13.5.5291
MyCloud PR2100 firmware 2.30.193
both claim to be the newest as of this writing
oh and I forgot to mention, when this happens it seems to progressively get worse. first the server is in indirect mode outside my home, then it becomes unavailable outside my home, then it becomes unavailable inside my home. that’s when I really notice and have to reboot it.
Happened again. This is the second time it wouldn’t come back no matter how many reboots. Stopped, restarted the app, still no access.
Unstalled it, reinstalled it, still no go.
Had to SSH and remove all files. then tried again.
This time I tried using the native WD version of Plex to see if it was more stable. Worked okay but couldn’t give it enough time to see how long it would take to fail as I have shows to record. Also, the native WD app is so old it doesn’t even have Plex DVR.
I installed the new 1.13.5.5291 on top of the native WD app as a new wrinkle. if it’s still unstable I’ll wipe it too and start over fresh…again…
And it’s dead again. Guess I’ll have to uninstall, ssh to wipe the files, and try again.
It ran okay for a little while with the old PMS that WD had in its store. I installed the latest PMS on top of it and now it’s inaccessible again, even on my local network.
Starting to think that this latest server version from Plex, 1.13.5.5291 is not compatible with the PR2100.
Anyone else having these issues? WD won’t help since this isn’t their native app.
Okay, I think I’m close to figuring something out. I changed my ATT Uverse router to give a permanent reservation to the PR2100 and things have improved in one small way.
Now when the server becomes inaccessible outside my network, I only have to remote in to my home desktop PC and go to the web viewer for Plex, go to Server, and retry Remote Access, and it restores and goes green. Then everything works remotely again. I don’t have to reboot the PR2100 like I had to before.
Now why is this working better I don’t know. But changing the ATT router to a permanent reservation and having this improve makes me think that there’s some subtle incompatibility between the way the PR2100 handles DHCP and the way the ATT router does. Who is at fault I don’t know. But I do know that during none of this was NFS disrupted. My dekstop PC mounts the PR2100 by its IP address and that has never had an issue. So this problem seems to be specific to port 32400 that Plex uses, or maybe obscure non internet standard ports in general. I don’t know.
Next step is I’m going to turn off DHCP on the PR2100 and manually assign the same IP address and go from there. Perhaps taking ATT’s DHCP out of the equation will bypass whatever has been going wrong with port 32400?
Solved!
Setting the PR2100 to use a fixed IP address, and the maintaining the permanent reservation of that IP address in the ATT router so it doesn’t get handed out to anyone else has apparently fixed it.
I have full remote access a day later, which I didn’t have before.
I will post back here if anything changes, but for now this looks like it was an issue between the PR2100 and the ATT router regarding port 32400 and DHCP refreshes, and removing DHCP from the equation appears to have resolved it.
Now there’s a new PMS server update today. Hmm…
I spoke too soon. The fixed IP address is helping in that I don’t have to reboot the PR2100 to get access to PMS again. But it’s still dropping off remotely every day, and sometimes locally.
Just now it was unavailable outside my network, so I remoted in to my Linux desktop running my prior instance of Plex, and it couldn’t see PMS on the PR2100 either, on the LAN.
I went into the Web console for the PR2100, went to Apps, went to Plex, clicked Configure, and that forced PMS on the PR2100 to load in a browser. Once there I went into Settings, Server, Remote Access and forced a Retry. Pushing it from there brought it back to life again and access became available locally and remotely.
I’m now thinking something is up with the PR2100’s network driver and it’s dropping port 32400. I could be mistaken but I don’t see how the ATT router would be adversely affecting LAN access by intermittently blocking that port.
Still happening. Yep, this is the famed auto negotiation problem WD has with certain network equipment, especially ATT routers.
What’s strange is the supposed fix is to put a switch between the NAS and the router so that it will broker auto negotiation. There is already a switch between my NAS and the router.
As it stands right now I have to Retry or Re-enable Remote Connections in the PMS Server settings each morning to refresh the connection and re-open the port, for the day.
I’m going to put another switch between the PR2100 and that ‘backbone’ switch and see if another layer of auto negotiation fixes anything. More to come…
Hi, I have similar problems.
And now I tried to bootup my WD MyCloud Home once the plex is down again.
However, when I do so, all individual files can still be seen but all the libraries contents are gone. All that remains are the flesh startup scan results same as the 1st time when I started using Plex. (All the poster, names, everything)
Every time I have a connection problem, I reboot the NAS, and when plex is available again, all things are just gone again.
Is there even a way for us to backup the databases 1st, so that we can restore the processed data?
I just want the databases to stay the same without managing them all over again at everytime bootup
Anyone here have the same problem as me on My Home Cloud? here link to my post:
Syncronizations stars whenever i turn on my NAS .
Thanks
