- Collabora code nextcloue 11 access denied install#
- Collabora code nextcloue 11 access denied update#
(To fix that, see below) $ mkdir nginx-proxy Before letting docker-compose start all the containers, there needs to exist a network_nf file, otherwise the nginx-proxy container will get an error. LETSENCRYPT_HOST= # change thisĪfter editing the file and changing the examples to your own data, save it. "domain=cloud\\.your-domain\\.tld" # change this (double Backslashes are important here) MYSQL_ROOT_PASSWORD=db_root_passwd # change this var/run/docker.sock:/var/run/docker.sock:ro Image: jrcs/letsencrypt-nginx-proxy-companion var/run/docker.sock:/tmp/docker.sock:ro opt/nextcloud/nginx-proxy/network_nf:/etc/nginx/network_nf Now inside the docker-compose.yml insert the following text and change all the annotated info with your own. To use docker-compose, there needs to be a docker-compose.yml describing what should be created. To check the installation: $ docker versionĪfter verifying that docker and docker-compose are installed, a folder in /opt needs to be created, that will contain the docker-compose.yml needed.
Collabora code nextcloue 11 access denied install#
To install Docker-Compose, download via curl to /usr/local/bin/docker-compose and make it executable with chmod +x: $ curl -L "$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
Collabora code nextcloue 11 access denied update#
To install Docker (on Ubuntu): $ apt update & apt upgrade -y With the Docker-Compose YAML-file specified here, you will automatically get the current version of Nextcloud, Collabora and nginx.Īt first we need Docker and Docker-Compose. Using Docker-Compose will also make configurations of nginx more easy, since its all done allready. In this process I will use Docker-Compose to get containers of Nextcloud, Collabora/CODE Server and the reverse Proxy nginx with LetsEncrypt for SSL certification up and running. So please let us know if you run into any issues and report them to our Github repo.With Docker and Docker-Compose you can quickly spin up all the important components of your own (self hosted) Cloud. Without your feedback it’s hard for us to know the errors and fix them. If you don’t find the Collabora script in the scripts folder of the VM, then get the latest version from Github: $~: sudo wget -P /var/scripts Please report issues When the VM is rebooted after the startup-script finished successfully, then run the Collabora script by typing: $~: sudo bash /var/scripts/collabora.sh
If you don’t have SSL on your cloud domain then just run the startup-script as usual and install SSL via Let’s Encrypt in the end of the startup-script. You also need to use SSL on the cloud domain prior to running the script. That means one domain for the Collabora docker () and one for your Nextcloud ().This is easily fixed by pointing your domain A-record to the server that will host Nextcloud / Collabora. There are some preparations though if you want it to work instantly when the VM is mounted for the first time and startup-script is run – you have to prepare your server with 2 domains, prior to running the script. So yesterday Daniel spent a whole day improving the script, and the result is: Collabora is no longer BETA! We consider it stable now, and as it’s downloaded via the startup-script in 11.0.1 already, it means that everyone that uses the current VM will get the stable Collabora script! Preparations But good in the same time, becuase the users that tried to install Collabora with the BETA version of the script, actually didn’t install anything at all so the VM didn’t get bloated becuase we added that check prior installing anything. It turned out that it didn’t work at all as one of the first checks was failing and aborted the script. A user posted a question on the Nextcloud forum about it and we started to investigate. In Nextcloud 11.0.1 we released the BETA version of the Collabora script and since we didn’t get any feedback we thought everything was good. When we first looked at it we scratched our heads and thought, how can we do this in the best and most secure way? There are a few things to think about the docker image, the proxying and checking that the user have setup the correct domains, also certain ports needs to be open. At Tech and Me we love to automate stuff to make tech easier, and this time it has come to the Collabora docker for Nextcloud, including the app.