Hi there!
I was using OMV 0.5 and set up ownCloud on there (never really used it, but I installed and configured it using the web gui).
When I tried to update to OMV 1.0, it failed because of ownCloud. Thanks to the posts here I figured out how to get rid of ownCloud and finaly was able to successfully update OMV. Now I am using 1.9 and just installed ownCloud again.
Here is what I did back then:
382 apt-get update
383 apt-get dist-upgrade
384 omv-update
385 omv-release-upgrade
386 echo $?
387 vi upgrade-failures.txt
388 reboot
389 exit
390 uname -a
391 uptime
392 omv-mkconf nginx
393 omv-mkconf php5fpm
394 service apache2 stop
395 service php5-fpm restart
396 service nginx restart
397 apt-get -f install
398 apt-get autoremove
399 apt-get remove openmediavault-owncloud
400 apt-get -f install
401 omv-mkconf nginx
402 omv-mkconf php5fpm
403 service nginx restart
404 rm -f /etc/nginx/sites-enabled/openmediavault-owncloud
405 apt-get -f install
406 omv-mkconf nginx
407 service nginx restart
Alles anzeigen
Now I have the following problem:
When I try to enable the service using the OMV web gui, it just says "An error has occured". The enable check stays, but when I try to disable -> same thing.
The configured portnumber is 8443 (which is not open). When I go to http://mynas/owncloud it forwards me to https://mynas (which does not work as port 443 is not open).
I guess /etc/nginx/sites-enabled/openmediavault-owncloud should be a link to /etc/nginx/sites-available/openmediavault-owncloud. But neither of them does exist. Which package should bring the file in the available folder?
I tried to remove owncloud and reinstall it (using the gui and bash). -> does not help
Is there more trace somewhere, to find out why "An error has occured"?
Cheers,
Robert