Variable DOCKER_EXPOSE_PORT should be left intact (80)Įxtra_params=-o:ssl. 0.0.1:9980:9980 -e 'domain
It's better to specify additional parameter -restart always in step 5 of Quick tryout with Nextcloud docker Before coping loolwsd.xml back to docker (step 3) you might need to chmod this file: chmod 666 loolwsd.xml We were able to fix this issue using the article Setting up and configuring collabora/code Docker image (Use the configuration file directly). Thus, DOCKER chain should look like this: iptables -L DOCKER -vnt nat This access is done internally via the docker private network with the hostname. LibreOffice must be able to access the wopi-app. Note we are running two services wopi-app on port 8080 and LibreOffice on 9980. You can get the collabora docker image from here. 172.21.0.2 - IP you get while performing iptables -L DOCKER -vnt nat Collabora is the community mainly developing the LibreOffice Online code. Then, edit mapping and specify Private Port equal to Public Portįurther, inside container add NAT rule, like: iptables -t nat -A DOCKER ! -i docker0 -p tcp -m tcp -dport 11010 -j DNAT -to-destination 172.21.0.2:9980 In this case, you can left only internal IP and make mapping as you did. So, in the settings of "Collabora online" you have to specify URL and remove mapping.Īnother way is a mapping trick. This can be easily overcome by adding of External IP. In other words, telnet $(hostname) 11010 says "connection refused" inside container since mapping works correct only from the Internet. This Caddy forum post seems to support my observations as it suggests that the Caddy error arises from an upstream server terminating a connection.We think the main reason of the issue is the fact that port mapping doesn't work in your case.Rather, the error is flagged when Collabora exits and returns control to Nextcloud and Its basically the LibreOffice interface in a web-browser. I noticed that saving a document within Collabora doesn't give rise to the error. Collabora Online Development Edition (or 'CODE'), is the lightweight, or 'home' edition of the commercially-supported Collabora Online platform.It.Collabora Online is now ready to use Share on Facebook Share on Twitter Share on Linkedin Share on Reddit.
#COLLABORA CODE PORT INSTALL#
So, I'm happy to deal with it in this discussion area (though I'd still like to bring it to the attention of as it is Caddy flagging the error). I was going to suggest that you repost this in the Caddy discussion area, but the more I looked into this, the more I felt the Caddy error was due to the behaviour of Collabora within the Nextcloud environment. I hadn't noticed this error before, but it does appear in my Caddy log as well. Click to expand.Thanks for pointing this out.