No Dashboard Access after OS5 upgrade

[MarthaC]

@SBrown

If the My Cloud is configured on a network that does not align with the Internal IP address rules, then it will need to be relocated on a different network that does align with the Internal IP address rules and 4 second pin reset to get it back into DHCP if configured with a static IP.

Is there a way to roll back?

[antoniov8]

Hi @SBrown,

I removed both drives, I get the same error (500 error, connection refused). I think my drives are ok, but the enclosure might be bricked.

What are the next steps?

@SBrown

HTTP Error 500 means internal server error.
Since you have access to your data, please make a backup copy if you haven’t already and if you are willing to troubleshoot…follow the steps below.

1. Power OFF the My Cloud (yes you’ll have to pull the power plug as we have no access to the dashboard)
2. Safely remove both HDD (do not mix them up)
3. Power ON the My Cloud and see if you have access to the AdminUI dashboard with no HDD inserted

If NO, the enclosure will need to be replaced
If YES, the issue is on the HDD and I will need to consult with engineering for direction.

[htb]

@antoniov8, Please help me to have a case open in our CRM and share the case number thru private message.
https://support-en.wd.com/app/ask

Thanks,

[Revid]

I have both a pr4100 and ex4100. After updating to os5 - I could sign in from the internet but could not get to my dashboard. I either got a 403 error or simply a blank page on my Mac. After hours of useless tech support and multiple promises of calls back from higher tier tech support (which never happened), I still was unable to access the dashboard. I finally connected to a completely different router with its own internal network. I was able to see the dashboard. When I reconnected to my home network - couldn’t see the dashboard again. Finally I noticed that I had manually forwarded the ports in os3 to the individual NAS units. I removed the manual port forwarding and was immediately able to see my dashboard. So simple I don’t know why WD tech support could not figure it out. They had even been remotely on my computer to try to fix the problem and couldn’t. Anyhow, I hope this helps some of you.

[remotelypossible]

OS5 admin access using powershell & OpenSSH

This is what I’ve done to do the SSH with powershell rather than Putty.

install OpenSSH in powershell

NAS02
Public IP port forward 80 on router to another port number:

123.123.123.123:8082

SSH User: sshd@123.123.123.123

The OpenSSH command line in powershell:

ssh -f sshd@123.123.123.123 -p 22 -L 8082:123.123.123.123:8082 -N

-f sends the ssh command to the background so that you don’t have to keep powershell open
“sshd” is the built in SSH user on the MyCloud
123.123.123.123 is the public IP (obviously I changed it from my actual NAS IP) of the MyCloud

22 is the public port on MyCloud that SSH is published to

-L is local port, so your localhost:8082 will be forwarded

123.123.123.123:8082

-N instructs OpenSSH to not execute a command on the remote system

So once you run the ssh command in powershell (admin) window you just open localhost:8082 in your browser and the NAS thinks you’re in it’s local subnet