So, I have a deployment of Nextcloud 32.0.3 using the official Docker image on PikaPods, with Nextcloud Office 9.0.2 and CODE 25.4.702 built-in apps installed. Whensoever I open a rich document, there is a popup that says I have server audit warnings:
Documents are not effectively contained: missing capabilities or namespaces.
Slow Kit jail setup with copying, cannot bind-mount.
Poorly performing proxying of all network requests.
There are no documentation links for any of these. I researched especially the last one, as I have noted that the performance of real-time editing operations is exceptionally poor (it takes the better part of a second for keystrokes to show up in the document), but was unable to find any information whatsoever, other than tracking down the actual line of code generating the warning (which was not very insightful for me to read).
What should I do about these warnings? Do any of them indicate an actual problem? Are any of them likely to be related to the high latency I observe on typing?
• The warnings are about container and network limitations, not errors.
• On PikaPods you usually can’t fix them.
• Only this one matters for your issue: “Poorly performing proxying of all network requests.”
• That is very likely the reason for your slow typing / input lag.
• The others mainly affect sandboxing and startup time, not live editing.
So:
Nothing is broken.
Performance is limited by how Collabora traffic is proxied in your hosting environment.
For faster typing, you’d need a self-hosted setup with proper networking (WebSockets, fewer proxies).
For faster typing, you’d need a self-hosted setup with proper networking (WebSockets, fewer proxies).
Is there any documentation on what the “proper networking” configuration would be? I created a self-hosted instance using the standard nextcloud:30 Docker image, and by default it exhibits exactly the same warning.
I could report an issue against the maintainers of that image, but I think first I would need to know what Collabora prefers in terms of configuration, before I can ask for the default configuration of the Nextcloud image to be changed.
Oh, I see, by “self-hosted” did you mean a self-hosted instance of Collabora Online, as opposed to using the built-in CODE server? I had initially assumed you meant a self-hosted instance of Nextcloud, as opposed to using one provided by e.g. PikaPods.
I admit I’m a bit confused as to why using the built-in server would result in bad networking performance; after all I would expect that keeping the data within localhost would in fact be lower latency. But it sounds like there is a limitation with the richdocuments proxy configuration where it doesn’t support persistent websocket connections, and so the frontend falls back to an inferior request pattern when using the built-in CODE server.
Hmmm, okay. I set up a Collabora Online server running on a different host, and configured my Nextcloud instance to use that CODE server instead of the built-in one.
Now, the warnings in the popup are gone (except one that complains about insufficient hardware resources). However, typing latency is the same as before.
I can’t imagine why back-end server resources could possibly result in a front-end lag when typing; there should not be any round-trip involved simply to put the characters visually on the page (of course then actually submitting the edit to the server to be persisted would be expected to take some time, and to show an error if it failed).
What am I missing here? Do other people just live with there being a noticeable delay between keystrokes and text showing up on the page? It seems pretty bad.
