December 6, 20187 yr 2 minutes ago, Squid said: sorry, now I get it, but still no access. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='ownCloud' --net='br0' --ip='192.168.1.25' --cpuset-cpus='0,1,2,3,4,5,6,7' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'TCP_PORT_443'='443' -e 'PUID'='99' -e 'PGID'='100' -e 'DB_PASS'='owncloud' -v '/mnt/user/appdata/ownCloud/data':'/data':'rw' -v '/mnt/user/appdata/ownCloud':'/config':'rw' --log-opt max-size=50m --log-opt max-file=1 'dlandon/owncloud' a86eff774d57772e65e06894f5d53647b386711251fa28d68819075d99f60cf1 The command finished successfully!
December 6, 20187 yr Just now, cracksilver said: sorry, now I get it, but still no access. Your original problem was that there was an orphan. Since that's now solved, I'm letting dlandon take over.
December 6, 20187 yr 1 minute ago, Squid said: Your original problem was that there was an orphan. Since that's now solved, I'm letting dlandon take over. What does orphan mean? Is there somethin broken in the image? What the best way to solve, just reinstall plugin with the same name? thx
December 6, 20187 yr 1 hour ago, Squid said: An orphaned image only happens when an error occurs on the docker run. IE: the container cannot execute because you've made a mistake somewhere in entering values on the template. Usual cause is re-using a port that's already in use et al.
December 6, 20187 yr Author 21 minutes ago, cracksilver said: What does orphan mean? Is there somethin broken in the image? What the best way to solve, just reinstall plugin with the same name? thx Start over. Remove the docker image and any orphans. Delete the appdata/owncloud folder. Use CA to find the docker and apply the default template. Don’t make any changes.
December 6, 20187 yr 10 minutes ago, dlandon said: Start over. Remove the docker image and any orphans. Delete the appdata/owncloud folder. Use CA to find the docker and apply the default template. Don’t make any changes. Did it. Same game. Shall I delete everything including DB and start again?
December 6, 20187 yr Author 12 minutes ago, cracksilver said: Did it. Same game. Shall I delete everything including DB and start again? Yes. Deleting the appdata folder removes everything. Show me a screen shot where you see the error.
December 6, 20187 yr Quote 2 minutes ago, dlandon said: Yes. Deleting the appdata folder removes everything. Show me a screen shot where you see the error. thats what I did before... still not reachable..
December 6, 20187 yr Author 13 minutes ago, cracksilver said: thats what I did before... still not reachable.. That's a connection refused message. That will occur if you try to access ownCloud with http:// which is what the nginx log showed earlier. If you look at the address bar you should see a lock or https:// indicating secure access. ownCloud refuses a http:// connection. It has to be https://. What shows when you click on the "DETAILS" button? Try another browser or computer. I suspect a browser issue.
December 6, 20187 yr I'm probably too stupid. I don't know anymore.... I set the network settings of my Unraid server (HP Gen8) on just one interface. No bridging, no bonding. Just standard, no extras. All other containers are reachable. Tried everything out. Bridge, Host, Custom-eth0. Same issue again. Strangely, the installation via the WebGUI worked last night. Today when reinstalling I never had access to the WebGUI. Even after deleting all app data, browser cache and so on.
December 6, 20187 yr Like a wonder, after trying again.... I'm having fun again... bammmmm!!! like a hammer in the face:
December 6, 20187 yr Author 15 minutes ago, cracksilver said: Like a wonder, after trying again.... I'm having fun again... bammmmm!!! like a hammer in the face: I don’t remember the :443 on the database ip address. Did you add that?
December 6, 20187 yr Author 10 minutes ago, cracksilver said: i really don't know, where exactly do you mean? Change the 172.17.0.2:443 to 'localhost'. Like this:
December 6, 20187 yr tried yesterday. Try it again.... Just finished a new installation. See log attached. May be you can find something wrong... install_log.rtf
December 6, 20187 yr It is unbelievable. I'M IN THE WEBGUI FROM OWNCLOUD !!!! That "localhost" was wrong. But yesterday get an error with that. After that I allways wrote the IP with Port there... Thank you VERY MUCH for not giving up with me !!! Wish you a good day/night, wherever you are at home i'm from Switzerland. cracksilver
December 6, 20187 yr Author 2 minutes ago, cracksilver said: It is unbelievable. I'M IN THE WEBGUI FROM OWNCLOUD !!!! That "localhost" was wrong. But yesterday get an error with that. After that I allways wrote the IP with Port there... Thank you VERY MUCH for not giving up with me !!! Wish you a good day/night, wherever you are at home i'm from Switzerland. cracksilver Glad you finally got it going. I hail from the US.
December 10, 20187 yr Howdy, I stumbled upon this docker after gjlm's was depreciated. In looking to stand this one up, I was able to get the docker running, configured, etc and pointed the data file to a user share. However, when I go to R/W from that folder, it seems the docker doesn't have permissions. Is there a way to fix? A bit of a linux noob, but can make my way around a command line.
December 10, 20187 yr 28 minutes ago, Gordo74 said: Howdy, I stumbled upon this docker after gjlm's was depreciated. In looking to stand this one up, I was able to get the docker running, configured, etc and pointed the data file to a user share. However, when I go to R/W from that folder, it seems the docker doesn't have permissions. Is there a way to fix? A bit of a linux noob, but can make my way around a command line. Figured out the issue. There was some legacy locked files causing the issue. Recreating all from scratch worked. Thank you!
January 13, 20197 yr Author I have made an adjustment in system parameters to improve the performance of redis. Unfortunately the only way to apply the change is through a command line parameter. This means I had to change the docker template. There are two ways to make the change: - Go to CA and search for ownCloud and apply the default settings and make any changes necessary to your situation. - Switch to the Advanced VIew and append the following to the Extra Parameters Field. --sysctl=net.core.somaxconn=511 Edit: Seems there were also a few other system settings that needed to be set to fix the Redis performance issues that can't be set this way. I'm issuing an update of the docker that will handle the settings internally, but the docker has to be run 'Privileged' in order for them to take effect. When an update shows up, edit your template and remove the '--sysctl=net.core.somaxconn=511' from the 'Extra Parameters' and turn on the 'Privilege' setting. Edited January 13, 20197 yr by dlandon
January 17, 20197 yr On 12/6/2018 at 6:01 PM, dlandon said: The WebUI port has to be 443. Http:// access is denied. You can only use https://. I'm trying to set up owncloud behind my traefik and I can't seem to get it to work. Could you maybe help me out? Owncloud is running fine when opened inside my network over port 8443, but when I try to open it through my domains subdirectory I get "400 Bad Request The plain HTTP request was sent to HTTPS port" The reason is obvious, traefik tries to reach owncloud over http but I have no idea how to change that. I thought I could just set owncloud to use http, but now you say that is not allowed, so what else can I do? If I add traefik.protocol=https I get "Internal Server Error" and the traefik log says "caused by: x509: cannot validate certificate for 172.17.0.2 because it doesn't contain any IP SANs"" I'm fairly new to docker/linux/unraid and I'm a little out of my depth now. Edited January 17, 20197 yr by shrtrnd
January 18, 20197 yr Author 3 hours ago, shrtrnd said: f I add traefik.protocol=https I get "Internal Server Error" and the traefik log says "caused by: x509: cannot validate certificate for 172.17.0.2 because it doesn't contain any IP SANs"" The ownCloud certificate is self signed and traefik does not like it. You need to get a valid certificate. Try Lets Encrypt. They offer valid certificates for free.
January 18, 20197 yr 6 hours ago, dlandon said: The ownCloud certificate is self signed and traefik does not like it. You need to get a valid certificate. Try Lets Encrypt. They offer valid certificates for free. Like I said, I'm fairly new to all of this, could you be a little bit more specific? My traefik already has a certificate for the communication to the outside world. I have that configured in my traefik toml and it works for pretty much everything else (sonarr, radarr, nzbget etc.). But all of these communicate with treafik on http so they don't need an extra certificate. As you said, owncloud forces https, so I would need to create an extra certificate just for owncloud? How would I do that? Use another docker with letsencrypt? Sorry if these are stupid questions, but I'm used to working with windows servers Edit: I found this (https://github.com/containous/traefik/issues/3906#issuecomment-422848924) about the issue and tried "traefik.frontend.auth.forward.tls.insecureSkipVerify=true" for the owncloud docker. That seems to have "fixed" the issue for now (I know it's not a real fix, I'm using that just for testing purposes), but now I have a new problem, the page is completely empty. Probably an issue with the subdirectory or something. Do I need to configure anything special in regards of subdirectories? This is the traefik error log: "Error calling . Cause: Get : unsupported protocol scheme \"\"" Here are my settings for owncloud Edited January 18, 20197 yr by shrtrnd
January 18, 20197 yr Author 4 hours ago, shrtrnd said: Like I said, I'm fairly new to all of this, could you be a little bit more specific? My traefik already has a certificate for the communication to the outside world. I have that configured in my traefik toml and it works for pretty much everything else (sonarr, radarr, nzbget etc.). But all of these communicate with treafik on http so they don't need an extra certificate. As you said, owncloud forces https, so I would need to create an extra certificate just for owncloud? How would I do that? Use another docker with letsencrypt? Sorry if these are stupid questions, but I'm used to working with windows servers Edit: I found this (https://github.com/containous/traefik/issues/3906#issuecomment-422848924) about the issue and tried "traefik.frontend.auth.forward.tls.insecureSkipVerify=true" for the owncloud docker. That seems to have "fixed" the issue for now (I know it's not a real fix, I'm using that just for testing purposes), but now I have a new problem, the page is completely empty. Probably an issue with the subdirectory or something. Do I need to configure anything special in regards of subdirectories? This is the traefik error log: "Error calling . Cause: Get : unsupported protocol scheme \"\"" Here are my settings for owncloud You probably would be better off getting support from traefik support forum. What is it you are trying to accomplish with traefik? Seems like a lot of work.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.