![Collabora code port](https://kumkoniak.com/72.jpg)
![collabora code port collabora code port](https://user-images.githubusercontent.com/39572468/65376615-463e4280-dc5f-11e9-9c05-73d9ea9a2ee8.png)
Recently (a couple of months back but I did not have time to try it sooner) I discovered Collabora CODE. And with the death of the LibreOffice web project the dream for real productivity where you are the owner of your own data also died, or so I thought. Unfortunately this project was abandoned somewhere along the way and this amazing software never saw the light of day. This project aimed to run LibreOffice in a webbrowser, enabling all devices with a webbrowser to use this amazing piece of software.
![collabora code port collabora code port](https://help.nextcloud.com/uploads/default/original/3X/d/6/d63aef72a723b9a8e5d45b16fcc85e074e27dbfb.png)
![collabora code port collabora code port](https://help.nextcloud.com/uploads/default/original/3X/0/1/01ed017ee54514e17928ec4bc3f0b71edfee8b02.png)
Because of this it was not usable on Android, IOS and ChromeOS (and probably a number of other operating systems).Īround 2012 LibreOffice started a side project to solve this issue once and for all. LibreOffice is well known for its open source and free office solution unfortunately LibreOffice always needed to be installed on a Windows, Linux or MacOS operating system. Today I can tell you one of Microsoft’s competitors has made the same move, and its not Google. And you probably also know about Microsoft’s move to the cloud.
- This Caddy forum post seems to support my observations as it suggests that the Caddy error arises from an upstream server terminating a connection.If your reading this article, you probably know Microsoft office.
- Rather, the error is flagged when Collabora exits and returns control to Nextcloud and
- I noticed that saving a document within Collabora doesn't give rise to the error.
- There isn't any evidence of a problem in the Nextcloud and Collabora logs at around the time the issue is flagged by Caddy.
- There has not been any outwardly visible impact (such as file corruption) arising from the error in the weeks I've been trialling Nextcloud-Collabora integration.
- I'm tempted to ignore the error for several reasons: 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.