# Issue installing Collabora following official guide **URL:** \ **Category:** ℹ️ Support\ **Created:** [July 20, 2016, 9:52am UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746 "2016-07-20T09:52:59Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![jurgenhaas](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jurgenhaas/32/559_2.png) [@jurgenhaas](https://help.nextcloud.com/u/jurgenhaas)\ **Post date:** [July 20, 2016, 9:52am UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/1 "2016-07-20T09:52:59Z")
I’m following the guide at [https://nextcloud.com/collaboraonline/](https://nextcloud.com/collaboraonline/) and I have a fresh NextCloud installation version 9.0.52 on Ubuntu 14.04. There are several problems: 1. Special characters when running docker: the documentation mentions the need to escape periods. Are there other characters (e.g. hyphens) that should also be escaped? 2. Apache Configuration ServerName: the guide mentions the servername including the colon and port but my understanding is that the server name should be without the port, isn’t it? 3. Apache Configuration DocRoot: the virtual host declares some paths that will be handled by the proxy settings, but if you browser to the domain itself, Apache is serving that request without using any proxy and in the default configuration delivers the request as if it were going to the default docroot of that host. Shouldn’t there be a DocRoot declaration that captures everything not being handled by the proxies and respond with a 404? 4. Install the “Collabora Online app”: The problem is that the app in my installation is named “Collabora Online Connector” and it is labeled as experimental. Is that correct? If not, why is my installation which is fresh (see above) not showing the correct one? 5. When going to the admin area where I want to provide the URL for the Collabora instance, I can click on “Save” but it doesn’t do anything. Nothing found in the logs for this. Maybe this is because of the previous item and I’m running the wrong app version? The version number given is 1.1.3 Any help is much appreciated and maybe we should eventually update the installation guide. ---
**Author:** ![accolon](https://help.nextcloud.com/user_avatar/help.nextcloud.com/accolon/32/657_2.png) [@accolon](https://help.nextcloud.com/u/accolon)\ **Post date:** [July 20, 2016, 10:56am UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/2 "2016-07-20T10:56:22Z")
While I can’t say anything about 1. to 3. for my test setup, I ran into the same questions you describe in 4. and 5. For me, the “Save” button didn’t work either when I tried with Safari – the field simply reset to the default entry (localhost) after exiting the settings. However, it did work when using Firefox on the same Mac. I can now open Collabora from the Nextcloud dropdown menu and select one of my ODT files, afterwards it loads some kind of UI (with text formatting options), but loading the document fails with an “unexpected connection error”. ---
**Author:** ![Nils\_Buchner](https://help.nextcloud.com/letter_avatar/nils_buchner/32/6_22734026db12803ebb3e059622ac3534.png) [@Nils\_Buchner](https://help.nextcloud.com/u/Nils_Buchner)\ **Post date:** [July 20, 2016, 12:10pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/3 "2016-07-20T12:10:28Z")
I have the same “unexpected connection error” here. ![](https://help.nextcloud.com/uploads/default/original/1X/f2fe87d43e922bc4692e862a231da4adc4016953.png) ---
**Author:** ![LukasReschke](https://help.nextcloud.com/user_avatar/help.nextcloud.com/lukasreschke/32/1929_2.png) [@LukasReschke](https://help.nextcloud.com/u/LukasReschke)\ **Post date:** [July 20, 2016, 12:14pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/4 "2016-07-20T12:14:09Z")
> [@jurgenhaas](#): > > Special characters when running docker: the documentation mentions the need to escape periods. Are there other characters (e.g. hyphens) that should also be escaped? It uses regex. So yes, might be required to also escape your hypens. > [@jurgenhaas](#): > > Apache Configuration ServerName: the guide mentions the servername including the colon and port but my understanding is that the server name should be without the port, isn’t it? Shouldn’t make a big difference I think. But PR welcome to [nextcloud.com/page-collaboraonline.php at master · nextcloud/nextcloud.com · GitHub](https://github.com/nextcloud/nextcloud.com/blob/master/page-collaboraonline.php) 🙂 > [@jurgenhaas](#): > > Install the “Collabora Online app”: The problem is that the app in my installation is named “Collabora Online Connector” and it is labeled as experimental. Is that correct? If not, why is my installation which is fresh (see above) not showing the correct one? Remarked it as approved. > [@jurgenhaas](#): > > When going to the admin area where I want to provide the URL for the Collabora instance, I can click on “Save” but it doesn’t do anything. Nothing found in the logs for this. Maybe this is because of the previous item and I’m running the wrong app version? The version number given is 1.1.3 Please check your browser console log. Also what browser do you use? > [@Nils\_Buchner](#): > > I have the same “unexpected connection error” here. This rather indicates a configuration issue, please post detailled what you did as well as the log output of the docker container. (start it without -d so we can see what it fails at) ---
**Author:** ![jurgenhaas](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jurgenhaas/32/559_2.png) [@jurgenhaas](https://help.nextcloud.com/u/jurgenhaas)\ **Post date:** [July 20, 2016, 12:54pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/5 "2016-07-20T12:54:55Z")
Thanks @LukasReschke I’ll address 1-3 accordingly and I can already confirm that I now have an app “Office” in the drop-down which I can open and that then gets me to [https://cloud.my-domain.com/index.php/apps/richdocuments/index](https://cloud.my-domain.com/index.php/apps/richdocuments/index) with 4 buttons to add three different document types or to upload one. So item 4 and 5 is now also resolved. However, when I click on “New document” I get a gray square and when I click on that I get a message “Failed to open undefined, file not supported.” ![](https://help.nextcloud.com/uploads/default/original/1X/05ff141320c21a79b3b0d7db7a5d72198c21c533.jpg) The browser console shows an error “Content Security Policy: frame-src” and that instead child-src should be used. And when I try to upload a document I get “Type Error: window.FileList.findFileEl is not a function”. The log is full of entries like “Undefined index: dir at /var/www/nextcloud/paragon/apps/richdocuments/controller/documentcontroller.php#289” Browsers used: latest Chrome and latest Firefox on Ubuntu 16.04 LTS ---
**Author:** ![LukasReschke](https://help.nextcloud.com/user_avatar/help.nextcloud.com/lukasreschke/32/1929_2.png) [@LukasReschke](https://help.nextcloud.com/u/LukasReschke)\ **Post date:** [July 20, 2016, 1:25pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/6 "2016-07-20T13:25:21Z")
What does your docker container say in the logs? I suppose the connection attempt is somehow failing 🙂 ---
**Author:** ![Reldeis](https://help.nextcloud.com/letter_avatar/reldeis/32/6_22734026db12803ebb3e059622ac3534.png) [@Reldeis](https://help.nextcloud.com/u/Reldeis)\ **Post date:** [July 20, 2016, 1:46pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/7 "2016-07-20T13:46:55Z")
I have the same problem as @jurgenhaas. The logs get spammed with > office\_1 | kit-00615-00 00:10:04.054159 [loolkit] Process started. > office\_1 | kit-00615-00 00:10:04.054358 [loolkit] Jail path: /opt/lool/child-roots/615/ > office\_1 | kit-00615-00 00:10:04.054722 [loolkit] symlink(“…/lo”,“/opt/lool/child-roots/615/opt/collaboraoffice5.1”) > office\_1 | kit-00615-00 00:10:04.181319 [loolkit] skip redundant paths share/config/wizard > office\_1 | kit-00615-00 00:10:04.192258 [loolkit] skip redundant paths share/template > office\_1 | kit-00615-00 00:10:04.192292 [loolkit] skip redundant paths share/Scripts > office\_1 | kit-00615-00 00:10:04.198212 [loolkit] skip redundant paths share/gallery > office\_1 | kit-00615-00 00:10:04.201204 [loolkit] skip redundant paths share/basic > office\_1 | kit-00615-00 00:10:04.207073 [loolkit] skip redundant paths program/wizards > office\_1 | kit-00615-00 00:10:04.365934 [loolkit] Initialized jail files. > office\_1 | kit-00615-00 00:10:04.366124 [loolkit] mknod(/opt/lool/child-roots/615//dev/random) failed. (errno: Operation not permitted) > office\_1 | kit-00615-00 00:10:04.366181 [loolkit] mknod(/opt/lool/child-roots/615//dev/urandom) failed. (errno: Operation not permitted) > office\_1 | kit-00615-00 00:10:04.366197 [loolkit] chroot(“/opt/lool/child-roots/615/”) > office\_1 | kit-00615-00 00:10:04.366217 [loolkit] chroot(“/opt/lool/child-roots/615/”) failed. (errno: Operation not permitted) > office\_1 | frk-00030-00 00:10:05.054808 [loolforkit] Child 615 has exited, removing its jail ‘/opt/lool/child-roots/615’ > office\_1 | wsd-00021-00 00:10:10.434189 [loolwsd] MasterToForKit: spawn 1 > office\_1 | wsd-00021-00 00:10:10.434237 [loolwsd] Writing to pipe. Data: [spawn 1]. > office\_1 | frk-00030-00 00:10:10.050371 [loolforkit] readFIFO for pipe: wsd\_pipe\_rd returned: 8 > office\_1 | frk-00030-00 00:10:10.050411 [loolforkit] Read line from pipe: wsd\_pipe\_rd, line: [spawn 1], data: . > office\_1 | frk-00030-00 00:10:10.050424 [loolforkit] ForKit command: [spawn 1]. > office\_1 | frk-00030-00 00:10:10.050443 [loolforkit] Spawning 1 child per request. > office\_1 | frk-00030-00 00:10:10.050455 [loolforkit] Creating 1 new child. > office\_1 | frk-00030-00 00:10:10.050464 [loolforkit] Forking a loolkit process. > office\_1 | frk-00030-00 00:10:10.053234 [loolforkit] Forked kit [620]. > office\_1 | kit-00620-00 00:10:10.053566 [loolforkit] Initializing kit > office\_1 | kit-00620-00 00:10:10.053626 [loolforkit] Log level is [8]. > office\_1 | kit-00620-00 00:10:10.053686 [loolkit] Process started. > office\_1 | kit-00620-00 00:10:10.053806 [loolkit] Jail path: /opt/lool/child-roots/620/ > office\_1 | kit-00620-00 00:10:10.054110 [loolkit] symlink(“…/lo”,“/opt/lool/child-roots/620/opt/collaboraoffice5.1”) > office\_1 | kit-00620-00 00:10:10.181806 [loolkit] skip redundant paths share/config/wizard > office\_1 | kit-00620-00 00:10:10.192326 [loolkit] skip redundant paths share/template > office\_1 | kit-00620-00 00:10:10.192370 [loolkit] skip redundant paths share/Scripts > office\_1 | kit-00620-00 00:10:10.198030 [loolkit] skip redundant paths share/gallery > office\_1 | kit-00620-00 00:10:10.200936 [loolkit] skip redundant paths share/basic > office\_1 | kit-00620-00 00:10:10.206367 [loolkit] skip redundant paths program/wizards > office\_1 | kit-00620-00 00:10:10.342580 [loolkit] Initialized jail files. > office\_1 | kit-00620-00 00:10:10.342755 [loolkit] mknod(/opt/lool/child-roots/620//dev/random) failed. (errno: Operation not permitted) > office\_1 | kit-00620-00 00:10:10.342795 [loolkit] mknod(/opt/lool/child-roots/620//dev/urandom) failed. (errno: Operation not permitted) > office\_1 | kit-00620-00 00:10:10.342805 [loolkit] chroot(“/opt/lool/child-roots/620/”) > office\_1 | kit-00620-00 00:10:10.342829 [loolkit] chroot(“/opt/lool/child-roots/620/”) failed. (errno: Operation not permitted) > office\_1 | frk-00030-00 00:10:11.054421 [loolforkit] Child 620 has exited, removing its jail ‘/opt/lool/child-roots/620’ There is nothing in the docker logs regarding opening a file/creating a file Small Edit: I use docker-compose and this is my `docker-compose.yml`: > cloud: > image: wonderfall/nextcloud > restart: always > links: > - cloudDB:cloudDB > environment: > - UID=109 > - GID=119 > - VIRTUAL\_HOST=[cloud.example.com](http://cloud.example.com) > - LETSENCRYPT\_HOST=[cloud.example.com](http://cloud.example.com) > - [LETSENCRYPT\_EMAIL=certs@example.com](mailto:LETSENCRYPT_EMAIL=certs@example.com) > volumes: > - /home/cloud/data:/data > - /home/cloud/config:/config > - /home/cloud/apps:/apps2 > cloudDB: > image: mariadb:10 > restart: always > volumes: > - /home/cloud/db:/var/lib/mysql > environment: > - MYSQL\_ROOT\_PASSWORD=someThing > - MYSQL\_DATABASE=nextcloud > - MYSQL\_USER=nextcloud > - MYSQL\_PASSWORD=someThing > office: > image: collabora/code > restart: always > ports: > - “127.0.0.1:9980:9980” > environment: > - VIRTUAL\_HOST=[office.example.com](http://office.example.com) > - LETSENCRYPT\_HOST=[office.example.com](http://office.example.com) > - [LETSENCRYPT\_EMAIL=certs@example.com](mailto:LETSENCRYPT_EMAIL=certs@example.com) > - domain=cloud.example.com > cap\_add: > - MKNOD ---
**Author:** ![Adnae](https://help.nextcloud.com/user_avatar/help.nextcloud.com/adnae/32/662_2.png) [@Adnae](https://help.nextcloud.com/u/Adnae)\ **Post date:** [July 20, 2016, 1:53pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/8 "2016-07-20T13:53:23Z")
I become the the error … and here is my log: Generating RSA private key, 2048 bit long modulus …+++ …+++ e is 65537 (0x10001) Generating RSA private key, 2048 bit long modulus …+++ …+++ e is 65537 (0x10001) Signature ok subject=/C=DE/ST=BW/L=Stuttgart/O=Dummy Authority/CN=localhost Getting CA Private Key wsd-00022-00 00:00:00.000712 [loolwsd] Initializing wsd wsd-00022-00 00:00:00.000858 [loolwsd] Log level is [8]. wsd-00022-00 00:00:00.002511 [loolwsd] Open Documents Limit: 10 wsd-00022-00 00:00:00.002616 [loolwsd] Client Connections Limit: 20 wsd-00022-00 00:00:00.002774 [loolwsd] Adding trusted WOPI host: [nextcloud.adm.dcsix]. wsd-00022-00 00:00:00.002867 [loolwsd] Adding trusted WOPI host: [10.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}]. wsd-00022-00 00:00:00.002943 [loolwsd] Adding trusted WOPI host: [172.1[6789].[0-9]{1,3}.[0-9]{1,3}]. wsd-00022-00 00:00:00.003034 [loolwsd] Adding trusted WOPI host: [172.2[0-9].[0-9]{1,3}.[0-9]{1,3}]. wsd-00022-00 00:00:00.003103 [loolwsd] Adding trusted WOPI host: [172.3[01].[0-9]{1,3}.[0-9]{1,3}]. wsd-00022-00 00:00:00.003183 [loolwsd] Adding trusted WOPI host: [192.168.[0-9]{1,3}.[0-9]{1,3}]. wsd-00022-00 00:00:00.003256 [loolwsd] Adding blocked WOPI host: [192.168.1.1]. loolwsd 1.7.2 - 1.7.2 wsd-00022-00 00:00:00.003511 [loolwsd] SSL Cert file: /etc/loolwsd/cert.pem wsd-00022-00 00:00:00.003589 [loolwsd] SSL Key file: /etc/loolwsd/key.pem wsd-00022-00 00:00:00.003668 [loolwsd] SSL CA file: /etc/loolwsd/ca-chain.cert.pem wsd-00022-00 00:00:00.012456 [loolwsd] FileServerRoot: /usr/share/loolwsd wsd-00022-00 00:00:00.012779 [loolwsd] mkfifo(/opt/lool/child-roots/pipe/loolwsdfifo) wsd-00022-00 00:00:00.012853 [loolwsd] File server ctor. wsd-00022-00 00:00:00.013433 [loolwsd] Starting master server listening on 9980 wsd-00022-00 00:00:00.013570 [loolwsd] Starting prisoner server listening on 9981 wsd-00022-00 00:00:00.013668 [loolwsd] Launching forkit process: /usr/bin/loolforkit --losubpath=lo --systemplate=/opt/lool/systemplate --lotemplate=/opt/collaboraoffice5.1 --childroot=/opt/lool/child-roots/ --clientport=9980 --version frk-00031-00 00:00:00.000759 [loolforkit] Initializing frk frk-00031-00 00:00:00.000866 [loolforkit] Log level is [8]. loolforkit 1.7.2 - 1.7.2 frk-00031-00 00:00:00.000981 [loolforkit] Note: LD\_BIND\_NOW is not set. frk-00031-00 00:00:00.001012 [loolforkit] Note: LOK\_VIEW\_CALLBACK is not set. frk-00031-00 00:00:00.001112 [loolforkit] open(/opt/lool/child-roots/pipe/loolwsdfifo, RDONLY) = 4 wsd-00022-00 00:00:00.335334 [loolwsd] open(/opt/lool/child-roots/pipe/loolwsdfifo, WRONLY) = 8 wsd-00022-00 00:00:00.335677 [loolwsd] AdminModel ctor. wsd-00022-00 00:00:00.336042 [loolwsd] Admin ctor. wsd-00022-00 00:00:00.336189 [loolwsd] Memory stat ctor wsd-00022-00 00:00:00.336455 [loolwsd] Cpu stat ctor frk-00031-00 00:00:02.424755 [loolforkit] Preinit stage OK. frk-00031-00 00:00:02.424843 [loolforkit] Forking a loolkit process. frk-00031-00 00:00:02.429436 [loolforkit] Forked kit [35]. frk-00031-00 00:00:02.429627 [loolforkit] ForKit process is ready. kit-00035-00 00:00:02.430099 [loolforkit] Initializing kit kit-00035-00 00:00:02.430327 [loolforkit] Log level is [8]. kit-00035-00 00:00:02.430506 [loolkit] Process started. kit-00035-00 00:00:02.430786 [loolkit] Jail path: /opt/lool/child-roots/35/ kit-00035-00 00:00:02.431411 [loolkit] symlink("…/lo","/opt/lool/child-roots/35/opt/collaboraoffice5.1") kit-00035-00 00:00:02.654860 [loolkit] link("/opt/collaboraoffice5.1/LICENSE","/opt/lool/child-roots/35/lo/LICENSE") failed. Exiting. (errno: Operation not permitted) frk-00031-00 00:00:03.430815 [loolforkit] Child 35 has exited, removing its jail '/opt/lool/child-roots/35’ wsd-00022-00 00:00:04.336766 [loolwsd] MasterToForKit: spawn 1 wsd-00022-00 00:00:04.336856 [loolwsd] Writing to pipe. Data: [spawn 1]. frk-00031-00 00:00:04.002861 [loolforkit] readFIFO for pipe: wsd\_pipe\_rd returned: 8 frk-00031-00 00:00:04.003018 [loolforkit] Read line from pipe: wsd\_pipe\_rd, line: [spawn 1], data: []. frk-00031-00 00:00:04.003105 [loolforkit] ForKit command: [spawn 1]. frk-00031-00 00:00:04.003382 [loolforkit] Spawning 1 child per request. frk-00031-00 00:00:04.003496 [loolforkit] Creating 1 new child. frk-00031-00 00:00:04.003607 [loolforkit] Forking a loolkit process. frk-00031-00 00:00:04.010471 [loolforkit] Forked kit [36]. kit-00036-00 00:00:04.011065 [loolforkit] Initializing kit kit-00036-00 00:00:04.011207 [loolforkit] Log level is [8]. kit-00036-00 00:00:04.011333 [loolkit] Process started. kit-00036-00 00:00:04.011580 [loolkit] Jail path: /opt/lool/child-roots/36/ kit-00036-00 00:00:04.012164 [loolkit] symlink("…/lo","/opt/lool/child-roots/36/opt/collaboraoffice5.1") kit-00036-00 00:00:04.082538 [loolkit] link("/opt/collaboraoffice5.1/LICENSE","/opt/lool/child-roots/36/lo/LICENSE") failed. Exiting. (errno: Operation not permitted) frk-00031-00 00:00:05.011726 [loolforkit] Child 36 has exited, removing its jail '/opt/lool/child-roots/36’ wsd-00022-10 00:00:05.348457 [loolwsd] Total memory used: 207864 Under /opt/lool/child-roots no dirs created and doesn’t exists … ---
**Author:** ![LukasReschke](https://help.nextcloud.com/user_avatar/help.nextcloud.com/lukasreschke/32/1929_2.png) [@LukasReschke](https://help.nextcloud.com/u/LukasReschke)\ **Post date:** [July 20, 2016, 1:54pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/9 "2016-07-20T13:54:02Z")
> [@Reldeis](#): > > office\_1 | kit-00620-00 00:10:10.342755 [loolkit] mknod(/opt/lool/child-roots/620//dev/random) failed. (errno: Operation not permitted)office\_1 | kit-00620-00 00:10:10.342795 [loolkit] mknod(/opt/lool/child-roots/620//dev/urandom) failed. (errno: Operation not permitted)office\_1 | kit-00620-00 00:10:10.342805 [loolkit] chroot(“/opt/lool/child-roots/620/”)office\_1 | kit-00620-00 00:10:10.342829 [loolkit] chroot(“/opt/lool/child-roots/620/”) failed. (errno: Operation not permitted) This is a permission problem on your environment. Please make sure you don’t have anything in place that restricts the permission of the container. One example is AppArmor, it may be sensible to disable AppArmor for the docker container. … if somebody has some decent knowledge about AppArmor then feedback on proper rules for Ubuntu are welcome 🙂 ---
**Author:** ![LukasReschke](https://help.nextcloud.com/user_avatar/help.nextcloud.com/lukasreschke/32/1929_2.png) [@LukasReschke](https://help.nextcloud.com/u/LukasReschke)\ **Post date:** [July 20, 2016, 1:57pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/10 "2016-07-20T13:57:17Z")
Aso make sure your Docker version supports already dropping the capabilities, alternatively starting with `--privileged` may help as well. On my Ubuntu Xenial docker host it was however sufficient to disable AppArmor. ---
**Author:** ![Adnae](https://help.nextcloud.com/user_avatar/help.nextcloud.com/adnae/32/662_2.png) [@Adnae](https://help.nextcloud.com/u/Adnae)\ **Post date:** [July 20, 2016, 2:01pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/11 "2016-07-20T14:01:48Z")
I use Debian Jessie has Docker Host. My Docker Version is: Docker version 1.11.2, build b9f10c9 ---
**Author:** ![Reldeis](https://help.nextcloud.com/letter_avatar/reldeis/32/6_22734026db12803ebb3e059622ac3534.png) [@Reldeis](https://help.nextcloud.com/u/Reldeis)\ **Post date:** [July 20, 2016, 2:20pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/12 "2016-07-20T14:20:39Z")
I don’t think a docker container should rely on a disabled apparmor environment. Docker already provides a [default policy](https://docs.docker.com/v1.11/engine/security/apparmor/). If this is not sufficent you can provide your own policy. Disabling apparmor entirely might make an server more vulnerable. If this is still an issue this weekend, i will setup a VM and test it with AppArmor disabled 🙂 ---
**Author:** ![jurgenhaas](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jurgenhaas/32/559_2.png) [@jurgenhaas](https://help.nextcloud.com/u/jurgenhaas)\ **Post date:** [July 20, 2016, 2:28pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/13 "2016-07-20T14:28:24Z")
Got it working when disabling the firewall. Looks like my firewall settings are preventing communication with the docker network. ---
**Author:** ![husky](https://help.nextcloud.com/user_avatar/help.nextcloud.com/husky/32/16406_2.png) [@husky](https://help.nextcloud.com/u/husky)\ **Post date:** [July 20, 2016, 4:32pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/14 "2016-07-20T16:32:43Z")
Tried using firefox for entering the domain of the Collabora VirtualHost right after reading your note - but to no avail. 😔 The browser console doesn’t say a thing for me - except for several errors about certificate issues. But hitting the SAVE button doesn’t do anything at all, so I wonder if I’m using it correctly (I’m unfamiliar with it, I’m not a developer) - I just opened it and then hit the button again. ---
**Author:** ![rigrig](https://help.nextcloud.com/user_avatar/help.nextcloud.com/rigrig/32/529_2.png) [@rigrig](https://help.nextcloud.com/u/rigrig)\ **Post date:** [July 20, 2016, 6:12pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/15 "2016-07-20T18:12:41Z")
Getting similar output as Adnae from docker, with something like this repeating over and over again: ```auto frk-00031-00 00:00:04.179890 [loolforkit] Forking a loolkit process. kit-00035-00 00:00:04.186325 [loolkit] Jail path: /opt/lool/child-roots/35/ kit-00035-00 00:00:04.193690 [loolkit] symlink("../lo","/opt/lool/child-roots/35/opt/collaboraoffice5.1") frk-00031-00 00:00:04.222657 [loolforkit] Forked kit [36]. kit-00036-00 00:00:04.233226 [loolforkit] Initializing kit kit-00036-00 00:00:04.236718 [loolforkit] Log level is [8]. kit-00036-00 00:00:04.239553 [loolkit] Process started. kit-00036-00 00:00:04.241127 [loolkit] Jail path: /opt/lool/child-roots/36/ kit-00036-00 00:00:04.251402 [loolkit] symlink("../lo","/opt/lool/child-roots/36/opt/collaboraoffice5.1") kit-00035-00 00:00:04.821600 [loolkit] link("/opt/collaboraoffice5.1/readmes/README_en-US","/opt/lool/child-roots/35/lo/readmes/README_en-US") failed. Exiting. (errno: Operation not permitted) kit-00036-00 00:00:04.825847 [loolkit] link("/opt/collaboraoffice5.1/readmes/README_en-US","/opt/lool/child-roots/36/lo/readmes/README_en-US") failed. Exiting. (errno: Operation not permitted) wsd-00022-10 00:00:05.214971 [loolwsd] Total memory used: 113408 frk-00031-00 00:00:05.232064 [loolforkit] Child 35 has exited, removing its jail '/opt/lool/child-roots/35' frk-00031-00 00:00:05.302966 [loolforkit] Child 36 has exited, removing its jail '/opt/lool/child-roots/36' ``` The last two kit-… lines (about _link…failed_) are bold red This keeps on happening, even when I don’t have “Office” open. The browser debug console shows _error: Service is unavailable. Please try again later and report to your administrator if the issue persists._ from the websocket connection: ![](https://help.nextcloud.com/uploads/default/original/1X/b8749e62d1d73c8f9c3fad0a41b33888c851c5c2.png) ---
**Author:** ![dcrdev](https://help.nextcloud.com/letter_avatar/dcrdev/32/6_22734026db12803ebb3e059622ac3534.png) [@dcrdev](https://help.nextcloud.com/u/dcrdev)\ **Post date:** [July 20, 2016, 6:20pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/16 "2016-07-20T18:20:43Z")
For anyone having issues where the save button is not working - I got it to work just by waiting a couple of seconds; looks like it’s really slow. Also there’s no confirmation of it having saved the new URL. Also I received a cURL error saying that the root certificate had not been installed - I concatenated my self signed CA cert onto ca-bundle.crt and that’s fixed it. I use self signed certificates and have CloudFlare on top in order to present a trusted cert. The ca-bundle.crt is going to get overwritten with every update, is there a better way of doing this? I don’t really understand either because my CA is trusted on my server and I can use cURL via the shell against it. One last thing - is the docker container self updating? ---
**Author:** ![koehn](https://help.nextcloud.com/user_avatar/help.nextcloud.com/koehn/32/593_2.png) [@koehn](https://help.nextcloud.com/u/koehn)\ **Post date:** [July 21, 2016, 2:36pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/18 "2016-07-21T14:36:22Z")
I was able to set the URL using the following against my database: ```auto insert into oc_appconfig(appid, configkey, configvalue) values ('richdocuments','wopi_url','https://[your url here]'); ``` Now I can open the page that shows the document list. When I open a document, I’m now also getting the `We are sorry, this is an unexpected connection error.` message. I’ve disabled `apparmor` and running in `--privileged` mode. Here’s what I see (repeated ad nauseum): ```auto frk-00031-00 00:00:01.392604 [loolforkit] Preinit stage OK. frk-00031-00 00:00:01.392685 [loolforkit] Forking a loolkit process. frk-00031-00 00:00:01.396012 [loolforkit] Forked kit [35]. frk-00031-00 00:00:01.396135 [loolforkit] ForKit process is ready. kit-00035-00 00:00:01.396303 [loolforkit] Initializing kit kit-00035-00 00:00:01.396393 [loolforkit] Log level is [8]. kit-00035-00 00:00:01.396457 [loolkit] Process started. kit-00035-00 00:00:01.396579 [loolkit] Jail path: /opt/lool/child-roots/35/ kit-00035-00 00:00:01.396950 [loolkit] symlink("../lo","/opt/lool/child-roots/35/opt/collaboraoffice5.1") kit-00035-00 00:00:01.592696 [loolkit] link("/opt/collaboraoffice5.1/readmes/README_en-US","/opt/lool/child-roots/35/lo/readmes/README_en-US") failed. Exiting. (errno: Operation not permitted) ``` ---
**Author:** ![LukasReschke](https://help.nextcloud.com/user_avatar/help.nextcloud.com/lukasreschke/32/1929_2.png) [@LukasReschke](https://help.nextcloud.com/u/LukasReschke)\ **Post date:** [July 21, 2016, 5:14pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/19 "2016-07-21T17:14:50Z")
Are you all on Ubuntu 14.04? My best guess is [https://github.com/docker/docker/issues/20658](https://github.com/docker/docker/issues/20658) then: Probably the kernel isn’t compiled with `CONFIG_AUFS_XATTR`. Has anybody the chance here to test that quickly? 🙂 ---
**Author:** ![jurgenhaas](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jurgenhaas/32/559_2.png) [@jurgenhaas](https://help.nextcloud.com/u/jurgenhaas)\ **Post date:** [July 21, 2016, 5:26pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/20 "2016-07-21T17:26:07Z")
I have quickly tested to run docker with the `--security-opt=seccomp:unconfined` option and it looks as if it is working much better now. Still having to sort out my firewall issue but when I turn that off, it looks as if it is working OK. ---
**Author:** ![X4LD1M0](https://help.nextcloud.com/user_avatar/help.nextcloud.com/x4ld1m0/32/44898_2.png) [@X4LD1M0](https://help.nextcloud.com/u/X4LD1M0)\ **Post date:** [July 21, 2016, 5:26pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/21 "2016-07-21T17:26:42Z")
I am running Debian 8 (Jessie) so not sure if still relevant. [Next page](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746.md?page=2)