Unix and Linux network configuration. Multiple network interfaces. Bridged NICs. High-availability network configurations.


Reviews of latest Unix and Linux software. Helpful tips for application support admins. Automating application support.


Disk partitioning, filesystems, directories, and files. Volume management, logical volumes, HA filesystems. Backups and disaster recovery.


Distributed server monitoring. Server performance and capacity planning. Monitoring applications, network status and user activity.

Commands & Shells

Cool Unix shell commands and options. Command-line tools and application. Things every Unix sysadmin needs to know.

Home » Applications

Notes on ownCloud configuration

Submitted by on April 12, 2019 – 4:13 pm

The ownCloud file sharing application has been around for some time now, but somehow evaded my attention. My limited imagination makes me say “think of it us Dropbox hosted on the server in your basement”.

Of course, it is much more than that. You can even get a cloud-hosted setup, but the “server in the your basement” is what led me to ownCloud in the first place. Plus, ownCloud is full package – server software, desktop clients, and mobile clients – all available for common operating environments.

The install is fairly straight-forward and is amply explained in the documentation as well as by countless bloggers. Personally, I followed this set of instructions to get ownCloud up and running on my CentOS 6 box.

I really didn’t have to do much, as I already had working LAMP configuration in place. I just created a new MySQL schema; unpacked the application tarball into a sub-folder of one of my existing sites; and made a couple of quick edits of the config.php.

Having said that, I did run into a few puzzling situations that were easy to resolve, but prompted me to do this quick write-up.

First, make sure to download the latest stable version, as the upgrade process is a bit hairy and you may want to enjoy the application’s functionality for a while before having to go down that rabbit hole.

Second, when editing that pesky config.php, understand this: the trusted_domains array must contain the actual full server name, IP, or domain – basically, whatever you type into the browser to get to it. Wildcards, IP ranges, CIDR notations – none of that is allowed. Here’s an example:

Strictly speaking, if everything’s working just fine, you don’t need all of these things in your trusted_domains – just the primary address is whatever URL you use to access ownCloud.

Three, when choosing the administrator’s account name, go with anything but admin. And, when choosing the password, avoid Windows special characters, such as ()&%!*. Why? Because Windows is stupid and if you would like to connect to WebDAV, those special characters in the password will be a problem.

Four, since we’re on the WebDAV topic, here’s to mount your ownCloud account. Open cmd.exe as administrator and type something like this:

You can also do the same via the File Explorer. To get the correct WebDAV URL for your installation of ownCloud, log in via the Web UI and in the bottom left corner click “Settings” and there it will be.

As I mentioned, ownCloud upgrade process, while not complicated, is a bit convoluted. I wrote a small helper script (you can download it here). I haven’t had much time to test it, so no guarantees…


Print Friendly, PDF & Email

Leave a Reply