After updating mycloud firmware WD sync is showing “mycloud is missing”! I tried removing and re-adding sync folder to WD sync but it did not solve the problem.
The uninstall/install does work-BUT only for a little while.
I have had WDSync for a while now and it keeps getting stuck in “mycloud is missing”.
It would be nice to have a permanent fix for this.
It becomes somewhat tedious having to keep unistalling/installing WDSync.
Do what some others have done. Uninstall WD Sync, clean up any folders it’s uninstaller fails to remove, then use a third party sync program like Free File Sync (http://www.freefilesync.org/). The downside to third party sync programs is the inability to sync to the My Cloud from a remote location.
If installing Free File Sync make sure to reach each installer screen carefully and uncheck the extra programs (from OpenCandy) it may ask to install.
Has anyone ever heard back from Support on how to fix this problem, or if they are going to fix this. I have plans for this device, but only if it can do the remove sync they claim it can do… So far it is just gathering dust not working.
I get the same, it is setup with a static ip, but over the last 3 weeks I keep getting the “device is missing” message. I have rebooted my pc with no effect, rebooted my rooter, with no effect.
The only way to get it working again is to do the 4 sec reset.
But then it connects and starts to sync, but then it is missing again for about 10 minutes then starts to sync again, then missing again.
This message means that your internal or upstream DNS servers cannot resolve the unique ID of your My Cloud.
BTW: I would suggest to delete the picture
After using WDSync for months, a few days ago the “MyCloud is missing” error occurred. Read through the many helpful posts and tried fixes such as uninstalling / reinstalling WDSync, with no success. Remove the MyCloud device and then could not add it back. Changed network settings to use Google public DNS servers. New error message from WDSync: “The remote name could not be resolved.”
Thanks for any pointers to fixing this one.
Try these steps to see which hostname can’t resolve.
Normally it’s the My Cloud unique name
My Cloud Unique ID
Obtain the My Cloud device’s Unique ID using the My Cloud device’s IP address. The Unique ID will be used to validate remote access from the remote location.
Open a web browser
Enter the IP Address of the My Cloud device preceded by https://
Open the browser to the online DNS Lookup Tool DNS Lookup Tool - DNS Tools - MxToolbox or open a command prompt on the computer being used for remote access and check name resolution and traceroute to the following online resources Failure of DNS lookup can result in failed remote access to the My Cloud device.
nslookup mycloud.com
nslookup www.wd2go.com
nslookup discovery.wd2go.com
nslookup wd.com
nslookup device1234567-12345678.wd2go.com
nslookup device1234567-12345678-local.wd2go.com
tracert (Windows) or traceroute (macOS) mycloud.com
tracert (Windows) or traceroute (macOS) wd.com
tracert (Windows) or traceroute (macOS) discovery.wd2go.com
tracert (Windows) or traceroute (macOS) device1234567-12345678.wd2go.com
tracert (Windows) or traceroute (macOS) device1234567-12345678-local.wd2go.com
The nslookup and tracert commands all executed without error or complaint.
The nslookup returned a lot of cdns01.comcast.net answers
After posting my question, I messed around with the network settings using
the Dashboard. Tried static, and then went back to using DNS. No longer
getting the “remote name cannot resolved” error, now back to the “unable to
connect to the remote server” error.