Zitat von "ryecoaaron"If you use the alias installer, you don't specify a port because it is running on the same port that the OMV web interface runs on. I didn't test running the alias script with https enabled. That may be the problem as well.
https shouldn't cause any trouble (at least it doesn't for me). If you look at the config files you see that OMV uses the same config for both port 80 and 443 and since you're just getting redirected to a folder and not a VirtualHost SSL should work if you have configured it in OMV.
Here is another thing some of you might like. I was fiddleing around with the Unix User Backend App and got it working. Here is how:
Step 1. Download, Extract and copy the plugin to your /var/www/owncloud/apps folder.
Step 2. Make sure permissions are correct e.g. if you used the script without folder redirection it would be owncloud:owncloud.
Step 3. Copy the recompiled pwauth file (see attachment) to any folder on your system. (/usr/bin/local/ is a good place for example)
Step 4. Creat a new group pwauth and put whatever user owncloud is running at in its members. (Again, it's either ownlcoud or openmediavault)
Step 5. Change the ownership of the pwauth file to the group you've just created. (e.g. chown :pwauth /usr/bin/local/pwauth)
Step 6. Set permissions on the pwauth file to 750
Step 7. Now log into your owncloud and activate the app, and then go to the admin page and change the path of the pwauth executable to where you put yours.
Step 8. Become a Jedi and join the Dark Side.
The pwauth file that is already on the system can only be executed by the www-data user or to be more percise, by the uid that was defind in the config.h file. Which is why it had to be recompiled in order for us to work. I left the uid undefiend while recompiling so it can be executed by the group that owns it.
The alternative would be to change all the web content to www-data. BUT, I tried that and it went horribly wrong.