@giox069 Thanks. Good news first: the memory message is gone, so the Apache sandbox was behind that line. The remaining failure is something else.
The three lines you quoted are normal for the built-in server. The cache and proof-key messages appear on every built-in CODE install, and the seccomp warning is how the AppImage always runs. More telling is what is not there: no error at all when you try to open the document. That suggests the request never reaches coolwsd. Could you send:
- The exact message the browser shows now. Is it still “taking longer than expected”, or something else?
- Whether coolwsd is listening, and what the proxy reports:
ss -ltnp | grep 9983
curl -s https://YOUR-HOST/apps/richdocumentscode/proxy.php?status - All log lines, not only ERR/WRN, from the moment you open a document:
tail -60 $LOG
plus any richdocuments entries in nextcloud.log from the same minute.
One more thing worth trying in parallel: richdocumentscode 26.4.402 came out on 24 Sep, right when you upgraded, and two people on 24.04 report that documents stopped opening with it while 26.4.303 works (#355 (Built-in CODE 26.4.402 fails to open documents with "System exception"; downgrade to 26.4.303 fixes it · Issue #355 · CollaboraOnline/richdocumentscode · GitHub), #356 (26.4.402: Built-in CODE fails to auto-start, proxy.php waits indefinitely for coolwsd.pid · Issue #356 · CollaboraOnline/richdocumentscode · GitHub)). You can install 26.4.303 by hand from the releases page (Release 26.4.303 · CollaboraOnline/richdocumentscode · GitHub): disable the app, replace the apps/richdocumentscode folder, enable it again. If that fixes it, we know the Ubuntu sandbox was only half of the story.