# 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:** 11
**Author:** ![MikeLupe](https://help.nextcloud.com/letter_avatar/mikelupe/32/6_22734026db12803ebb3e059622ac3534.png) [@MikeLupe](https://help.nextcloud.com/u/MikeLupe)\ **Post date:** [October 11, 2016, 10:24am UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/203 "2016-10-11T10:24:12Z")
One possible solution of connection error may be disabling “allow only for groups x” in the app section. > [@Collabora App doesn't work when only enabled for specific groups](https://help.nextcloud.com/t/collabora-app-doesnt-work-when-only-enabled-for-specific-groups/4061): > > I’ve had the usual “We are sorry, this is an unexpected connection error. Please try again.” error with my Collabora setup. There are for sure a lot of reasons why that error might turn up, but for me it simply was the fact, that I had the app only enabled for specific group. Can anybody confirm this? Thanks, Jakob Cudos to Jakob42 - well, we know what 42 means 🙂 ---
**Author:** ![liszca](https://help.nextcloud.com/letter_avatar/liszca/32/6_22734026db12803ebb3e059622ac3534.png) [@liszca](https://help.nextcloud.com/u/liszca)\ **Post date:** [October 13, 2016, 10:43pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/204 "2016-10-13T22:43:01Z")
I am a little bit confused about my `ifconfig` output: > ``` > docker0 Link encap:Ethernet HWaddr 02:42:50:5c:d8:21 > inet addr:172.17.0.1 Bcast:0.0.0.0 Mask:255.255.0.0 > inet6 addr: fe80::42:50ff:fe5c:d821/64 Scope:Link > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:24 errors:0 dropped:0 overruns:0 frame:0 > TX packets:87 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1608 (1.6 KB) TX bytes:23277 (23.2 KB) > > ``` Do I have to change the IP-Address here? `docker run -t -d -p 127.0.0.1:9980:9980 -e "domain=cloud\.nextcloud\.com" --restart always --cap-add MKNOD collabora/code` And what about the vhost config? \> # static html, js, images, etc. served from loolwsd > ``` > # loleaflet is the client part of LibreOffice Online > ProxyPass /loleaflet https://127.0.0.1:9980/loleaflet retry=0 > ProxyPassReverse /loleaflet https://127.0.0.1:9980/loleaflet > > ``` > ``` > # WOPI discovery URL > ProxyPass /hosting/discovery https://127.0.0.1:9980/hosting/discovery retry=0 > ProxyPassReverse /hosting/discovery https://127.0.0.1:9980/hosting/discovery > > ``` > ``` > # Main websocket > ProxyPass /lool/ws wss://127.0.0.1:9980/lool/ws > > ``` > ``` > # Admin Console websocket > ProxyPass /lool/adminws wss://127.0.0.1:9980/lool/adminws > > ``` > ``` > # Download as, Fullscreen presentation and Image upload operations > ProxyPass /lool https://127.0.0.1:9980/lool > ProxyPassReverse /lool https://127.0.0.1:9980/lool > > ``` Please let me know how to set these things up properly ---
**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:** [October 14, 2016, 6:46am UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/205 "2016-10-14T06:46:35Z")
127.0.0.1 is localhost. If your base system is setup correctly, this IP address always refers to the local system itself, so if you’re running Collabora there, the IP is correct. ---
**Author:** ![Twilek](https://help.nextcloud.com/user_avatar/help.nextcloud.com/twilek/32/637_2.png) [@Twilek](https://help.nextcloud.com/u/Twilek)\ **Post date:** [October 14, 2016, 10:48pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/206 "2016-10-14T22:48:30Z")
Hi all, since last update yesterday my nextcloud cannot completely connect to the document. It gives the error “Well, this is embarrassing, we cannot connect to your document. Please try again.”. The docker container seems to run fine and it worked before with the same config. Anyone seeing the same problem? ---
**Author:** ![Pisoko](https://help.nextcloud.com/user_avatar/help.nextcloud.com/pisoko/32/22884_2.png) [@Pisoko](https://help.nextcloud.com/u/Pisoko)\ **Post date:** [October 17, 2016, 12:14pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/207 "2016-10-17T12:14:53Z")
_Check this line in your Apache Config…_ # Main websocket ProxyPassMatch “/lool/(.\*)/ws$” wss://127.0.0.1:9980/lool/$1/ws ---
**Author:** ![ajdunevent](https://help.nextcloud.com/user_avatar/help.nextcloud.com/ajdunevent/32/1391_2.png) [@ajdunevent](https://help.nextcloud.com/u/ajdunevent)\ **Post date:** [October 17, 2016, 10:43pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/208 "2016-10-17T22:43:53Z")
You are not alone. I keep checking daily for updates to either the CODE Docker image or the Collabora Online Nextcloud app. Hopefully this will get resolved soon! Edit: Ah, got it! Thanks for the clue @Pisoko ---
**Author:** ![Ccandreva](https://help.nextcloud.com/user_avatar/help.nextcloud.com/ccandreva/32/1490_2.png) [@Ccandreva](https://help.nextcloud.com/u/Ccandreva)\ **Post date:** [October 19, 2016, 2:43pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/209 "2016-10-19T14:43:14Z")
Sorry I haven’t been back in a while. This is what I have for vhosts for standard http (https is right out of the docs). ``` ServerName nextcloud.foo.com DocumentRoot /var/www/nextcloud RedirectPermanent / https://nextcloud.foo.com/ ErrorLog logs/nextcloud/error_log TransferLog logs/nextcloud/access_log ServerName collabora.foo.com DocumentRoot /var/www/collabora RedirectPermanent / https://collabora.foo.com/ ErrorLog logs/collabora/error_log TransferLog logs/collabora/access_log ``` ---
**Author:** ![Leon\_Van\_Zyl](https://help.nextcloud.com/letter_avatar/leon_van_zyl/32/6_22734026db12803ebb3e059622ac3534.png) [@Leon\_Van\_Zyl](https://help.nextcloud.com/u/Leon_Van_Zyl)\ **Post date:** [October 20, 2016, 9:34am UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/210 "2016-10-20T09:34:21Z")
Ubuntu 16.10 users get the following error when starting the the new version :(or previous version actually) kit-00057-00 00:00:28.213298 [loolkit] mknod(/opt/lool/child-roots/57//dev/random) failed. (errno: Operation not permitted) kit-00057-00 00:00:28.213344 [loolkit] mknod(/opt/lool/child-roots/57//dev/urandom) failed. (errno: Operation not permitted) kit-00057-00 00:00:28.213364 [loolkit] chroot("/opt/lool/child-roots/57/") kit-00057-00 00:00:28.213391 [loolkit] chroot("/opt/lool/child-roots/57/") failed. (errno: Operation not permitted) In Ubuntu 16.10 the kernel configuration CONFIG\_AUFS\_XATTR=y has been omitted. Test: 16.10 $ grep AUFS\_X /boot/config-4.8.0-22-generic CONFIG\_AUFS\_XATTR is not set 16.04: grep AUFS\_X /boot/config-4.4.0-42-generic CONFIG\_AUFS\_XATTR=y Without CONFIG\_AUFS\_XATTR docker users using the AUFS driver can not use the image ---
**Author:** ![idef1x](https://help.nextcloud.com/user_avatar/help.nextcloud.com/idef1x/32/1409_2.png) [@idef1x](https://help.nextcloud.com/u/idef1x)\ **Post date:** [October 20, 2016, 12:07pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/211 "2016-10-20T12:07:47Z")
I finally got my setup working after I was receiving the following error all the time: **BadRequestException: Invalid URI or access denied.** I made sure that all connections to the nextcloud server and/or collabora server where comming from the public IP that matches the DNS names for them, so my working set-up is now: - a VPS with Ubuntu 16.04 server running nextcloud (on NGINX) in an LXD container (IP: 10.10.0.90) behind an NGINX reversed proxy (IP: 10.10.0.80) in another LXD container. Subnet for LXD is 10.10.0.0/24 - On the same VPS I have docker installed and runs with docker0 subnet 10.10.1.0/24 - Started the collabora docker container (IP: 10.10.1.2) without the -p settings and used \\ for the domain variable like the guide says (so -e “domain=cloud\\.example\\.com” ) - iptable rules to apply on the VPS: iptables -t nat -I PREROUTING -s 10.10.0.0/16 -d -p tcp --dport 443 -j DNAT --to 10.10.0.80 iptables -t nat -I POSTROUTING -s 10.10.0.0/16 -d 10.10.0.80 -p tcp --dport 443 -j SNAT --to the public IP of the VPS stands for [cloud.example.com](http://cloud.example.com) and [office.example.com](http://office.example.com) in DNS Hope this helps someone else as well. The video tutorial hinted me to backtrace the communication flow whereas a home server normally is behind a NAT internet router, which will source NAT addresses from the LAN into it’s public IP and than concludes that it has to forward this traffic back into the LAN to the reversed proxy 😉 ---
**Author:** ![Christoph\_Geiser](https://help.nextcloud.com/user_avatar/help.nextcloud.com/christoph_geiser/32/46430_2.png) [@Christoph\_Geiser](https://help.nextcloud.com/u/Christoph_Geiser)\ **Post date:** [October 20, 2016, 6:35pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/212 "2016-10-20T18:35:30Z")
Hi guys, Installed my collabora/code successfully. Docker is running and the connector works as well. Until I open or create a document… You know… the known error… (connnecting… couldn’t connect to the document blablabla…) I checked my apache-settings and they seem to be up to date and correct… docker log says: > frk-00033-00 00:00:48.639055 [loolforkit] Child 84 has exited, removing its jail ‘/opt/lool/child-roots/84’ > wsd-00024-03 00:00:51.660485 [client\_ws\_0002] getNewChild: No live child, forking more. > wsd-00024-03 00:00:51.660580 [client\_ws\_0002] getNewChild: No available child. Sending spawn request to forkit and failing. > wsd-00024-03 00:00:51.660667 [client\_ws\_0002] getNewChild: Have 0 children, forking 1 > wsd-00024-03 00:00:51.660730 [client\_ws\_0002] MasterToForKit: spawn 1 > wsd-00024-03 00:00:51.660790 [client\_ws\_0002] Writing to pipe. Data: [spawn 1]. > frk-00033-00 00:00:51.636432 [loolforkit] readFIFO for pipe: wsd\_pipe\_rd returned: 8 > frk-00033-00 00:00:51.636473 [loolforkit] Read line from pipe: wsd\_pipe\_rd, line: [spawn 1], data: . > frk-00033-00 00:00:51.636488 [loolforkit] ForKit command: [spawn 1]. > frk-00033-00 00:00:51.636508 [loolforkit] Spawning 1 child per request. > frk-00033-00 00:00:51.636522 [loolforkit] Creating 1 new child. > frk-00033-00 00:00:51.636533 [loolforkit] Forking a loolkit process. > frk-00033-00 00:00:51.638347 [loolforkit] Forked kit [89]. > kit-00089-00 00:00:51.638632 [loolforkit] Initializing kit > kit-00089-00 00:00:51.638688 [loolforkit] Log level is [8]. > kit-00089-00 00:00:51.638775 [loolkit] Process started. > kit-00089-00 00:00:51.638909 [loolkit] Jail path: /opt/lool/child-roots/89/ > kit-00089-00 00:00:51.639212 [loolkit] symlink(“…/lo”,“/opt/lool/child-roots/89/opt/collaboraoffice5.1”) > kit-00089-00 00:00:51.639857 [loolkit] link(“/opt/lool/systemplate/etc/resolv.conf”,“/opt/lool/child-roots/89/etc/resolv.conf”) failed. Exiting. (errno: Operation not permitted) OS is Debian Jessie with Kernel 3.16.0-4. What can I do? Do I need to update the Kernel (not sure if I should do that, as I’m running PLESK and stuff… and I had some bad problems when upgrading kernel or distro…) Thanks for any help 🙂 Chris ---
**Author:** ![ezraholm50](https://help.nextcloud.com/user_avatar/help.nextcloud.com/ezraholm50/32/836_2.png) [@ezraholm50](https://help.nextcloud.com/u/ezraholm50)\ **Post date:** [October 20, 2016, 7:35pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/213 "2016-10-20T19:35:46Z")
After enabling Collabora for certain user groups, it broke. Try disabling the NC Collabora App and de-install it from the Apps menu. Then install it again and enter the URL again. This made it work again for my installation. Also before that try to run: docker pull collabora/code && docker restart UUID-of-collabora-docker(docker ps shows it) ---
**Author:** ![Christoph\_Geiser](https://help.nextcloud.com/user_avatar/help.nextcloud.com/christoph_geiser/32/46430_2.png) [@Christoph\_Geiser](https://help.nextcloud.com/u/Christoph_Geiser)\ **Post date:** [October 20, 2016, 8:54pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/214 "2016-10-20T20:54:15Z")
Hi ezra, thanks for your suggestions. I tried that already yesterday, but did it again. Also I ran your suggested command to be sure I have the latest collabora/code installed. that is also true. I also removed the complete docker image and everything… I did not enable it for certain user groups. Didn’t see that option first 😉 Oh and in my admin URL I did not put the :9980 port but no port (or 443). 9980 is not working. But without port/443 it runs good. as well the XML (in my case [https://office.matthaeus-augsburg.de/hosting/discovery](https://office.matthaeus-augsburg.de/hosting/discovery)) pulls up correct. No idea what’s wrong here right now ☹ ---
**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:** [October 21, 2016, 8:19am UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/215 "2016-10-21T08:19:16Z")
Your problem was described above a couple of times, usually it is due to missing AUFS support in the Kernel. You can check for your Kernel like this: [Issue installing Collabora following official guide](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/210) If your Kernel doesn’t support AUFS, I’m afraid you either have to update it or find another solution (which probably requires some Docker knowledge). ---
**Author:** ![Christoph\_Geiser](https://help.nextcloud.com/user_avatar/help.nextcloud.com/christoph_geiser/32/46430_2.png) [@Christoph\_Geiser](https://help.nextcloud.com/u/Christoph_Geiser)\ **Post date:** [October 21, 2016, 9:01am UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/216 "2016-10-21T09:01:01Z")
Hi accolon, thanks for the suggestion… I had the hope that this is only for Ubuntu. So I skipped that part first (updating Kernel… uuuh… danger ;)). but well, I’m going to check that and will update the kernel if necesary. thanks a lot. Chris ---
**Author:** ![Christoph\_Geiser](https://help.nextcloud.com/user_avatar/help.nextcloud.com/christoph_geiser/32/46430_2.png) [@Christoph\_Geiser](https://help.nextcloud.com/u/Christoph_Geiser)\ **Post date:** [October 21, 2016, 3:57pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/217 "2016-10-21T15:57:08Z")
Hi accolon, I read into a few more things about AUFS. As the post you mentioned only mentions Ubuntu, I thought I’m checking a few things: - first of all: Debian does not support the kernel 4.x yet (at least not official, as they’re gonna integrate it in Debian 9 coming stable in february (hopefully) next year. - the grep command for my installed linux-kernel does not gives any output, BUT - checking if AUFS is supported and running with that documentation: [Use the AUFS storage driver | Docker Docs](https://docs.docker.com/engine/userguide/storagedriver/aufs-driver/) shows: > root@server /boot # grep aufs /proc/filesystems > nodev aufs > meaning, my system IS supporting AUFS correctly. I got to /etc/default and edited the docker-config there, adding > DOCKER\_OPTS=“–storage-driver=aufs” and checked after starting up docker again > Storage Driver: aufs > Root Dir: /var/lib/docker/aufs > Backing Filesystem: extfs > Dirs: 8 > Dirperm1 Supported: true > Logging Driver: json-file > Cgroup Driver: cgroupfs So that seems good I guess… on the other hand I also found something like this while starting dockerd > WARN[0001] Your kernel does not support cgroup memory limit > WARN[0001] Your kernel does not support cgroup cfs period > WARN[0001] Your kernel does not support cgroup cfs quotas So, before I try to update to a 4.x kernel on a unstable base: do I really need to update to an kernel, I maybe don’t need? As it looks for me, like AUFS is supported correctly… Greetings, Chris ---
**Author:** ![Christoph\_Geiser](https://help.nextcloud.com/user_avatar/help.nextcloud.com/christoph_geiser/32/46430_2.png) [@Christoph\_Geiser](https://help.nextcloud.com/u/Christoph_Geiser)\ **Post date:** [October 21, 2016, 5:41pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/218 "2016-10-21T17:41:25Z")
Okay guys… I switched from aufs to devicemapper as a driver… and now… well… it works 😉 ---
**Author:** ![liszca](https://help.nextcloud.com/letter_avatar/liszca/32/6_22734026db12803ebb3e059622ac3534.png) [@liszca](https://help.nextcloud.com/u/liszca)\ **Post date:** [October 21, 2016, 6:09pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/219 "2016-10-21T18:09:42Z")
Still having this Error > Well, this is embarrassing, we cannot connect to your document. Please try again. somehow the behavior of apache feels strange to me when I test the reverse proxy page in my browser I’ll get a page which shouldn’t be there. ---
**Author:** ![MikeLupe](https://help.nextcloud.com/letter_avatar/mikelupe/32/6_22734026db12803ebb3e059622ac3534.png) [@MikeLupe](https://help.nextcloud.com/u/MikeLupe)\ **Post date:** [October 21, 2016, 7:41pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/220 "2016-10-21T19:41:54Z")
@Christoph_Geiser I had to upgrade my kernel on Debian Jessie 8.6 to 4.7. It then finally worked for me. I tried almost everything needed before trying that, I think the only thing I changed _after_ the kernel upgrade was disabling groups for the app. ---
**Author:** ![Christoph\_Geiser](https://help.nextcloud.com/user_avatar/help.nextcloud.com/christoph_geiser/32/46430_2.png) [@Christoph\_Geiser](https://help.nextcloud.com/u/Christoph_Geiser)\ **Post date:** [October 21, 2016, 7:47pm UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/221 "2016-10-21T19:47:00Z")
Hm, I’m still not sure if I really want to update the kernel. Using devicemapper as device driver (ans xfs as filesystem) works, but not sure if that is the best option… Also: bigger excel lists (several sheets and more than 100 rows and about 20 columns) are quite slow. If I edit some stuff in the cells sometimes I need to hit save that the changes are visible. ---
**Author:** ![AYTAC\_DEDE](https://help.nextcloud.com/letter_avatar/aytac_dede/32/6_22734026db12803ebb3e059622ac3534.png) [@AYTAC\_DEDE](https://help.nextcloud.com/u/AYTAC_DEDE)\ **Post date:** [October 22, 2016, 4:53am UTC](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746/222 "2016-10-22T04:53:01Z")
dear sir could you explain how did you switch from auf to devicemapper i think i haveto do same but i dont have any idea thanks [Previous page](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746.md?page=10) [Next page](https://help.nextcloud.com/t/issue-installing-collabora-following-official-guide/1746.md?page=12)