Collabora problems

harley-peter · January 19, 2021, 9:27am

Hello,
I installed a NC (version 20.0.5) on my domain www.mydomain.de and also on my local computer and installed Collabora Built-in CODE Server and Collabora online. On my local installation it works fine and I can edit office files but if I activate Collabora Online on my domain installation NC becomes extremly slow, any action takes several minutes. It is impossible to work with NC in a normal manner.
Can someone help?

REAPERSbattlecry · February 3, 2022, 7:47pm

+1 get the same issue.
Do you also use a reverse proxy?

JimmyKater · February 4, 2022, 6:48am

did one of you guys come up with the idea of asking your hosting provider about issue first?

REAPERSbattlecry · February 6, 2022, 6:43pm

In my case no hosting provider issue.
Found some issues on the code server github page that describe the problem. But no solution yet

JimmyKater · February 6, 2022, 6:58pm

great!
you see why it is important to always give out as much information as possible when posting a problem?

it would be nice if you would link them here so that you would earn yourself a “solution”-award…

REAPERSbattlecry · February 8, 2022, 5:14am

Sorry.
Was a little in a hurry when i answered to the thread.

The github issue is this one:

github.com/nextcloud/richdocuments

RichDocuments built-in CODE causes significant slowdown/timeout issues

opened 01:12PM - 07 Dec 20 UTC

eganonoa

bug 2. developing high

Over the last couple of weeks Snap and Docker versions of Nextcloud have updated… to version 2.0.2 (snap on Friday). After the upgrade the connection to Nextcloud, particularly via the web-interface, slows to a crawl and/or times out. It appears to be caused by richdocuments/collabora. What is strange about this is that you cannot see easily identify the problem: basic analytics show no major increase in load on the CPU, Ram or I/O, the logs don't immediately show anything out of the ordinary. If you open top/htop on the server, however, and observe for a while you can see big, temporary spikes where available CPU's are maxed out by richdocuments/the Appimage related to Collabora and the Code server. When you go to the admin settings under collabora you can see an error that says that it cannot establish a connection to the in-built CODE server. The performance problem can be fixed by disabling both the collabora and code server apps: either in the web interface if you can get there through the performance issues, or in the server terminal (sudo snap run nextcloud.occ app:disable richdocuments ; sudo snap run nextcloud.occ app:disable richdocumentscore). After doing that normal service is resumed entirely across the Nextcloud server. This indicates that the failure to establish a connection to the inbuilt CODE server is the underlying problem and that there is something that happens when upgrading from Nextcloud v. 2.0.1 to 2.0.2 that causes it to break. Strangely, however, this is an issue that only appears to be present in Nextcloud Snap (where slowdown occurs) and Docker (where timeouts occur) and doesn't appear to have been reported by users of the regular Nextcloud: see threads on Nextcloud Community Forum (https://help.nextcloud.com/t/nextcloud-20-0-2snap2-interface-incredibly-slow/100304), Nextcloud Snap Github (https://github.com/nextcloud/nextcloud-snap/issues/1569), and Nextcloud Reddit (https://www.reddit.com/r/NextCloud/comments/k7b1of/extremely_slow_interface_nextcloud_snap/).

Unfortunately there is no solution so far and the last post is more than a year old.

In my case it is really easy to reproduce.
Install the code server, install collabora and the external access instantly slow down to 2 min loading time. Remove the collabora stuff and normal loading times. With the lokal ip address everything works fine.
As mentioned my ncp instance is behind a ngnix proxy.