I've got Owncloud running from the OMV plugin and have been trying to organise remote access - that's kind of the point in my view.
I've got into my router and created a virtual server pointing port 80 external to the 192.168.1.19 (the machine which OMV is running on).
I've also created an 'a' record on an external DNS service pointing my intended domain 'cloud.example.com' at my router's ip address (it's fixed).
I now have two problems:
Firstly, and this something I haven't encountered before, If I go to that domain from within the LAN it seems to ignore the virtual server rule and direct straight through to the router's webserver, and admin interface. External requests go to 192.168.1.19, the correct ip.
My second problem is that I can't get apache to point that incoming domain to the Owncloud server, rather than the OMV admin interface.
I've tried editing /etc/apache2/owncloud-webgui.d/default.conf and replacing the ServerName with cloud.example.com but that doesn't work (and thinking about it that's not right anyway.
owncloud-webgui seems to be pointing at port 8080 of the root:
and the included file seems to be pointing at the document root /var/www/owncloud
So why's Owncloud appearing at http://example.com/owncloud:80?
...actually, I can see in php-fcgi
which presumably is responsible for the subdirectory. But the port?
What I really want is for Owncloud to be visible to the world, and for OMV to only be visible inside my LAN. I can't see anything good coming from allowing the world to see my OMV admin login screen.
Any suggestions would be much appreciated.