Dashboard login unavailable - fix?


I bought a 1TB MyCloud device
I created a share and checked it was accessible then upgraded the firmware as the device said there was a new firmware.

Bad move I can no longer access the dashboard. :disappointed:

So I did the simple reset but no joy still cannot access ::frowning:

I then did the 40second one which was slightly more productive. :persevere:

I could get access to the dashboard, but was presented with a modal windows with Initialising on it.
Waited 15 minutes and did an F5 refresh - can’t access page. Port scan shows port 80 not listening. :confounded:

Then I repeated the process and got a bit further using 2 web browsers
The main one still had the initializing windows that couldn’t be closed
The second browser tab was more usable but not much.
I could click most things but setting SSH, or a static IP gave me a check connection error.
It seems I couldn’t make any changes as the hardware would not send/receive commands.
Cannot upgrade firmware from the web front end :angry:

So while I can use twonky and see the shares I cant access the web to set a static IP and add users and such like now.

I’m told there’s a fix using a linux distro and hooking up as an external so if anyone can point me at it I’d appreciate it


If your My Cloud rebooted after the firmware update then the URL has probably changed. You will need to take a look at your network devices and under storage do a right click on WD My Cloud, look at Properties and see what URL is showing. Be sure to write that down and then do a right click on the Dashboard icon and see if the URL’s are the same, if not change the Dashboard URL. After that you should be able to open the Dashboard again.


By URL, I presume you mean the IP has changed and therefor the URL is differnet?

The device was on DHCP. A standard lease is 24 hours.
The upgrade took about 20 minutes - why would it be given a different address.

Anyway, it hasn’t got a different IP. It’s the same.as previous.

And as I mentioned - the website is available - if only for for a while.
The shares are accessible - by IP not name.
Twonky website config is available - again by IP
Unit pings fine by IP and name.
So just to reiterate the IP hasn’t changed
The device refuses to respond on port 80 after the “initializing” (white led) has finished and it’s settled on the Blue LED.

The bloke that sold it says this can be fixed with a hookup to a Linux box.
That’s the fix I’m after.

When one upgrades the firmware on the My Cloud, the My Cloud will reboot when the upgrade is finished. Upon reboot, in certain instances, the network DHCP Server may issues the My Cloud a new (and different) IP Address if the My Cloud is configured to obtain the IP Address from a DHCP Server and that server is not configured to reserve a specific IP Address for the My Cloud.

To the general issue you are having, have you rebooted the computer? Sometimes that may solve network issues. Other times rebooting the network router may solve network issues.

If using Windows 10, make sure to update Windows 10 with all the latest Microsoft updates. There was a recent update by Microsoft to fix one particular issue with Windows 10 that was introduced last November that prevented proper access to the My Cloud.

Try this link out if you are just trying to open up the Dashboard.


Once an IP is offered and accepted the , a DHCP server should always respond to a DHCPdiscover request with a DHCPOffer with the same IP information. This should be the case for both a new IP request and a renewal request.

This might not be the case if

The DHCP server was rebooted losing it’s record of assigned IP
The IP lease was deliberately removed.
Something else is brought to the network with that specific address as a static IP
The MAC address was changed.

However, this is a moot point.
The IP was exactly the same pre & post upgrade.
Plus I’ve also tested this on 2 separate networks with differing IP ranges and the issue remains.

Let me re-iterate
While it is initialising the web-page is partially accessible via htp:// forwards to htp://
It is also available by htp://wdmycloud which forwards to htp://wdmycloud/ui. I say Partially accessible in that I can see everything but I cant do anything unless I have 2 browser tabs open due to a modal window saying “Initialising”. However with a 2nd browser tab, I can access much of the controls - they are clickable but I cannot get any config changes uploaded. Will not accept a firmware upgrade, cannot apply a new device name, cant set a static ip, will not accept a reset, cannot enable FTP or SSH.

Once the machine is fully up & running it does not display the web page.
Usual windows error

The shares are accessible - both by name and by IP.
net use j: \\files
net use k: \wdmycloud\files

