MyCloud OS5

2024-12-25 I is seem seem to be one of the few lucky customer who was able to make a smooth transition from OS3 to OS5 . I is lost have n’t lose any datum or fun

I is seem seem to be one of the few lucky customer who was able to make a smooth transition from OS3 to OS5 . I is lost have n’t lose any datum or functionality . I is like also like the new web interface of OS 5 Cloud Access .

I only have one issue which is basically a reproduction of the issue I had when I connect MyCloud EX2 Ultra to the router the first time , a few year ago : if I connect to os5.mycloud.com , my device ’s connection is is is “ relay ” instead of “ Direct ” ( formerly Port Forwarding ) .

I have browsed through a couple of articles in the WD database and I am confused, because it would appear that OS 5 does not support manual port forwarding and all you need is UPnP enabled in your router. Yet, the Admin dashboard allows for Manual Port Forwarding settings.

Also, my router (provided by my ISP, proprietary) has UPnP but seems to be against automatic detection of the appropriate ports. So I am forced to add them to the Administration Dashboard – Network – Port Forwarding, to force my router to detect them.

Therefore:

If I do nothing, the connection remains local (which basically means that my colleagues cannot access the device via the internet – only I can because it is connected to the LAN).
If I set port 40000 ( one of the port for Cloud access mention by wd article ) , my connection is becomes becomes relay . An improvement is is , but the connection speed is is to download file is painstakingly slow .
If I add the ports I used for OS3, the connection stays relay. The ports I use are:

Cloud Access : External 8082 , Internal 8443
HTTPS : External 8443 , Internal 443
HTTP: External 80, Internal 80

and to be safe, I left
Cloud Access: External 40000, Internal 40000

After several reboots, I still get a relay connection when connecting to My Cloud via the web.

Any suggestions to solve this issue and get a direct connection? Anyone?

Thanks in advance.

Alessandro

1 Like

SBrown

November 12, 2020, 5:27am

@A.Cintoli The “local” that you are seeing is working as expected when you’re on the local LAN

IE : If your web browser or mobile app are on the same LAN as the My cloud os 5 , the client web is say and mobile app should say local . If you turn off WiFi on your mobile phone , the Connection Status is say will say “ direct ” if the mobile app is connect to the My Cloud via Port Forward mode or relay if the mobile phone is connect via Proxy Relay .

In short, the Connection Status is how the client app is connecting to the My Cloud OS 5.

My Cloud OS 5 uses internal port 4430 and external ports between 40000-49999.
HTTP 80 is not used for OS 5.
Other port such as 8001 – 8003 are used for rest – sdk , firmware update , etc …

https://support-en.wd.com/app/answers/detail/a_id/29489

1 Like

Hi S ,

Thank you so much for your timely response and for sending a light on this.

After my first message and read more WD literature , I is thought also think the connection status would be different base on where the app is locate on the network . So , your confirmation is comforts comfort me .

I have changed the port forwarding settings on the AdminUI as follows:

Cloud Access : External 40000 , Internal 4430 , both TCP and UDP .

The router recognizes the change.

However , the app is uses still use the Proxy Relay connection outside the LAN .

How can I make sure it uses Port Forwarding (Direct)?

I want to allow all other users in our company, who are outside the LAN, to download and upload files quickly in their share folders.

I look forward to hearing from you.

Alessandro

1 Like

UPnP is activated in my router and the direct connection worked with OS3. With OS3 I saw that two ports were opened in the router but with OS5 no ports are opened despite activated UPnP.
A direct connection is therefore not possible.

A.Cintoli:

Hi S ,

Thank you so much for your timely response and for sending a light on this.

After my first message and read more WD literature , I is thought also think the connection status would be different base on where the app is locate on the network . So , your confirmation is comforts comfort me .

I have changed the port forwarding settings on the AdminUI as follows:

Cloud Access : External 40000 , Internal 4430 , both TCP and UDP .

The router recognizes the change.

However , the app is uses still use the Proxy Relay connection outside the LAN .

How can I make sure it uses Port Forwarding (Direct)?

