Comments on: WordPress on WDMyCloud V4 Firmwares

By: Nazar

Nazar — Tue, 21 Jan 2020 16:46:50 +0000

In reply to planetastronomia. Yes (-: My WordPress site used to be running on the MyCloud firmware V4 for many years.

By: planetastronomia

planetastronomia — Tue, 21 Jan 2020 09:11:21 +0000

Hello,

I have a MyCloud 1 bay 2TB, with serial num. WDBCTL******-00. And I have the firmware versión V4

I have a wordpress blog, and I would like to move the host to my MyCloud.

Is this method valid for me?

Thanks

By: Mathieu Vanier

Mathieu Vanier — Wed, 29 Mar 2017 19:06:25 +0000

In reply to Nazar. Worked #1, Thx again for all your work. :) Mathieu

By: Nazar

Nazar — Wed, 29 Mar 2017 18:36:15 +0000

In reply to Mathieu Vanier.

Your router doesn't support NAT loopback. This means you can't access any port forwarding setup while you're within your local network but the connection works when you're outside the network.

So for this temporary workaround you'll need to modify your PC's hosts file to tell that you want to connect to an internal IP via the full qualified domain. You can use LMHOSTS too but HOSTS file is probably easier. Now on your current PC, edit this file "C:\Windows\System32\drivers\etc\hosts" or if you're using Mac, "/etc/hosts". You'll definitely need admin access and/or take ownership of the file's privileges. Add a new line 192.168.1.2 classemathieu.ddns.net where 192.168.1.2 is your MyCloud's internal IP. After saving it, you can now browse using http://classemathieu.ddns.net:5080/ which your PC will resolve the DDNS to your MyCloud's internal IP instead of your ISP's IP.

This is not a standard implementation but it's just a workaround for your case. You will also need to modify the hosts file on all internal device as necessary. If your router has the ability to specify static hostnames (I used to have one), you can just do this on your router to avoid modifying hosts file on all internal devices.

By: Mathieu Vanier

Mathieu Vanier — Wed, 29 Mar 2017 18:13:16 +0000

In reply to Nazar. i do not know how to set this nat loopback... can you explain more?

By: Nazar

Nazar — Wed, 29 Mar 2017 17:55:28 +0000

In reply to Mathieu Vanier.

This is just how WordPress works, might be standard for other CMS too. It will always redirect you to your hostname in the setup. I think because primarily WordPress is able to run on multi-site so it needs to redirect correctly according to the hostname in the setup.

BTW why are you trying to access using IP? Have you setup the hosts file I mentioned earlier since your router have NAT loopback limitations? In Windows: "C:\Windows\System32\drivers\etc\hosts" or Mac: /etc/hosts.

By: Mathieu Vanier

Mathieu Vanier — Wed, 29 Mar 2017 17:42:38 +0000

In reply to Nazar. I think the problem is wordpress always make attempt to connect to : http://classemathieu.ddns.net:5080/wp-login.php If i write my local ip adress :192.168.1.200:5080/wp-login.php i can go to login screen. But when i press the connect button, it try to connect to my ddne.net adress. is that a router problem or wordpress settings?

By: Nazar

Nazar — Wed, 29 Mar 2017 17:36:57 +0000

In reply to Mathieu Vanier.

I'm not sure how you setup is and whether it's final or not but that's up to you. I don't see WordPress running on your port 5080 but there's Joomla on port 80. If you're accessing WordPress directly using the port 5080 and not using any PAT (port address translation), go to your WordPress Dashboard -> Settings -> General and edit both "WordPress Address" and "Site Address" appending port ":5080" to it i.e. http://yourddns.com:5080/.

By: Mathieu Vanier

Mathieu Vanier — Wed, 29 Mar 2017 17:12:39 +0000

In reply to Mathieu Vanier. but do you know why on external network i can access to wordpress dashboard and i can't on my internal network?

By: Nazar

Nazar — Wed, 29 Mar 2017 17:10:16 +0000

In reply to Mathieu Vanier.

Glad it worked out for you, enjoy (-: