Issue installing Collabora following official guide

[X4LD1M0]

@bomo I didn’t switch. I kept the OS to Debian 8.5. The thing I did was:

1. Install docker (which went to default AUFS)
2. Install Collabora

Outcome: failed stating permission errors

3. Delete /var/lib/docker/* and created only /var/lib/docker/overlay
4. Install Collabora

Outcome: failed stating permission errors

5. Delete /var/lib/docker/* and created again /var/lib/docker/aufs
6. Install Collabora

Outcome: Working Collabora

I am unclear why it worked when I switched back to AUFS, since all other directories were removed and a clean install of Collabora was done again.

[hans]

Hello Remidebette,
thank you very much for your fast help with the copying of the certificate!
I had to spend quite some time to get my SSL certificates working correctly (it turns out the OpenSSL client used by the app is more picky about the intermediate certificates, than the normal web-browsers), but now it works.

Kind Regards,
Hans

[lebernd]

Did this change something to permissions of /var/lib/docker/aufs ? My permissions are root:root 700

[X4LD1M0]

It seems I am lying. It isn’t using AUFS but using devicemapper:

root@portal:/var/www/nextcloud# ls -l /var/lib/docker/
total 32
drwx------ 5 root root 4096 Aug 15 13:11 containers
drwx------ 5 root root 4096 Aug 12 20:22 devicemapper
drwx------ 3 root root 4096 Aug 12 20:19 image
drwxr-x--- 3 root root 4096 Aug 12 20:19 network
drwx------ 2 root root 4096 Aug 12 20:19 swarm
drwx------ 2 root root 4096 Aug 12 20:24 tmp
drwx------ 2 root root 4096 Aug 12 20:19 trust
drwx------ 2 root root 4096 Aug 12 20:19 volumes

[PaoloVecchi]

I finally managed to get NextCloud-Collabora/Code working on Jessie.
The official guide is absolutely fantastic, thanks guys, but need to add a note as (today) Docker aufs on Jessie has got issues so devicemapper should be used instead.

Once I switched to devicemapper got to the following issue described by @jospoortvliet :

wsd-BLA ~DocumentBroker [https://cloud.josandcamila.com/apps/richdocuments/wopi/files/3610765?access_token=W7hLlzliRy7FYYY9BIqE3WTiBUoqgcMh] destroyed with 0 sessions left.

After much pain and testing I rechecked also NextCloud configuration to find that “overwrite.cli.url” was set to http instead of https, Added the “s” and it loaded the documents flawlessly.

[cxx]

I also had the problem

[ loolkit ] link("/opt/collaboraoffice5.1/CREDITS.fodt","/opt/lool/child-roots/1032/lo/CREDITS.fodt") failed. Exiting. (errno: Operation not permitted)

I changed the permissions of the files to belong to lool:lool (uid 105 gid 108), but I did it for all the files below /opt/collaboraoffice5.1.
Now this error is gone and I run into another error.

mknod(/opt/lool/child-roots/1973//dev/random) failed. (errno: Operation not permitted)

I think this is because I changed permisisons too generously. I don’t have any more time today maybe someone wants to fiddle it out or I will try tomorrow

[lebernd]

I can answer the question about different portnumbers now. Putting the portnumber in several ways after the domainname didn’t work. So I’ve added --expose <portnumber> to the line from the docs and it is running

The solution with --devicemapper is not optimal I think as long as https://github.com/docker/docker/issues/15629#issuecomment-238178503
is still true. I don’t get the thin provisioning on a dedicated device working on debian 8.

[Cult]

Is there a way to specify more than one Nextcloud hosts/domains to be accepted when starting the docker container ?

[LEDfan]

Please have a look at Allow several domains for Collabora?

[Nemskiller]

Hey Pupaxxo, i have the same problem, could you please tell me on what file exactly you change this line ?
Thank you in advance.

EDIT : Here is the answer of @pupaxxo :
I edited this file apps/richdocuments/controller/documentcontroller.php
adding this line $token = str_replace("?encoding=text", “”, $token); after the token variable declaration

So i done that then i got an error in docker : wrong permission.

So i had to edit /etc/default/docker and to add this line :
DOCKER_OPTS="–storage-driver=aufs"
(Be sure to have Linux Extra image installed apt-get install linux-image-extra-$(uname -r) )
Made a reboot, rebuild the docker image and it’s working now.

[Insan3]

Hi,

I have succesfully installed collabora but for some reasin it is extremely slow. It takes about 20 seconds to open a document. In the docker log I can find anything that might be the problem. Maybe someone else can see it?

I have put the log here since it is to big to put in the code tags.

[lebernd]

There is already a thread, yes 20 seconds (don’t be too excited about the ‘solved’ tag)

Collabora "connecting" delay for 20 seconds

I’ve setup two VM’s - one running Nextcloud 9.0.52 and the other running the docker image for Collabora Online. I’ve set it up as per the online documentation. Both servers have real SSL certs installed. Everything works perfectly and I was super happy to have Collabora fire up first time and I’m able to edit documents and spreadsheets and the like. What I’m curious about is when I launch a document. Collabora fires up and I get a “connecting” spinner for about 20 to 25 seconds before the docu…

[Nemskiller]

Yes for the moment there is two solutions :

1- compile yourself loolwsd, loleaflet and libreoffice and some dependencies

2- use the docker image to take out necessary files to working inside your system and not into docker’s one.

[Steven_Horner]

I have the same setup, guessing would need a self-signed certificate and maybe could edit the hosts file?

[Pisoko]

Are there sizing whitepapers or some hints for hardwarescaling?

[jospoortvliet]

@Pisoko

Are there sizing whitepapers or some hints for hardwarescaling?

not yet, we’re actually looking for customers to work with us getting this set up for 10K users or so and create a nice set of best practices for that. Collabora has experience with it so it shouldn’t be super painful but it has to be done on our side a few times first before I’m happy to write a white paper…

[nextgen-networks]

To everyone who faced the unexpected connection error:

Please check if you have restricted the collabora online app within nextcloud/ownCloud to a specific user-group.
This doesn’t work now - seems to be a bug.
Filed here: https://github.com/owncloud/richdocuments/issues/102

I wrote a little article about that behavior (german only by now - sorry)
https://www.2good4you.net/blog/19-web-stuff/6-collabora-online-unter-debian-8

[JohnnyGonzales]

Summary for the Debian Jessie problem

• Make the docker image run properly

Also known as Link problem:

[ loolkit ] link(“/opt/collaboraoffice5.1/CREDITS.fodt”,“/opt/lool/child-roots/1032/lo/CREDITS.fodt”)
failed. Exiting. (errno: Operation not permitted)

Don’t install a backport kernel, simply switch from aufs to devicemapper.
Easiest way:

apt-get remove --purge docker-engine
mv /var/lib/docker /var/lib/docker.old
apt-get install docker-engine


systemctrl stop docker
mv /var/lib/docker/aufs /var/lib/docker/devicemapper
systemctrl start docker

Changing /etc/default/docker and add DOCKER_OPTS=“–storage-driver=aufs” does not work on systemd.
Installing docker from other sources (script based etc) is not necessary.

• remove unexpected connection error

Dont restrict the nextCloud/ownCloud app to a specific user group

Are there still other problems out there?

[JohnnyGonzales]

Does anyone know how to install fonts (ttf) that can be displayed or used in a document by Collabora?
Installing the fonts in the hosting Linux environment does not seem to suffice.

[Eshmael]

Hi, i tried to install collabora into my nextcloud installation.
I followed the guide and have come to the point where i met an error:

its on the second part from i understand. When i try to make a new doc the file itself is made, but Collabor does not open it.

in the docker.log from var/logs is no entry at all (last one is from 2 days ago).
the logging from nextcloud throws the folowing debugging infos: (newest to oldest)

Debug no app in context Issuing token for USER file 43, version 0 owned by USER, path/to/file/file
Debug richdocuments Generating WOPI Token for file 43, version 0.
Info admin_audit File accessed: "path/to/file/file "
Debug no app in context Storing the discovery.xml to the cache.
Debug no app in context getDiscovery(): Getting discovery.xml from the cache.
Debug no app in context Storing the discovery.xml to the cache.
Debug no app in context getDiscovery(): Getting discovery.xml from the cache.
Error files Could not find resource file “/apps/files/js/jquery.iframe-transport.js”

apache log:
No protocol handler was valid for the URL /lool/ws/https://spdatabase.v22016023347031802.supersrv.de/index.php/apps/richdocuments/wopi/files/43. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule

Could it be the missing proxy_wstunnel mod?
I hope someone can help. i couldnt manage to find anything on google that helped me.

Debian Wheezy
Apache 2.2.20
PHP 5.5.38
mysql 5.5.50
Kernel 3.16
Nextcloud 10 (latest 9 version same behaviour and Errors)

Thanks for your Time patient reader
Esh