No problem, glad it helps (-:

Just for the benefit of anyone else reading this, it seems installing OwnCloud requires a bit of tweaking which was a bit beyond my capability.

Reflashing the firmware (rather than just a dashboard reset) allows you to start with a clean slate, removing any OwnCloud installations or other mods.

CloudDAVMod is awesome, but that goes without saying. Simple to install and very lightweight. Much better suited to what I was looking for.

Finally, a point which I didn’t know. Using the Twonky Server, it is better to leave the scan rate at 0, it then can easily check for new files without rescanning. I had set it to ~4 hours, this meant it rescanned the whole disk every 4 hours, killing performance.

A big thank you, to you Nazar, for all of your help and expert advice. My NAS is infinitely better for all of your hard work. 🙂

Which part of OwnCloud are you having trouble with?

As for the CloudDAVMod installation, I’ll contact you directly via your PayPal registered email.

And for your last question, you can do it several ways. The easiest is to reflash the firmware from the Dashboard.

You could try using the APCu cache (Though I have not tried), set to your OwnCloud config.php: /DataVolume/owncloud/config/config.php -> 'memcache.local' => '\OC\Memcache\APCu',. Play around with the cache size: /etc/php5/fpm/conf.d/20-apcu.ini -> apc.shm_size=2M, default is 32MB, WD sets it to 2MB think due to the limited RAM. Note that you’ll need to reload PHP on every changes: service php5-fpm reload.

Personally I use my own mod, CloudDAVMod v1.1 for WD My Cloud firmware V4, its WebUI is simplier and way much faster because it’s not using PHP. Note that the latest v1.1 (more functions like WWW-SSH, System Panel, searching and sharing) is reserved for donors and only v1.0 (need to downgrade to a specific firmware version) was released to the public, CloudDAVMod v1.0 for WD My Cloud firmware V4.

To make the changes, enter nano /etc/php5/fpm/pool.d/www.conf:

Scroll towards the end of the file and you’ll see this ;env[PATH]. Remove the “semicolon” from the beginning of the line then CTRL+X to exit and save the changes.

If you want to match the PATH environment to our MyCloud (recommended, see env|grep PATH), instead of uncommenting, enter a new line just below it and use this instead:
env[PATH] = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin.

Then don’t forget to restart the PHP daemon, service php5-fpm restart.

As for the slowness that you encountered, although I don’t use OwnCloud, I had spent some time playing with it and it seems ok.

Some thoughts, in the top command, also take note of the followings:

1. “wa” (IO wait percentage, in the %Cpu(s) row)

2. “Swap” (used in KB, 1000KB=1MB)

If the IO wait percentage is consistently hitting high and your swap usage is almost 300MB, then this is where MyCloud tends to slow down due to disk/Swap IO trashing. Do you have any other 3rd party apps?

It’s also good to monitor the top command, enter “f”, scroll to “VIRT”, enter “s” then “ESC”. This is to sort the list by virtual memory (in KB, press “h” for help) to see which process is using relatively high memory and decide if you don’t need them to be running (like the wdmcserver, wdphotodbmerger, nfs, vsftpd, and/or replace Twonky with MiniDLNA or disable DLNA if you don’t need them, to stop service <service> stop, to disable/enable at boot use the update-rc.d <service> disable|enable) as MyCloud has only 256MB of RAM. This is how I manage my MyCloud running this site with all the installers and stuffs.

A forum suggested: Uncommenting the line “env[PATH] = /usr/local/bin:/usr/bin:/bin” in the file “/etc/php5/fpm/pool.d/www.conf” to remove the error.

I have limited knowledge in this area, and don’t want to brick my NAS, can you provide any advice? Thanks

The sub-path method is merely placing your scripts into a new subdirectory under the www root path (/var/www/html/new-sub-path/) and accessing it directly with http://ip-or-domain/new-sub-path/ without the need to setup vhost (virtual host). I suggest you’d move away and symlink this path into the /DataVolume because it will be lost on firmware update.

As for your DDNS, the vhost needs to be setup, have you gone through steps 3 and 4 of my guide? You need to edit the config file especially the server_name variable replacing it with your DDNS. Ensure the config is enabled as stated in the guide then reload it service nginx reload. Only then you can access it with your DDNS.