How will I know the Collabora server is working correctly, and I can proceed to step 5?Īfter a restart, it can take a few minutes for the Collabora server to reach a quiescent state. When configured in this manner, there should be no SSL errors in the server log.īuild and run Collabora CODE with Compose sudo docker-compose up -d. The Collabora server is placed behind the reverse proxy. A separate reverse proxy will provide certification services and TLS termination for Collabora. Note: By design, certification services are switched off in the Collabora container. Requesting address is denied: ::ffff:172.17.0.1| wsd/LOOLWSD.cpp:1971Īlter the highlighted entries to suit your environment.Collabora, Nextcloud 11, FreeNAS, Nginx.Setting up and configuring collabora/code Docker image.'extra_params=-o:ssl.enable=false -o:ssl.termination=true' Create the Compose file nano docker-compose.yml and paste the following: Step 4: Install Collabora using Docker ComposeĬhange to the home directory cd and create a directory for the Compose file mkdir collabora. Refer to the first three steps of the resource Nextcloud and OnlyOffice Integration. Note: For the purpose of explanation, the steps below assume that the Nextcloud FQDN is and for Collabora, it is. You may be able to cherry-pick from these steps if you already have some of the building blocks in place. Enable and configure the Collabora Online connector in Nextcloud.Set up the Collabora server behind the reverse proxy.Install Ubuntu with Docker and Docker Compose in a FreeNAS VM.Set up Nextcloud behind a reverse proxy.To realise this, a number of building blocks need to be put : Nextcloud and Caddy : Collabora configuration, Docker Compose This is a collection of notes on how to get Collabora Online Development Edition (CODE) working in Nextcloud behind a reverse proxy on FreeNAS. Collabora and OnlyOffice are popular office suite choices for Nextcloud.

Collabora online nextcloud no docker