Tried to do a Factory Restore - System Only from the Dashboard. When the Wd MyCloud has rebooted and I try to login through the dashboard it get stuck on “Reading configuration information…” I cant access it through SSH, propably cause the settings are restored. Same with Ftp… But I can access my shares with windows explorer. So the my wd is up and running. Just cant enter the dashboard after I did the system restore… Anybody have a solution for me I would be greatful.
I am using the correct ip adress… The dashboard login just stoip when it comes to reading configuration information…
I have tried a system restore with holding in the reset button in 40 secs when you put the power on, but I dont think Im doing it right. It just boots up as normal.
Try disconnecting the ethernet cable from the back of My Cloud, wait until the front light turns yellow, then plug the ethernet cable back into My Cloud. These actions might reset the web server software on My Cloud.
I faced with this problem when I was trying to install openVPN via SSH like “apt-get install openvpn”, due to some PHP5 packages were unable to update.
After that I was trying to fix packages installation via “apt-get -f install” and I was getting error
After I run again apt-get -f install and it succeed!
It asked to me resolve some php5.ini conflicts, so for PHP i overwritten it from update and for apache2 I kept original one
After I did reboot with command “reboot” I was able to login to dashboard!, only problem is that firmware version is now unavailable, during automative firmware update I am getting error get_firmware_info_500
Try closing the browser window and opening a new window and trying access again; I’ve found that the browser sometimes accesses a cached version of the page, and, getting no response from the MyCloud, just sits there showing ‘Reading configuration’.
Had the same problem. while it was hanging in “Reading configuration information” in the chrome browser, went and saw the console messages, it had error “Server returned error 403 forbidden”. For this error, just setup the userid properly in Windows credential manager. e.g. if user name was root then change to 192.168.1.20\root. That change did the trick and then i got to the logon screen