I have this up and running.  Is there anyway to access it without typing the port number?  I have my domain allowed in the config but I still have to type :8000 afterwards.  If I don't, unRaid picks up at port 80 and requests me to login to the server.  In theory I'd like to be able to type cloud.mydomain.com and go directly to my owncloud.  Thanks in advance for your patience as I'm sure it's very elementary for most of you.

 

I'm no expert but if you want that, you will need to change unraid default port to something else.

 

Don't change the unRAID default port.  It is not a good answer.

Thank you for your replies.  Do I need to do anything in the config.php to get it to listen on 443? 

I actually got it working by having 443 mapped to 8000 on the unRAID IP address.  Now if I type http://cloud.mydomain.com it goes to the unRAID login vs the owncloud login.  Is there a way to have it automatically go to https rather than having to type it.  I'm thinking of my wife who will probably just type cloud.mydomain.com and forget to use https.

 

Thank you for your replies.  Do I need to do anything in the config.php to get it to listen on 443?

No.  It's set up for 443 for security and listens on 443.

I actually got it working by having 443 mapped to 8000 on the unRAID IP address.  Now if I type http://cloud.mydomain.com it goes to the unRAID login vs the owncloud login.  Is there a way to have it automatically go to https rather than having to type it.  I'm thinking of my wife who will probably just type cloud.mydomain.com and forget to use https.

 

No.  The https:// directs it to port 443.  Without it it goes to port 80.

 

Set up a bookmark in your browser and you're set.  Just click on the bookmark.

I actually got it working by having 443 mapped to 8000 on the unRAID IP address.  Now if I type http://cloud.mydomain.com it goes to the unRAID login vs the owncloud login.  Is there a way to have it automatically go to https rather than having to type it.  I'm thinking of my wife who will probably just type cloud.mydomain.com and forget to use https.

You can set up a reverse proxy.

Everything you asked is doable using this way.

Check pages 15 onwards in this thread...

Is there a way to have the app data separate from the user data?

 

I use a cache drive for all my docker app files and that drive has limited space. 

Ideally I'd have the app files installed at /mnt/user/Dockers/Owncloud (excluded from the array) and my cloud files would be in my user share at /mnt/user/Media/Owncloud.

 

Owncloud quit working for me today, so I saw there was an update, so I installed it.  Now it won't even start.  If I look at the syslog I see:

 

Nov  2 18:31:10 tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'start' 'ownCloud'

Nov  2 18:31:10 tower kernel: device veth86c5d74 entered promiscuous mode

Nov  2 18:31:10 tower kernel: docker0: port 2(veth86c5d74) entered forwarding state

Nov  2 18:31:10 tower kernel: docker0: port 2(veth86c5d74) entered forwarding state

Nov  2 18:31:10 tower avahi-daemon[2740]: Withdrawing workstation service for vethf3d9038.

Nov  2 18:31:10 tower kernel: docker0: port 2(veth86c5d74) entered disabled state

Nov  2 18:31:10 tower kernel: eth0: renamed from vethf3d9038

Nov  2 18:31:10 tower kernel: docker0: port 2(veth86c5d74) entered forwarding state

Nov  2 18:31:10 tower kernel: docker0: port 2(veth86c5d74) entered forwarding state

Nov  2 18:31:11 tower kernel: vethf3d9038: renamed from eth0

Nov  2 18:31:11 tower kernel: docker0: port 2(veth86c5d74) entered disabled state

Nov  2 18:31:11 tower kernel: docker0: port 2(veth86c5d74) entered disabled state

Nov  2 18:31:11 tower avahi-daemon[2740]: Withdrawing workstation service for vethf3d9038.

Nov  2 18:31:11 tower avahi-daemon[2740]: Withdrawing workstation service for veth86c5d74.

Nov  2 18:31:11 tower kernel: device veth86c5d74 left promiscuous mode

Nov  2 18:31:11 tower kernel: docker0: port 2(veth86c5d74) entered disabled state

 

 

Any ideas what happened?

 

david

Wondering if this is working for anyone else?  I just removed the docker and re-installed with the same results.

 

thanks,

david

Still working for me. Im running the latest version as well

Well I finally got around to rebooting the server and now everything works.

 

Seems I needed to take a microsoft approach to my UnRaid issue

 

david

Was doing some ownCloud maintenance (installing an SSL certificate), when I noticed there's an upgrade for it. I installed the upgrade, and now it won't load. I've already rebooted the physical server.

 

The docker starts, but when I try to visit the website, it just tells me "Unable to connect". None of the clients connect either.

 

I can't even find a log file for this to check what could be wrong.

 

This is my log, which doesn't indicate anything wrong as far as I can tell:

Nov 8 13:15:01 winserver kernel: UnRAIDBridge: port 3(vnet0) entered forwarding state

Nov 8 13:15:08 winserver kernel: UnRAIDBridge: port 5(vnet2) entered learning state

Nov 8 13:15:12 winserver kernel: UnRAIDBridge: topology change detected, propagating

Nov 8 13:15:12 winserver kernel: UnRAIDBridge: port 4(vnet1) entered forwarding state

Nov 8 13:15:23 winserver kernel: UnRAIDBridge: topology change detected, propagating

Nov 8 13:15:23 winserver kernel: UnRAIDBridge: port 5(vnet2) entered forwarding state

Nov 8 13:19:34 winserver emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog

Nov 8 13:20:06 winserver php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'restart' 'ownCloud'

Nov 8 13:20:06 winserver kernel: vethd81ab33: renamed from eth0

Nov 8 13:20:06 winserver kernel: docker0: port 1(veth98d8a8b) entered disabled state

Nov 8 13:20:06 winserver kernel: docker0: port 1(veth98d8a8b) entered disabled state

