Getting started in 3 steps

We'll describe how to get Collabora Online running on your server and how to integrate it into your Nextcloud using the docker image Nextcloud and Collabora built.


To install it the following dependencies are required:

  • A host that can run a Docker container
  • A subdomain or a second domain that the Collabora Online server can run on
  • An Apache server with some enabled modules (NGINX instructions in a blog here)
  • A valid SSL certificate for the domain that Collabora Online should run on
  • A valid SSL certificate for your Nextcloud

Note: This guide does NOT cover self-signed certificates. If you use a self-signed certificate then you're mostly on your own ;-)

Install the Collabora Online server

Setup using the built-in CODE server

Install the Collabora Online - Built-in CODE Server app from your Nextclouds apps management. This app provides a built-in server with all of the document editing features of Collabora Online. Easy to install, for personal use or for small teams. It is a bit slower than a standalone server and without the advanced scalability features.

Setup using docker

The collabora/code Docker image can be installed to any x86-64 host (e.g. on Linux and Windows 10), and it is fully configurable. For more information about setup and configuration for deployment, please read the CODE Docker page. If you want to try it out quickly, you can set up CODE docker image with file sharing integration in less than 5 minutes in a very basic way, following these instructions: quick tryout with Nextcloud.

The following steps will download the Collabora Online docker, make sure to replace "" with the host that your own Nextcloud runs on. Also make sure to escape all dots with double backslashes (), since this string will be evaluated as a regular expression (and your bash 'eats' the first backslash.) If you want to use the docker container with more than one Nextcloud, you'll need to use 'domain=cloud\.nextcloud\.com|second\.nexcloud\.com' instead. (All hosts are separated by |.)

docker pull collabora/code
docker run -t -d -p \
    -e 'domain=cloud\\.nextcloud\\.com' \
    --restart always \
    --cap-add MKNOD \

Optionally, you can select the dictionaries you want with:

        docker run -t -d -p -e 'domain=cloud\\.nextcloud\\.com' -e 'dictionaries=de en es ..' --restart always --cap-add MKNOD collabora/code

This way you are not only limited to German, English, Italian, French and Spanish.

That will be enough. Once you have done that the server will listen on "localhost:9980". Now we just need to configure the locally installed Apache reverse proxy.

Setup using packages

As an alternative to Docker image, Collabora provide native Linux packages for selected Linux distributions. If you have Debian 8, Debian 9, Ubuntu 16.04, Ubuntu 18.04, CentOS 7 or openSUSE Leap, please read the CODE Linux packages page.

Setting up a reverse proxy and SSL

It is highly recommended to set up a reverse proxy in front of CODE, either you run CODE from Docker, or you use native packages. It is easy, and this way CODE can be reached on standard HTTP or HTTPS ports. We provide sample configuration files for Apache2 and Nginx. If you want SSL, we recommend certificates from Let's Encrypt.

Now you can give as the WOPI URL in your preferred File Sync and Share solution. See below for specific examples.

Apache guide

On a recent Ubuntu or Debian this should be possible using:

apt-get install apache2
a2enmod proxy
a2enmod proxy_wstunnel
a2enmod proxy_http
a2enmod ssl

Afterward, configure one VirtualHost properly to proxy the traffic. For security reason we recommend to use a subdomain such as instead of running on the same domain. An example config can be found below:

<VirtualHost *:443>

# SSL configuration, you may want to take the easy route instead and use Lets Encrypt!
SSLEngine on
SSLCertificateFile /path/to/signed_certificate
SSLCertificateChainFile /path/to/intermediate_certificate
SSLCertificateKeyFile /path/to/private/key
SSLProtocol             all -SSLv2 -SSLv3
SSLHonorCipherOrder     on

# Encoded slashes need to be allowed
AllowEncodedSlashes NoDecode

# Container uses a unique non-signed certificate
SSLProxyEngine On
SSLProxyVerify None
SSLProxyCheckPeerCN Off
SSLProxyCheckPeerName Off

# keep the host
ProxyPreserveHost On

# static html, js, images, etc. served from loolwsd
# loleaflet is the client part of LibreOffice Online
ProxyPass           /loleaflet retry=0
ProxyPassReverse    /loleaflet

# WOPI discovery URL
ProxyPass           /hosting/discovery retry=0
ProxyPassReverse    /hosting/discovery

# Main websocket
ProxyPassMatch "/lool/(.*)/ws$" wss://$1/ws nocanon

# Admin Console websocket
ProxyPass   /lool/adminws wss://

# Download as, Fullscreen presentation and Image upload operations
ProxyPass           /lool
ProxyPassReverse    /lool

# Endpoint with information about availability of various features
ProxyPass           /hosting/capabilities retry=0
ProxyPassReverse    /hosting/capabilities

After configuring these do restart your apache using /etc/init.d/apache2 restart.

Configure the app in Nextcloud

Go to the Apps section and choose "Office & text" Install the "Collabora Online app" Admin -> Collabora Online -> Specify the server you have setup before (e.g. "")

Congratulations, your Nextcloud has Collabora Online Office integrated!

Updating the docker image

Occasionally, new versions of this docker image are released with security and feature updates. We will of course let you know when that happens! This is how you upgrade to a new version:

grab new docker image:

docker pull collabora/code

List docker images:

docker ps

from the output you can glean the Container ID of your Collabora Online docker image. stop and remove the Collabora Online docker image:

docker stop CONTAINER_ID
docker rm CONTAINER_ID

start the new image:

docker run -t -d -p -e 'domain=cloud\\.nextcloud\\.com' --restart always --cap-add MKNOD collabora/code