Comments on: CloudDAVMod v1.1 for WD My Cloud firmware V4 http://teanazar.com/2016/09/clouddavmod-v1-1-for-wd-my-cloud-firmware-v4/ ..._\m/ Wed, 09 Nov 2022 22:09:54 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Nazar http://teanazar.com/2016/09/clouddavmod-v1-1-for-wd-my-cloud-firmware-v4/comment-page-4/#comment-1664 Wed, 09 Nov 2022 22:09:54 +0000 http://teanazar.com/?p=2213#comment-1664 Only WDMyCloud single bay first gen is supported.

]]> By: Paschalis http://teanazar.com/2016/09/clouddavmod-v1-1-for-wd-my-cloud-firmware-v4/comment-page-4/#comment-1663 Wed, 09 Nov 2022 19:51:47 +0000 http://teanazar.com/?p=2213#comment-1663 Hi, so from what I’ve read wd mycloud ex2 ultra , which has v.5 firmware is not supported, correct?

]]> By: Walter http://teanazar.com/2016/09/clouddavmod-v1-1-for-wd-my-cloud-firmware-v4/comment-page-4/#comment-1657 Fri, 16 Sep 2022 16:49:04 +0000 http://teanazar.com/?p=2213#comment-1657 Hi, the link not working, my ip is banned 1 hour 🙁

]]> By: Nazar http://teanazar.com/2016/09/clouddavmod-v1-1-for-wd-my-cloud-firmware-v4/comment-page-4/#comment-1656 Mon, 08 Aug 2022 17:17:07 +0000 http://teanazar.com/?p=2213#comment-1656 It’s not compatible yet. I’ll release it soon, stay tuned.

]]> By: nos1609 http://teanazar.com/2016/09/clouddavmod-v1-1-for-wd-my-cloud-firmware-v4/comment-page-4/#comment-1654 Sun, 07 Aug 2022 09:29:28 +0000 http://teanazar.com/?p=2213#comment-1654 Hi Nazar

WD has released the final Firmware version 04.06.00-111. Is the latest release on this page compatible with WD’s latest firmware?

https://downloads.wdc.com/nas/sq-040600-111-20220109.deb

]]> By: Nazar http://teanazar.com/2016/09/clouddavmod-v1-1-for-wd-my-cloud-firmware-v4/comment-page-3/#comment-1649 Thu, 31 Mar 2022 18:53:21 +0000 http://teanazar.com/?p=2213#comment-1649 Hi Jim,

No problem glad it turns out good. The WD’s DDNS sometimes is down, that could be the issue. Only after April 15, 2022 then the service will be turned off.

For the v353 not loading I need to look into it, not sure what happened as it seems to work on my test instance. I’ll need to look at your instance to determine the issue, probably when you’re free we could link up in an email conversation.

]]> By: Jim Witherspoon http://teanazar.com/2016/09/clouddavmod-v1-1-for-wd-my-cloud-firmware-v4/comment-page-3/#comment-1648 Thu, 31 Mar 2022 18:41:44 +0000 http://teanazar.com/?p=2213#comment-1648 Somehow remote access is now working with the wd2go.com link – I must have had a typo somewhere in the URL. Sorry for the false alarm on that!

]]> By: Jim Witherspoon http://teanazar.com/2016/09/clouddavmod-v1-1-for-wd-my-cloud-firmware-v4/comment-page-3/#comment-1647 Thu, 31 Mar 2022 16:39:19 +0000 http://teanazar.com/?p=2213#comment-1647 p.s. I have Cloud Access turned on in the My Cloud dashboard, and a port forwarding connection is establshed, not a relay connection.

]]> By: Jim Witherspoon http://teanazar.com/2016/09/clouddavmod-v1-1-for-wd-my-cloud-firmware-v4/comment-page-3/#comment-1646 Thu, 31 Mar 2022 16:18:49 +0000 http://teanazar.com/?p=2213#comment-1646 Hi Nazar, I had updated the firmware to 353 and also installed the 353 version of CloudDAVMod. I couldn’t get the CloudDAVMod interface to load completely. I successfully downgraded the firmware and CloudDAVMod to 342, and now the web interface loads again. But the web2go.com link given in the CloudDAVMod help doesn’t work – Windows gives a “This site cannot be reached” error. The network diagnostics says ” Your DNS server might be unavailable. Windows can’t find the host name “deviceXXXXXXX-XXXXXXXX.wd2go.com” using DNS. ” Has remote access through web2go.com links already been disabled for this device? Going forward (after April 15), will there be a way to access the WD My Cloud remotely? Thanks for any help!

]]> By: Nazar http://teanazar.com/2016/09/clouddavmod-v1-1-for-wd-my-cloud-firmware-v4/comment-page-3/#comment-1636 Sat, 19 Feb 2022 04:46:13 +0000 http://teanazar.com/?p=2213#comment-1636 I don’t think WD locked the SSH in v04.05.00-353. Perhaps there’s a glitch during the update. Are you trying to SSH by using the hostname? Try using its IP instead. Perhaps you could try to update to the same firmware again.

]]>