It responds to pings on ip and by name.

Twonky is running fine - again accessible by IP or name

I’ve performed both resets, and the issue continues.

It’s not a connectivity issue, it’s not an IP address issue, it’s not a name issue

Look at this link for an explanation of the issue.

The seller advised me there’s a way to sort this by connecting to a linux box but has yet to get back to me with details. It’s probably a way to squirt old firmware in.

I’ll be unimpressed with responses advising check the IP address.

And yes I know it should be h ttp not htp, but as a new user I’m not allowed multiple links.

Was this My Cloud purchased new? Or used?

What firmware were you upgrading from, v3.x firmware?

If the My Cloud was purchased used, did the previous seller indicate they replaced the hard drive or “unbricked” the hard drive in the past?

Purchased Used via ebay
Didnt fully read the listing but he pointed out that it specifically mentioned not to upgrade the firmware.

It was V3 firmware I believe, and it was working
The dashboard prompted the upgrade so I did it then it broke.

However the seller has come back with this Youtube Video which I am going to try.

As I suspected, the seller replaced the hard drive and that’s why they stated not to upgrade to the newer (v4.x) firmware. For some (me included) there is an issue post unbricking a replacement hard drive where upgrading to v4.x firmware leads to the Dashboard not loading. In my case (and a few others) the solution was to run a GTP fix (sudo gdisk /dev/sdb) in Linux BEFORE beginning the procedure to unbrick. I created a thread that explains my experience and my individual solution to the issue.


The specific directions I’ve used, twice now, to unbrick two different drives that were successfully upgraded to the v4.x firmware.

How to unbrick, replace or restore original WD My Cloud single hard drive firmware:

These basic directions assume you have a 4GB or larger USB flash/pen drive, a computer with SATA connectors or some form of external SATA enclosure/docking station, basic knowledge of how to boot PC using a boot disc, basic knowledge of how to use Linux.

Note: Use and proceed at your own risk!!!

• Download original_v3.04.01-230.tar.gz to a flash drive: https://drive.google.com/file/d/0B_6OlQ_H0PxVQ2l5MTNvQk1xSUU
• Used Ubuntu Live/Boot CD: http://www.ubuntu.com/download/desktop
• To avoid damaging non WD My Cloud hard drives remove or disconnect them from the computer.
• Backup any data on your My Cloud as these directions may result in the erasure of all data on hard drive.  
• Insert USB Flash/Pen drive containing the file original_v3.04.01-230.tar.gz (or it's extracted contents) into PC before booting with Linux Live/Boot CD
• All terminal commands run from Root user or Sudo. For purposes of this guide Sudo was used.
• After booting with Live/Boot CD open terminal window by typing: 
[ctrl] + [alt] + [t]
Then type:
sudo apt-get update 
sudo apt-get install mdadm parted

To install new/used hard drive start with step 1. 
To repair existing bricked WD My Cloud hard drive start with step 13.

Note: Starting from step 1 will erase hard drive contents. If hard drive contains important data, backup hard drive before proceeding.

1. Find the My Cloud hard drive name (sda, sdb, sdd, sdc, sde, etc.) by typing:
sudo fdisk -l 
sudo parted -l

Note: For these basic directions "sdb" is used. 

2. If you get GTP errors running fdisk or parted then try the following command:
sudo gdisk /dev/sdb

Then type "o" then type "w" to fix GTP errors.

3. Run parted utility:
sudo parted /dev/sdb

4. Type "print" to see what partitions exist on hard drive.

5. If any partitions exist, remove each of them by typing "rm 1" (where 1 - number of partition)

6. Create new table:
mklabel gpt
mkpart primary 528M 2576M
mkpart primary 2576M 4624M
mkpart primary 16M 528M
mkpart primary 4828M -1M
mkpart primary 4624M 4724M
mkpart primary 4724M 4824M
mkpart primary 4824M 4826M
mkpart primary 4826M 4828M
set 1 raid on
set 2 raid on

Type "quit" to exit parted.

7. Format data partition:
sudo mkfs -t ext4 /dev/sdb4

8. Reboot computer, boot back to Linux Live CD. From command line run: 
sudo apt-get update 
sudo apt-get install mdadm parted.

9. Run sudo fdisk -l or sudo parted -l and note the drive names just incase the /dev/sd* location changed.

10. Create main RAID partition, type: 
sudo mdadm --create /dev/md0 --level=1 --metadata=0.9 --raid-devices=2 /dev/sdb1 /dev/sdb2

11. Wait for RAID creation to complete, type:
sudo watch cat /proc/mdstat 

Wait to 100%. Then type:
[ctrl] + [c] for close.

12. Stop auto-loaded raid, type: 
sudo mdadm --stop /dev/md0

If /dev/md0 not found type the following to find RAID mount point: 
sudo ls /dev 
sudo grep md

13. Start normal raid (must be /dev/md0), type: 
sudo mdadm -A /dev/md0 /dev/sdb1 /dev/sdb2

14. Using terminal window navigate to USB Flash/Pen drive location. Example: /media/ubuntu/<drive name> If the contents of file original_v3.04.01-230.tar.gz have not been previously extracted on the USB Flash/Pen drive, type:
sudo tar xvfz original_v3.04.01-230.tar.gz

15. Upload backup images to WD's hdd:
sudo dd if=kernel.img of=/dev/sdb5
sudo dd if=kernel.img of=/dev/sdb6
sudo dd if=config.img of=/dev/sdb7
sudo dd if=config.img of=/dev/sdb8
sudo dd if=rootfs.img of=/dev/md0

16. A Note: If for what ever reason the My Cloud fails to boot (white LED), or problems with upgrade to newer firmware failing/not working (ex. UI fails to load) try the following alternative step.
sudo mdadm --stop /dev/md0

sudo dd if=kernel.img of=/dev/sdb5
sudo dd if=kernel.img of=/dev/sdb6
sudo dd if=config.img of=/dev/sdb7
sudo dd if=config.img of=/dev/sdb8
sudo dd if=rootfs.img of=/dev/sdb1
sudo dd if=rootfs.img of=/dev/sdb2

17. Shutdown PC from terminal window by typing: shutdown -p -H 0 Or use "Logout" from menu.

18. Disconnect hard drive from computer/external connector and connect to WD My Cloud circuit board. Then connect power to the My Cloud circuit board to turn on WD My Cloud. Boot process may take 5-10 min or longer. LED light should change from White to Blue.

Note: If the WD My Cloud fails to boot with either a solid white or red LED, then reattach hard drive to PC/docking station, reinsert USB Flash/Pen drive, boot back into Linux, go back to step 13, then proceed to step 16 to push the three "img" files to their respective partitions, shut down PC and try booting the hard drive again with the WD My Cloud circuit board. 
If the drive still fails to boot (white or red LED), the GTP entry probably needs to be repaired. If that is the case try step 2 above to rebuilt the GPT entry (will probably erase drive contents) and then perform the rest of the subsequent steps. If step 2 doesn't work then start from scratch at step 1. Backup any files if needed from sdb4 (the mountable ext4 partition containing the shares) prior to starting from step 1.

19. After WD My Cloud boots to Blue LED, access the Dashboard with web browser (http://wdmycloud/). Proceed through initial access screen then enable SSH on the Settings -> Network -> Network Services section. Often the capacity will be incorrectly listed, fix by selecting Quick Restore (or Quick Factory Restore) from the Settings -> Utilities section. The device will reboot and rebuild the system files.

20. After factory restore has been performed and WD My Cloud boots, restore any settings (like Static IP) as needed and update the firmware if needed. Be patient. If there was existing data on the hard drive it may take the WD My Cloud OS a long time to scan/catalog the files.

This I will also look at :slight_smile:

Just to say this is sorted after following the youtube video.
It’s very similar to Bennor’s suggestions :slight_smile:

I’m not upgrading the firmware again on this device though.
Just not worth the hassle.

Thanks for all the input folks.