Bungy

Yeah, i've seen that before. You need to set up your owncloud container to serve the static files on /owncloud. Add or edit these lines in your config.php file 'overwritewebroot' => 'owncloud', 'overwrite.cli.url' => 'https://server.com/owncloud', Then reboot the owncloud container and you should be good to go.

My config is quite a bit different from yours. Looking at the error.log file for your apache container should help. This should be exposed in the volume mount for your apache container (/config). Try changing: ProxyRequests Off ProxyPreserveHost Off ProxyPass / https://192.168.178.28:8000/ ProxyPassReverse / https://192.168.178.28:8000/ To: LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so <Location /> ProxyPass http://192.168.178.28:8000/ ProxyPassReverse http://192.168.178.28:8000/ </Location> Note: If you're using the official owncloud container, you should point to http instead of https as changed above. I'm in the process of changing my reverse proxy over to nginx reverse proxy by jwilder since it has auto-generation of configuration. You may want to take a look at that as well (https://github.com/jwilder/nginx-proxy).

Nice! Yeah I switched to Hass about two months ago and never looked back. I found its much more stable and I like developing in python way more than java.

Currently, openhab has been lacking updates because I'm no longer using it. Also, it's a nightmare of a docker/enviornment to set up, so I dread having to update it. I'll work on pushing an update soon.

Yeah sorry about that. I'll update the template to point to the right container repo. That docker is extremely beta - I couldn't get it to work well and abandoned it. I haven't touched it in months so proceed with caution.

The official owncloud container does not have HTTPS built in. I would recommend setting up a reverse proxy using linuxserver.io's apache container. You'll have to add https to the reverse proxy container and have that container forward requests to your owncloud container.

Instead of entering the docker, edit your config file from your host. The file is likely located somewhere like /mnt/cache/appdata/owncloud/config/config.php. Then simply restart the docker and you should be good to go.

# To enter the docker shell docker exec -it owncloud bash # To show the contents of the config.php file cat config/config.php # To check the permissions of config.php file ls -l config/config.php

I think I ran into this issue as well and fixed it by manually editing the config.php file. Can you check what the trusted_domains array is in your config.php file and also the permissions of this file?

I used to use openhab but switched to home assistant lately. It's much less buggy and easier to develop on. Im not sure about that specific device being supported but openhab definitely has extensive support for zwave in general.

Hmm. I just updated my gitlab docker after seeing your and I'm not seeing the same thing. It sounds like something is going wrong with your gitlab template or with your docker image. Can you check how much free space your docker image has? You can see this on the dashboard view in unraid.

Are you seeing this during the update or in the docker logs for the gitlab docker?

I believe I've seen that before and simply restarting the docker fixed it. It would help to show the contents of that file as well

Is there anything in your docker logs?

I'm pretty sure they won't unless they start from scratch. The updates pull from the running containers link to the registry and remaking the containers is typically done using the users local cache of the templates

Will do. I refrained since others are already using l3iggs but I'll update the template

I've actually switched away from l3iggs container to the official owncloud container. I found it has less bugs

chmod -R 0770 data

No problem! Happy to help

Give it a few seconds and try the second command again. Sounds like the container is still booting up. I ran in to the same issue.

Dockers are pretty finicky and getting used to them at first can be difficult. I've often start by configuring the minimum amount of settings I need to going and then building from there. Try those two commands I just sent you. They don't include the volume mappings. You may have to wait like 30 seconds after the first one while the docker boots up before you get the 2nd one to work properly. If they work, then you can add the volume mappings in and see if you can get everything up and running. The syntax for volume mappings is -v [host_directory]:[container_directory] Hang in there. Dockers are a HUGE pain at first, but will end up being your best friend once you learn more about how to use them.

So what that command is doing is creating a 2nd mysql docker and trying to connect othe the first one with it. My guess is the permissions table on your docker isn't allowing connections from anywhere but 127.0.0.1, but the ip address of your new temporary docker is 172.17.42.1. Try this instead: # This will get you into the shell of the mysql docker docker exec -it mysql bash mysql -u root -p # Then enter your password Give that a shot and let me know how it works for ya. Here's the result, I have gotten similar results with HeidiSQL, same error that is. root@HORTA-unRaid:~# docker exec -it mysql bash root@4c46fbbf6f82:/# mysql -u root -p Enter password: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES) root@4c46fbbf6f82:/# I just tried it out on my machine and it works. First command to initiate the mysql container: docker run --name some-mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql 2nd command to connect to the mysql instance: docker run -it --link some-mysql:mysql --rm mysql sh -c 'exec mysql -hmysql -uroot -pmy-secret-pw'

So what that command is doing is creating a 2nd mysql docker and trying to connect othe the first one with it. My guess is the permissions table on your docker isn't allowing connections from anywhere but 127.0.0.1, but the ip address of your new temporary docker is 172.17.42.1. Try this instead: # This will get you into the shell of the mysql docker docker exec -it mysql bash mysql -u root -p # Then enter your password Give that a shot and let me know how it works for ya.

The proper way to include your own certificate files are to put them inside of a directory and map that directory to /https in the container. Other then that, are there any files popping up in your configuration directory? Also can you post which volumes you're mapping?

Where would one go for your own certs? How would one install said certs? Check out section 4 of the docker container author's instructions: https://github.com/l3iggs/docker-owncloud