![]() This will allow you to use Collabora with SSL provided by a reverse proxy (in this case Traefik). The following two parameters need to be set in the loolwsd.xml file on the host: The final docker-compose entry for Collabora: collabora: I also had to read the loolwsl.xml parameters from a file on the host, as it turned out the parameters I passed as env variables weren't being processed in the container. There is an undocumented option within Collabora's config file: true var/run/docker.sock:/var/run/docker.sock To be clear, I simply want to access Collabora CODE via HTTPS at within the framework of the following solution: version: '3.3' Collabora Online comes from the CODE edition (Collabora Office development edition). ![]() ![]() ![]() I believe the issue is the "extra_params=-o:ssl.enable=false" environment variable that I'm passing to the Collabora image, but I can't get Collabora to work with its own SSL enabled.ĭoes anyone know if there's a way to force Collabora to respond with HTTPS at all times?Īny help would be appreciated. Collabora Online will be automatically enabled in Nextcloud if the package nethserver-nextcloud is present when the virtual host is configured, otherwise you can enable with. Everything appeared to be up and running from this deployment, but whenever I try to access the Collabora CODE editor, I get the following "mixed content" error: Blocked loading mixed active content “” I am trying to install Collabora CODE alongside Nextcloud via docker-compose.
0 Comments
Leave a Reply. |