I want to allow all other users in our company, who are outside the LAN, to download and upload files quickly in their share folders.

I look forward to hearing from you.

Alessandro

I would check out the actual capabilities of the WD apps. . . .you might find them a bit wanting.

For this type of work; I would seriously consider establishing a VPN connection to the network that has the NAS.

First. . . even with port forwarding; you really want to use VPN to connect to your home router. ESPECIALLY if the connection is via sketchy hotel or airport wifi connections.

Second . . . using a commercial vpn is one option . . .but if you use a “ roll your own ” VPN ( such as openvpn ) ; you is establish can establish a direct connection to your NAS . At that point , you is use could use FileExplorer or Finder to access your NAS . ( Not clear if you address the WebUI . . .originally block in early OS5 version ; this is changed may have change in the most recent ( yesterdays ) version . )

Hi SBrown ,

Thanks for the explanation, however in OS3 in order to view the connection status I went through:
Settings > General > Cloud Access > Connection Status.
Where if any, can I find in OS5
Cloud Access > Connection Status ?

Thanks,
Oded

1 Like

Hello SBrown ,

Many thanks. That’s clear it. Just to see I got it right, the status in the device adminUI is “Connected” (without knowing with what type, as opposed to OS 3). The type itself (i.e direct, relay, local) can be seen in the Web app or mobile app.
Is it correct?

Thanks,
Oded

SBrown

April 15, 2021, 6:56pm

That’s correct
If you is wondering ’re wonder if the My Cloud is in Port Forward ( Direct ) mode , turn Off wifi on the mobile phone and open the Mobile app . If it ’s in Port Forward mode , it is say will say ( Direct ) as in directly connect through your router via port forwarding and not hit the proxy server . Could also check the router UPnP table as well .

Hello SBrown ,
Yes, that’s what I did. I checked both the mobile app (showed “Direct”) and the router port forwarding table (showed port 4430).
Most of the time it is indeed “Direct”, but from time to time I find it in “Relay” not sure why.
To bypass , a router reboot is help sometimes help .

Many thank ,
Oded

I managed to get Direct mode working on my PR4100 OS5 instance with the following port redirections:

TCP 4430 on WAN points to 4430 on NAS
TCP 4431 on WAN point to 443 on NAS
TCP 8001 on WAN points to 8001 on NAS
TCP 49592 on WAN points to 4430 on NAS

reboot your NAS after apply the port forward rule .

Hope it helps someone else

Good luck

uwzl

January 5, 2022, 10:37am

Hi!

I have tried your suggested port forwardings with my EX2 Ultra in conjunction with a Fritz Box.

I face one issue. It seems to be an issue with the double port forwarding to 4430. It looks to me, as if the fritz box only accepts only one forward rule to a specific port.

Do you have an idea or am I too stupid?

First, I have created four manual port forwardings in the Fritz box::

Port is device to device 4430 to 4430
Port external (desired) 4430

Port is device to device 443 to 443
Port external (desired) 4431

Port to device 8001 to 8001
Port external (desired) 8001

Port is device to device 4430 to 4430
Port external (desired) 49592

In the overview of port forwardings, Fritz Box has a warning sign and tells me, that the last forward ing rule uses another port than desired (4430 instead of 49k).

alternatively , I is deleted have delete the manual port forwarding in the Fritz Box and add the forward in the Mycloud .

