hello , thks for a tuto .
Whis nextcloud 10 , you have in admin a menu of collabora , because is working but i dont have a menu ! ?
If I understand you correctly, you mean you canāt find a way to open the Collabore office suite from inside Nextcloud?
For this you have to install an app: youāll need to enable experimental apps (not sure about this however) and then go to the Productivy section and enable the āCollabora Onlineā app.
Good luck!
hello
where are you this interface ? in nexcloud ?
you have also there for the URL
Go in admin -> then additional settings -> then you have collabora
This is thread is becoming flooded and useless because of our off-top, admin panel is not related to connecting delay and itās not part of Nextcloud, itās part of LibreOffice Online.
I donāt use docker and not sure how admin panel works there, but if you use LibreOffice Online without docker then the address is as follows:
https://yourserver.com:9980/loleaflet/dist/admin/admin.html - the location maybe different depending on how you installed LOO
by the way, I noticed that some of the documents donāt close and just sit there in the background, so you have to clear them out.
for those who are interested, iāve lodged bug report 101809 with the libreoffice people so that someone can attend to the issue with the docker image.
Hi @wizdude,
I am the maintainer of collabora/code docker image. Thanks for this hint, I pushed a new image today to hub.docker.com with this fix in it.
Best regards,
Andras Timar
4 Likes
Hi @faktori,
I pushed a new collabora/code docker image to docker hub, which has a fix for the āspecial characterā problem. The docker image did not have the locales in it, and lacale set to POSIX. However, in this case LibreOffice can handle only ASCII file names. The solution was to install all locales, and I set en_US.UTF-8 in the environment. Thanks for the bug report.
Best regards,
Andras Timar
2 Likes
Hi @timar,
Is there any chance to have ARM (aarch64) docker images? I guess many of us have those SoC as own/nextcloud server and it would be great to play with CODE.
Best
Hello Timar, thank you for your help on this topic
I have downloaded your last image on docker hub and I am using it.
However I am still having āconnectingā delay of almost 30 seconds for my documents.
I tried opening some files on remote and local folders with no differences on the delay.
I tested collabora with various formats, (doc(x), xls(x), ): again no differences
An near empty 9kB odt file still takes 30sec to open.
So Iām pretty confident it is not a lool performance issue
I also tried repatching the docker image (just in case of ā¦) but I didnāt get any improvement.
I there anybody still having a 20sec+ delay with the newest docker image ?
(My server is a dual core vps from OVH, itās āunder-usedā, so Iām quite confident this is not a local performance issue)
Regards, Aal.
many thanks @timar for this. itās working well 
hi @aalaesar i can confirm that the new docker image has this DNS issue resolved and iām no longer getting the additional 20 second delay when opening documents. i have performed tcpdump testing on the docker0 virtual interface and all requests are being handled correctly.
1 Like
Thanks! For me the problem is solved now
For reference here is how fast it is for me now:
(It are two separate VPSāes, one with Collabora running in Docker + Apache proy and one with the Nextcloud installation)
@aalaesar are you sure you have stopped and started the docker container after pulling? More information here: Collabora online - Nextcloud (at the bottom of the page before the troubleshooting section)
2 Likes
Hello
thank you for your feed back,
So it confirms something is messed-up with my nextcloud instance. (upgraded to nextcloud 10, could be a causeā¦)
I did create a new container to test this image.
With further testing, I have weird symptoms on my instance (NC10) like :
- no collabora section in the admin conf (while the document apps is not activated)
- on Chrome/Chromium/Firefox: open a first doc instantaneously only once then always fails with āunexpected connection errorā after 45 sec while no error appears in the docker logs for any document, Even after cleaning cache and cookies (if related to browser)
-on EDGE : open any document with a connection delay of 30 seconds.
Iāll make some more testing on my side, but Iām opened for any suggestion.
Regards,
Aal.
The section is under āAdditional settingsā
Oops 
I was looking to fast.
One mystery solved, Thanks !
I haventt found yet why I have a 30 sec delay on Edge and sort of ātimeoutā on the other browsers.
Hello.
I have tested 2 brand new instances of nextcloud:
1- v9.0.53 => opening Documents/example.odt : Everything works fine except closing & reopening the file immediately (āconnectingā delay, then āunexpected connexion errorā)
2- v10.0 => opening Documents/About.odt : āconnectingā delay, then āunexpected connexion errorā, no errors in logs.
Edge manages to work most of the time but with a āconnectingā delay of 30sec.
So I came to the conclusion that this topicās issue is solved 
but something is broken since nextcloud 10, at least on my side, but without obvious causes to be found in the logs, Iām clueless. Any hint ?
Regards
1 Like
Iād like to invite people who want to try the libreoffice building, to follow this step (in deutch unfortunately):
Iāve builded LO using this guide on a Ubuntu Xenial VM, no 20 seconds delay, everything ok.
I tried the same thing on a debian jessie but here, no luck. I have 40 seconds delayā¦ I donāt know why but this is a different problemā¦ the vm performances are good (Iāve used the same VM of the ubuntu xenial) but the delay is enourmous.
Can anyone guide me through this issue? What can it be to create this long delay?
Thanks!
I solved my issue with the 2x delay!
As my previuos post, after compiling LO+loolwsd I was experiencing a ~40-44 seconds delay.
Iāve compiled LO+loolwsd on a VM located on my LAN, and then I moved the builded LO to my VPS that has only a public IP. Everything was working very good except this delay, it looked as a timeout somewhere so I decided to point out the DNS issues as per @wizdude post. Even if he were using the docker image and I was not, the theory of the DNS timeout made some sense to me, so, on my VPS I logged every packet going to private networks using this script:
#!/bin/bash
IPT=/sbin/iptables
$IPT -F OUTPUT
$IPT -A OUTPUT -d 10.0.0.0/8 -j LOG --log-prefix " LOG:"
$IPT -A OUTPUT -d 10.0.0.0/8 -j REJECT
$IPT -A OUTPUT -d 172.16.0.0/12 -j LOG --log-prefix " LOG:"
$IPT -A OUTPUT -d 172.16.0.0/12 -j REJECT
$IPT -A OUTPUT -d 192.168.0.0/16 -j LOG --log-prefix " LOG:"
$IPT -A OUTPUT -d 192.168.0.0/16 -j REJECT
No more delay and something really disappointing on the firewall logs:
Sep 6 19:39:30 oc kernel: [187734.187350] LOG:IN= OUT=eth0 SRC=188.x.x.x DST=192.168.10.2 LEN=61 TOS=0x00 PREC=0x00 TTL=64 ID=65021 DF PROTO=UDP SPT=58650 DPT=53 LEN=41
Sep 6 19:39:30 oc kernel: [187734.187418] LOG:IN= OUT=eth0 SRC=188.x.x.x DST=192.168.10.3 LEN=61 TOS=0x00 PREC=0x00 TTL=64 ID=26974 DF PROTO=UDP SPT=49437 DPT=53 LEN=41
Catch! 192.168.10.2 and 192.168.10.3 are my internal DNS listed on /etc/resolv.conf on the VM I used to build LO/loolwsd. The 2x delay is explained by my 2 dns servers: 20 seconds each = 40 secondsā¦
Anyone has any idea of the library/process that took the DNS from my building system? It may be happened during LO compiling or during the loolwsd compiling, Iād have to recompile loolwsd changing my system DNS and then look again, but not nowā¦ 
āupdate: The issue is on loolwsd only. I put a public DNS on my /etc/resolv.conf and I rebuilded loolwsd. Now the delay is gone, without any iptables workaround
1 Like
Congratulations aventrax for finding the root of this problem.
Has it been reported to the libreoffice online project ?
Regards.