Nov 8 13:20:06 winserver avahi-daemon[11219]: Withdrawing workstation service for vethd81ab33.

Nov 8 13:20:06 winserver avahi-daemon[11219]: Withdrawing workstation service for veth98d8a8b.

Nov 8 13:20:06 winserver kernel: device veth98d8a8b left promiscuous mode

Nov 8 13:20:06 winserver kernel: docker0: port 1(veth98d8a8b) entered disabled state

Nov 8 13:20:06 winserver kernel: device veth89c0aff entered promiscuous mode

Nov 8 13:20:06 winserver kernel: docker0: port 1(veth89c0aff) entered forwarding state

Nov 8 13:20:06 winserver kernel: docker0: port 1(veth89c0aff) entered forwarding state

Nov 8 13:20:06 winserver avahi-daemon[11219]: Withdrawing workstation service for veth0479f76.

Nov 8 13:20:06 winserver kernel: docker0: port 1(veth89c0aff) entered disabled state

Nov 8 13:20:06 winserver kernel: eth0: renamed from veth0479f76

Nov 8 13:20:06 winserver kernel: docker0: port 1(veth89c0aff) entered forwarding state

Nov 8 13:20:06 winserver kernel: docker0: port 1(veth89c0aff) entered forwarding state

Nov 8 13:20:21 winserver kernel: docker0: port 1(veth89c0aff) entered forwarding state

Nov 8 13:20:36 winserver php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php

 

To clarify, the SSL certificate installation went great. I had that up and running for a few hours before I noticed and initiated the update to ownCloud.

 

Any suggestions? Thanks.

 

 

The newest update broke owncloud for me. I can't access the webpage anymore just says err connection refused. Restarting the docker or unraid makes no difference and the log file doesn't contain anything of interest.

The newest update broke owncloud for me. I can't access the webpage anymore just says err connection refused. Restarting the docker or unraid makes no difference and the log file doesn't contain anything of interest.

 

Just updated my test server to see what would happen and you are right.  Not working.

The newest update broke owncloud for me. I can't access the webpage anymore just says err connection refused. Restarting the docker or unraid makes no difference and the log file doesn't contain anything of interest.

 

Just updated my test server to see what would happen and you are right.  Not working.

 

It did finally start, but I don't know what I did to get it going.  I was messing around in the docker looking around and then it just started.  It kind of looks like nginx was not starting.

finally, just got the update in the Docker page of Unraid GUI.  I did the Update.  Then Not connecting.  Now it finally connects after some time, by it says there is an update on the login page.  Clicking on the Start Upgrade doesn't work. 

 

Everytime there is a owncloud update... that breaks it.  I should just stop updating it

 

tried to go inside the docker to launch the update manually... will retry after changing ownership of "occ" to root

 

EDIT : 

 

It worked.  If you get the Upgrade page not working, you can go inside the running docker (in a SSH session) :

 

docker exec -it ownCloud bash

Assuming that your container is called ownCloud

 

Then, when inside it, go to the owncloud folder :

 

cd /var/www/owncloud

 

Then, change owner + execution on couple of files :

 

su root
chown root:root occ
chown root:root ./config/config.php
chmod +x occ

 

Then run the updgrade :

 

./occ upgrade

 

At that point, wait for it to complete (it took 5 minutes on my server).

 

Dont forget to set back the permission and owner to nobody:users.:

 

chown nobody:users occ
chown nobody:users ./config/config.php
chmod -x occ

 

That's it, just type "exit" and your done.  Now the login page will display the usual login page instead of the "update available" page.

The newest update broke owncloud for me. I can't access the webpage anymore just says err connection refused. Restarting the docker or unraid makes no difference and the log file doesn't contain anything of interest.

 

Just updated my test server to see what would happen and you are right.  Not working.

 

It did finally start, but I don't know what I did to get it going.  I was messing around in the docker looking around and then it just started.  It kind of looks like nginx was not starting.

 

Yes mine is now working too but it took at least an hr to get going. Strange.

It took me two tries to get the update to work from the webgui.

It took me two tries to get the update to work from the webgui.

 

Tried at least 6-7 times before going deep inside the docker and do it manually.

Owncloud updates have been troublesome lately.  I updated my test server, but I'll hold off for a while on my main server.  I count on owncloud for my business and can't have down time.  I wish there was a rollback process on docker updates.

The newest update broke owncloud for me. I can't access the webpage anymore just says err connection refused. Restarting the docker or unraid makes no difference and the log file doesn't contain anything of interest.

 

Just updated my test server to see what would happen and you are right.  Not working.

 

It did finally start, but I don't know what I did to get it going.  I was messing around in the docker looking around and then it just started.  It kind of looks like nginx was not starting.

 

I've added Diffie-Hellman parameters to increase security. The fist time you install/update, it will took some time (5-15 minutes) to generate the DH file, and then nginx gets executed.

Updated my main server and no issues after waiting a bit before trying to update through the webgui.

 

EDIT: It is recommended that add on apps like calendar and contacts be disabled before updating.

The newest update broke owncloud for me. I can't access the webpage anymore just says err connection refused. Restarting the docker or unraid makes no difference and the log file doesn't contain anything of interest.

 

Just updated my test server to see what would happen and you are right.  Not working.

 

It did finally start, but I don't know what I did to get it going.  I was messing around in the docker looking around and then it just started.  It kind of looks like nginx was not starting.

 

I've added Denavit–Hartenberg parameters to increase security. The fist time you install/update, it will took some time (5-15 minutes) to generate the DH file, and then nginx gets executed.

 

You mean Diffie-Hellman :-)

Any changelog to the ownCloud docker update?

Was cron support added ?

Maybe Redis  ? 

 

Thanks

 

You mean Diffie-Hellman :-)

 

Yep, that one!