Owncloud in kralizec

Hi all,

I got some issues using Owncloud after updating from 0.5.x to 1.0.7

A little background of issues and workarounds already applied.
The update wen almost fine, except some dependencies issues which forced me to uninstall all plugins to be able to do the upgrade.

After update, I tried to reinstalled OwnCloud plugin.
I got surprised to see that we now must use a certificate. OK, let's create one, OMV make this step easy, even if i'm not really a fan of self-signed certificate (because of the alert the browsers will display)
But after selectiong the certificate in owncloud config page, saving, and clicking "apply", I got a "An error occured" message without any details. but it saved the changes anyway.
Then tried to access myip/owncloud: i got a webdav error, that I have been able to solve following this thread: Owncloud missing WebDAV
So in general settings I activate SSL/TLS and select the newly created cetificate.
Then I save, and when I apply changes I also got a "an error occured" message without details.

The certificate is just /CN=192.168.1.43

I also create a share for owncloud of course.

After all of that, if i go to http://192.168.1.43/owncloud I got two issues:
First i got redirected to https://192.168.1.43:8443/, which will be an issue for external access (for exemple I won't be able to access from my office network).
Second issue is that the shares are not available in OwnCloud.

Just to be sure if it was an update issue or a bug, I tried to do a clean install on a VM, and faced the exact same problem.
So, did I missed something in this process?

Ok, I also got the workaround, thanks for giving me the way:
In Owncloud, click on Apps in the lower left corner, select External storage support and click enable.
Then go the the admin menu, the shares should be there.
To the developpers: isn't there a way to activate this plugin by default? i think lots of users will have the same issue.

Unfortunately, I still don't have a solution for the incorrect adress redirection. Maybe something to do with the reverse proxy settings in Nginx, but I'd rather have an specialist advice first

Hi tekkb,

Thank you for answering.

I modified the file as you asked, so I indeed have the "ownCloud Web Client" button in the config page.
But the issue is exactly the same than when I type the adresse manually: it redirects me to https://ipofomv:8443 instead of http(s)://ipofomv/owncloud.

Any way to correct that? Should I create an alias/reverse proxy setting manually?

I can open the 8443 port on my router. But the issue is that lots of networks (office, public wifi...) Do not allow outgoing connection on ports other than 80/443, so it won't be possible to connect through 8443, that's whyt i would be able to access it through port 80
It's a bit confusing as it was the default OMV behaviour previously

Anyway, I'll do the config manually, and detail the steps here if I manage to get it working. But I really suggest that you adress this behaviour in future versions
For exemple, a field "External domain(s)" in the OwnCloud setup page, that allows to configure 'trusted_domains' from the WebUI would be helpfull for non-CLI-savvy users. and eventually a button to create the reverse proxy settings?

Thanks for all your hard work, OMV is really an awesome system

OK, I almost got it working, but not completely yet

Warning: This is only tests and nobody should apply this until more verifications have been done. This is not a complete solution. And ther is a possibility that I forgot some steps...

Here are the steps (you'll need to know how to connect via SSH):

1- Create a new file for the proxy settings:
nano /etc/nginx/conf.d/proxy.conf
and paste the folllowing text in it:

proxy_redirect          off;
proxy_set_header        Host            $host;
proxy_set_header        X-Real-IP       $remote_addr;
proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
client_max_body_size    10m;
client_body_buffer_size 128k;
client_header_buffer_size 64k;
proxy_connect_timeout   90;
proxy_send_timeout      90;
proxy_read_timeout      90;
proxy_buffer_size   16k;
proxy_buffers       32   16k;
proxy_busy_buffers_size 64k;

2- Modify the owncloud.conf file:
nano /etc/nginx/openmediavault-webgui.d/owncloud.conf

and modify it to be like that:

Location /owncloud {
    proxy_pass   https://192.168.1.43:8443/;
}

Restart nginx:
service nginx restart

3. Edit config.php
nano /var/www/owncloud/config/config.php

Locate the trusted_domains area, and add the arrays corresponding to the adress you will connect from.
for exemple:

'trusted_domains' =>
array (
  0 => '192.168.1.43:8443',
  1=> '192.168.1.43/owncloud',
  2=> '192.168.1.43',
),

(I'm note completely sure that the "192.168.1.43/owncloud'," entry is necessary)

Then right after the ), line, add:

'overwritewebroot' => '/owncloud',

Now I am able to access owncloud from https://ipofomv/owncloud.
But I still have two problems:
- Access to apps seems to work, but navigating in the folders from the files menu doens't work. Also in apps not everything is working.
- access from http still redirects to https://ipofomv:8443/

I still have some things to try, but i won't be able to work on this until next monday or tuesday.