My Cloud PR4100 / EX2 Ultra Login My Cloud OS5 504 Error: How to Fix It

The My Cloud PR4100 / EX2 Ultra Login My Cloud OS5 504 Error can prevent users from accessing their NAS dashboard or cloud account even when the username and password are correct. A 504 Gateway Timeout generally means that a server or gateway did not receive a timely response from another server or application.

A WD Community discussion reported a widespread My Cloud OS 5 login problem beginning around March 10, 2024. Users reported the issue on devices including the My Cloud PR4100, PR2100, and EX2 Ultra, with the affected systems reportedly running firmware 5.27.161. The user who opened the discussion said that the same 504 error appeared when attempting to log in from a NAS, PC, or mobile phone. They also tested different internet service providers and devices, without resolving the problem.

Although a 504 error can sometimes be caused by a local network problem, repeated failures across multiple networks and devices can indicate that the problem is associated with an online service or another upstream component rather than the NAS hardware itself.

What Does My Cloud OS 5 Error 504 Mean?

A 504 Gateway Timeout occurs when one service acting as a gateway or proxy does not receive a response from an upstream service within the expected time.

For a My Cloud OS 5 user, this can appear during account authentication, cloud-related operations, or access to a web service. It does not automatically mean that the hard drives inside your PR4100 or EX2 Ultra have failed.

It is important to distinguish between:

A local dashboard problem

A Western Digital account login problem

A cloud-service communication problem

A network or router problem

A NAS operating-system problem

The troubleshooting method should depend on which type of access is failing.

Check Whether the Problem Is Local or Cloud-Based

First, determine whether you can access the NAS from your local network.

WD's documentation says that the My Cloud OS 5 dashboard is normally accessed from the local network. For example, the documented default addresses include http://mycloudex2ultra for the EX2 Ultra and http://mycloudpr4100 for the PR4100 on Windows.

Connect a computer to the same network as the NAS and try the appropriate device name or its local IP address.

If the local dashboard opens normally but cloud-account login fails, the problem may be related to account or cloud authentication rather than the storage system itself.

If the local dashboard also fails, continue with local-network troubleshooting.

1. Restart the Router

A temporary router or network communication problem can prevent the NAS from communicating correctly with online services.

Power off the router and wait approximately 30 seconds. Then turn it back on and allow it to reconnect to the internet.

WD specifically recommends removing power from the network router, waiting 30 seconds, powering it back on, and then power-cycling the My Cloud when the dashboard does not load.

After the router has fully restarted, restart the My Cloud device and test the login again.

2. Power Cycle the My Cloud NAS

A simple power cycle can clear temporary processes or communication problems.

Before doing this, make sure the NAS is not actively performing an important operation such as a disk rebuild, backup, file transfer, or firmware update.

After the device has restarted, wait until the power LED indicates that the NAS is ready. WD's troubleshooting guidance recommends confirming that the Power LED is solid blue before attempting dashboard access.

3. Check Your Network Connection

Make sure the computer and NAS are connected to the same local network.

Also check whether your computer is connected through:

A VPN

A guest Wi-Fi network

A different VLAN

A different subnet

A network isolation feature

WD specifically advises ensuring that the computer is not connected to a VPN or a different VLAN, network, or subnet when troubleshooting dashboard access.

If possible, temporarily disable the VPN and connect the computer directly to the primary home or office network.

4. Try the Local Dashboard

Testing the local dashboard is one of the most useful troubleshooting steps because it helps determine whether the NAS itself is responding.

For an EX2 Ultra, WD lists:

http://mycloudex2ultra

For a PR4100, WD lists:

http://mycloudpr4100

You can also use the NAS's local IP address in your browser. WD explains that the dashboard provides access to device settings and features and that dashboard access is limited to the local network by default.

If the dashboard loads successfully, your NAS may be functioning normally even if cloud login is failing.

5. Verify Your Account Credentials

If the error occurs during Western Digital account authentication, verify that you are using the correct email address and password.