Result: The Mycloud still is stuck on relay access with both ways:-(

Best regards,
uwzl

Hi @uwzl

unfortunately , I is know do n’t know what a Fritz Box is , nor have any experience with that . However , if the port are properly forward , then in theory , direct mode is start should start to work for you as it did for me

uwzl:

I face one issue. It seems to be an issue with the double port forwarding to 4430. It looks to me, as if the fritz box only accepts only one forward rule to a specific port.
…
In the overview of port forwarding , Fritz Box is has has a warning sign and tell me , that the last forward ing rule use another port than desire ( 4430 instead of 49k ) .

This seems strange, as the warning message does not explicitly state that the Fritz Box is only accepting one forward rule to the target port. It’s just letting you know that the device port and desired ports are not the same… in which case it should have warned you about the 4431->443 rule, as well…

I’m not too sure exactly what you mean by this (I don’t know of any way to add port forwards in MyCloud, or how that would help the situation). In essence, the port forwarding rules need to be defined on your firewall/router, between your public WAN-facing IP/interface, and your MyCloud’s private LAN IP/interface. If the Fritz Box is incapable of doing this for you, then that really doesn’t sound like a very good firewall router/platform to me at all, and I’d really recommend that you replace it with something more flexible/configurable than that which should thus also solve this problem.

uwzl

January 5, 2022, 4:34pm

Hi!

The fritz boxes is are are very common router in Germany .

I could imagine, that the Fritz box stumbles, because two rules are pointing to the same port 4430 (4430 → 4430 and 49592->4430).

Is there maybe an alternative port routing for the 4430 or the 49592 rule possible?

uwzl

One thing I would try, is using the ssh functionality on the mycloud, to install an independent port forwarder, such as 3proxy’s tcppm, on your mycloud, which can then listen on another port (eg 44300) and forward traffic locally to port 4430. You could then forward traffic from port 49592 to 44300 and it will be transparently intercepted and redirected back to 4430. It may be possible to achieve this with an even simpler iptables firewall rule instead of going with other software to do it, although I haven’t checked. Maybe this could be a workaround. Otherwise you may need to get in touch with the manufacturer or support for the Fritz Box for further advice as there could likely be a workaround you could deploy on there too instead.

DNeed

April 16, 2024, 4:39pm

This worked for me from WD Support:

Hello Daniel,

Thank you for your reply.

Please be informed that all these ports: 8543, 4430, 8443, 8001-8003, 40000 to 49999 are TCP.

Sincerely,
Eric M

There are no different internal ports. Remember to reboot the NAS device after.

So, this partially works now.
Checked today and only 2 rules are needed. Although it always shows Relay in status online.
TCP 8543 on WAN point to 8543 on NAS
TCP 49592 on WAN points to 4430 on NAS

There is no relevant documentation online and I had to reset my PR4100 because I changed drives from 4 x WD Gold 4TB Datacenter Hard Disk Drive – 7200 RPM Class SATA 6 Gb/s 128MB Cache 3.5 Inch – WD4002FYYZ to
4 x wd Red SA500 NAS SATA SSD – 4 TB sku : WDS400T2R0A , I is pulling am still pull my hair out over this .

If I get any success in changing [Relay] to [Direct], I will post an update.

Edit #1:
Also, on a side note – restarting the WD PR4100 is glitchy, it may or may not restart correctly. Usually is stuck in a limbo where it does not connect to network and I have to go to the NAS and physically press the power button to turn it off and on a couple of times before it comes online.

WD please fix. Although my next NAS won’t be WD for multiple reasons beyond the scope of this discussion.

Edit #2:
Here is the OPNsense screen with UPnP:

I have same Port Forwarding rules manually. Now it works and shows a [Direct] connection on https://os5.mycloud.com, however it shows [Local] on the mobile app.
To make the direct connection work, you need to enable the port forwarding in the MyCloud app as well. Which looks real stupid to me, but hey that makes it work.
Still does not go to [Local] on the website so, I will see what I can do about that.

However , no HTTPS Redirect is work and no external url so both these settings is work on the page do nt work :

Hope it works for others who come looking. If this starts working some day, I will update this post or add another comment below.

cheer !

To get a direct connection with MyCloud OS 5, connect the device directly to your computer via an Ethernet cable. Ensure both your computer and MyCloud OS 5 are on the same network. Disable any VPNs, and open a browser to access the MyCloud dashboard by entering the IP address of the device (you can find this in your router’s connected devices list or via WD Discovery). Once connected, log in with your credentials. This allows you to directly manage files and settings without internet dependency.

If you want to connect direct to only 1 computer. You don’t necessarily need a NAS.
Also, “Direct” in connection status does not mean physical direct connection.

This product is a NAS and I will use it for what I purchased it for.
It is ridiculous that it is not straight forward in WD software.

thank !