Using 172.18.0.0/16 worked for me on the WOPI whitelist when using built-in CODE server.

So there are some logs on the Nextcloud side too. It shows returning a 403, not authorized. It seems like the token it's retrieving is invalid or something. I didn't find anything too promising when searching Nextcloud forum either. I'll keep poking.

Support couldn't reproduce it for now so they just ignore it for now as it's not critical. Maybe someday we have an idea on what causes this.

@RazielKanos I pushed an update yesterday with language packs for collabora. Can you check if the situation changes with the new package?

This thread - https://forum.cloudron.io/topic/8978/nextcloud-office-and-onlyoffice

To get this working, you have to login to the collabora app on your Cloudron (we have added a small config UI for that purpose) and then configure which origins can connect: https://docs.cloudron.io/apps/collabora/

I tried this just now and I can confirm that the rendering in the actual document is not working. Seems like some upstream bug then, which needs investigation. Unfortunately there are no errors anywhere.

@ApplegateR @staff good news I found a problem I had to add 'https://yourcodeoffice,donain.com'

I was putting it without https:// that why it loading too long and keep access to insecure certification or something bug on here but hey it work again

Yes, as far as I understand each Nextcloud would initiate a document edit session with its own document URL and token exchange, so those should be isolated from one another.

@nebulon I can't share the original document publicly, unfortunately, but the problem has disappeared after having raised the PHP Memory Limit in Nextcloud from 512 MB to 2 GB.

The reason for the crash was that the app by now needs more memory. The app package with more language packs is out now. However one needs to adjust the available languages in the coolwsd.xml via the filemanager, to enable them. An app restart afterwards is required.

This seems to be a highly app specific issue. As far as I remeber, code renders document tiles which is what appears to be rather slow for you. As those are possibly only very short amounts of time where cpu spikes, it may not show up, but might be worth looking at htop via SSH during scrolling and see if the CPU is the problem. Otherwise you probably have to seek help with the upstream project I guess.

@murgero ah thanks, pushed a fix. Both nextcloud and collabora links were broken.

@jdaviescoates Yes I still use mainly Collabora with Nextcloud and I have noticed tremendous improvements, especially since NC and Collabora have worked together to improve the integration.
However, I wouldn't say it is still quite like Google doc, or quite as fast as OnlyOffice. I tired OnlyOffice when I installed CryptPad and something about it feels more responsive than Collabora due to client rendering. It is basically just like editing on a desktop and Collabora is not quite there...but pretty close. Also we can feel that both Gdocs and OnlyOffice were designed as a collaborative editing tool whereas Collabora somewhat inherits the LO single user approach and tries to adapt it for collaboration and the result still does not feel quite as sleek....but here again it is getting much better than it used to be.
I can say that Collabora does not suffer from issues from the past, does not feel laggy and is perfectly fast enough to use while not feeling it's slow or weird. Also I do think it provides the most complete online office suit in terms of functionalities, and the best if you using open document formats.

@avatar1024 thanks we will update. The reason for it not being updated yet, is that their package repositories are usually lacking behind their release tag by a day and we have to wait for those.

It just so happens, that the whole file is now renamed in upstream since their loolwsd part is now called coolwsd 🙂

The package should do the config file rename and sed things for that renaming automatically.

Just to be 100% sure, are you using ownCloud and also are you using Cloudron? Cloudron had an ownCloud package but this has not been maintained for atleast 3 years now. Or maybe ownCloud is a non-Cloudron install but CODE is a Cloudron install? Please tell us more about your setup.

Looks like this is fixed upstream with next release then https://github.com/nextcloud/richdocuments/pull/1412