Do not repeatedly enter passwords if you are unsure of the credentials. Instead, use the official password-reset process.

WD's current password-reset instructions state that users can select Forgot Password?, enter their email address, and follow the instructions sent by email. WD also notes that the email address must already exist in the Western Digital account database.

Check your spam, junk, trash, and other filtered folders if the reset email does not appear immediately.

6. Update the My Cloud OS 5 Mobile App

If the 504 error occurs only when using the mobile application, check that the application is up to date.

WD states that older My Cloud OS 5 and My Cloud Home mobile applications may no longer support Western Digital account login. Its support documentation specifically notes that mobile app versions 4.17 and older stopped working for account login in April 2022.

Update the application through the appropriate app store and then attempt to sign in again.

7. Check Browser and Cookie Settings

Browser settings can sometimes interfere with authentication.

For example, WD documents situations where blocked cookies can cause an "Oops! Something went wrong" message during My Cloud OS 5 mobile authentication. Its recommended troubleshooting includes allowing cookies in the relevant browser settings.

If the login page behaves strangely, try:

Opening a private/incognito browser window.

Clearing cached site data.

Allowing required cookies.

Temporarily disabling browser extensions.

Trying another supported browser.

These steps are especially useful when one browser fails but another works.

8. Avoid an Immediate Factory Reset

A common mistake is to assume that every login problem requires resetting the NAS.

A 504 Gateway Timeout does not by itself prove that your hard drives are damaged. If the device is accessible locally and your files are visible, avoid performing a destructive reset simply because the cloud login is failing.

WD's setup documentation does mention a 40-second pin reset when the dashboard login or setup page does not appear, but reset procedures should be used carefully and according to the applicable WD instructions.

Always protect important data before performing any reset or recovery procedure.

9. Test From Another Device or Network

If you suspect a local problem, test the login from another computer or phone.

You can also test from another internet connection when appropriate.

This is particularly helpful because the original WD Community report found that changing ISPs, using different devices, and testing from another country did not eliminate the 504 error. That evidence made a broad local-network explanation less likely for that particular incident.

However, because the original discussion dates from March 2024, users experiencing the error today should not automatically assume they are experiencing exactly the same service incident.

10. Contact Western Digital Support

If the error continues after basic troubleshooting, contact Western Digital Support and provide as much information as possible.

Include:

My Cloud model

Firmware version

Exact error message

Approximate time the problem started

Whether local dashboard access works

Whether the mobile app works

Whether multiple browsers were tested

Whether another network was tested

Whether other users or devices are affected

This information can help determine whether the problem is associated with the NAS, network, account, or cloud service.

Frequently Asked Questions

Why does my My Cloud PR4100 show a 504 error?

A 504 error means that a gateway or intermediary did not receive a timely response from an upstream service. It does not necessarily indicate a failed hard drive.

Can a 504 error be caused by my password?

Usually, an incorrect password should produce an authentication-related response rather than a gateway timeout. If the correct password causes a long delay followed by 504 while an incorrect password is immediately rejected, that can be a useful clue that the authentication process is reaching another service but not receiving a timely response.

Does restarting the NAS delete my files?

A normal power cycle does not intentionally erase stored files. However, you should avoid forcibly powering down the NAS during disk-intensive operations, RAID rebuilding, or firmware updates.

Can I access my PR4100 without cloud login?

Yes. The local My Cloud OS 5 dashboard can be accessed through the local network using the device name or IP address. WD provides specific local addresses for supported My Cloud models.

Should I reset my EX2 Ultra if I see error 504?

Not as a first step. First determine whether the problem is local, account-related, or cloud-service-related. Back up important data and follow WD's documented reset procedure before performing any reset.

Conclusion

The My Cloud PR4100 / EX2 Ultra Login My Cloud OS5 504 Error can be confusing because the NAS may be operating normally while an authentication or cloud-related service is experiencing a timeout. The 2024 WD Community report described users receiving the error across multiple devices and networks, which suggested that simply changing a PC, phone, or ISP was not enough to resolve that particular incident.