Nextcloud 10.2.0 and SMB Shares -> Collabora not working

[mx5gr]

Steps to reproduce

1. Sign in to Nextcloud
2. Go to an SMB-shared directory
3. Try to open/edit document

Expected behavior

Document should open for edit

Actual behavior

Collabora is launched, but either an error message regarding corrupted files is displayed (Read-only share) or a blank document (no contents) is shown (Read-write share)

Other information

Host OS: Ubuntu 24

Other valuable info

We are using the all-in-one docker version of nextcloud (version 10.2.0) and we have attached two external SMB shares, one as read-only and the other as read-write. The files are accessible within the nextcloud platform and we can download and/or upload them accordingly. The shares have being attached using a password locally-stored within the DB.

When we try to edit (or view) the files however using Collabora, we get two different kinds of errors...

For the Read-only share:

kit-00163-00163 2025-01-08 17:25:59.292640 +0200 [ kitbroker_003 ] ERR  ToMaster-00e: Failed to get LoKitDocument instance for [file:///tmp/user/docs/BYklEJn57xZb3AP7/oc_tmp_HPJjAj-.doc]| kit/ChildSession.cpp:927

wsd-00007-00179 2025-01-08 17:25:59.293956 +0200 [ docbroker_003 ] ERR  ToClient-00e: Document load failed: faileddocloading| wsd/ClientSession.cpp:1866

wsd-00007-00179 2025-01-08 17:25:59.294085 +0200 [ docbroker_003 ] ERR  Unexpected message: [o9 close: ].| wsd/DocumentBroker.cpp:3662

wsd-00007-00179 2025-01-08 17:25:59.294133 +0200 [ docbroker_003 ] WRN  #26: DocBroker [%2Fopt%2Fcool%2Fchild-roots%2F7-9b04fd52%2Ftmp%2Fincoming%2Fcool-QkHUmdwN2utQ3zFJ%2Foc_tmp_HPJjAj-.doc] got disconnected from its Kit (163) unexpectedly. Closing| wsd/COOLWSD.cpp:2918

frk-00013-00013 2025-01-08 17:26:01.296881 +0200 [ forkit ] WRN  The systemplate directory [/opt/cool/systemplate] is read-only, and at least [/opt/cool/systemplate//etc/hosts] is out-of-date. Will have to clone dynamic elements of systemplate to the jails. To restore optimal performance, make sure the files in [/opt/cool/systemplate/etc] are up-to-date.| common/JailUtil.cpp:585

frk-00013-00013 2025-01-08 17:26:28.836511 +0200 [ forkit ] WRN  The systemplate directory [/opt/cool/systemplate] is read-only, and at least [/opt/cool/systemplate//etc/hosts] is out-of-date. Will have to clone dynamic elements of systemplate to the jails. To restore optimal performance, make sure the files in [/opt/cool/systemplate/etc] are up-to-date.| common/JailUtil.cpp:585

kit-00187-00187 2025-01-08 17:26:29.236762 +0200 [ kitbroker_004 ] ERR  Failed to load: file:///tmp/user/docs/0ppBcYD5XWKX8iOn/%CE%91%CE%A0%CE%9F%CE%94%CE%9F%CE%A7%CE%97%20PARKING.doc, error: loadComponentFromURL returned an empty reference| kit/Kit.cpp:1985

kit-00187-00187 2025-01-08 17:26:29.237033 +0200 [ kitbroker_004 ] ERR  ToMaster-011: error: cmd=load kind=faileddocloading| common/Session.hpp:181

wsd-00007-00196 2025-01-08 17:26:29.237252 +0200 [ docbroker_004 ] ERR  ToClient-011: Document load failed: faileddocloading| wsd/ClientSession.cpp:1866
Failed to load the document. Setting TerminationFlagwsd-00007-00196 2025-01-08 17:26:29.237504 +0200 [ docbroker_004 ] ERR  Unexpected message: [o21 close: ].| wsd/DocumentBroker.cpp:3662

kit-00187-00187 2025-01-08 17:26:29.238150 +0200 [ kitbroker_004 ] FTL  Failed to load the document. Setting TerminationFlag| kit/Kit.cpp:2012

wsd-00007-00196 2025-01-08 17:26:29.238298 +0200 [ docbroker_004 ] WRN  #27: DocBroker [https%3A%2F%2Fmy.server.com%3A443%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F663770_ocnnlf8dlzvu] got disconnected from its Kit (187) unexpectedly. Closing| wsd/COOLWSD.cpp:2918

kit-00187-00187 2025-01-08 17:26:29.238242 +0200 [ kitbroker_004 ] ERR  ToMaster-011: Failed to get LoKitDocument instance for [file:///tmp/user/docs/0ppBcYD5XWKX8iOn/%CE%91%CE%A0%CE%9F%CE%94%CE%9F%CE%A7%CE%97%20PARKING.doc]| kit/ChildSession.cpp:927

kit-00187-00187 2025-01-08 17:26:29.237033 +0200 [ kitbroker_004 ] ERR  ToMaster-011: error: cmd=load kind=faileddocloading| common/Session.hpp:181

wsd-00007-00196 2025-01-08 17:26:29.237252 +0200 [ docbroker_004 ] ERR  ToClient-011: Document load failed: faileddocloading| wsd/ClientSession.cpp:1866
Failed to load the document. Setting TerminationFlagwsd-00007-00196 2025-01-08 17:26:29.237504 +0200 [ docbroker_004 ] ERR  Unexpected message: [o21 close: ].| wsd/DocumentBroker.cpp:3662

kit-00187-00187 2025-01-08 17:26:29.238150 +0200 [ kitbroker_004 ] FTL  Failed to load the document. Setting TerminationFlag| kit/Kit.cpp:2012

wsd-00007-00196 2025-01-08 17:26:29.238298 +0200 [ docbroker_004 ] WRN  #27: DocBroker [https%3A%2F%2Fthemis.photopoulos.com%3A443%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F663770_ocnnlf8dlzvu] got disconnected from its Kit (187) unexpectedly. Closing| wsd/COOLWSD.cpp:2918

kit-00187-00187 2025-01-08 17:26:29.238242 +0200 [ kitbroker_004 ] ERR  ToMaster-011: Failed to get LoKitDocument instance for [file:///tmp/user/docs/0ppBcYD5XWKX8iOn/%CE%91%CE%A0%CE%9F%CE%94%CE%9F%CE%A7%CE%97%20PARKING.doc]| kit/ChildSession.cpp:927

Regarding the SMB Read-write share however, the behavior is totally different:

frk-00013-00013 2025-01-08 17:28:07.390352 +0200 [ forkit ] WRN  The systemplate directory [/opt/cool/systemplate] is read-only, and at least [/opt/cool/systemplate//etc/hosts] is out-of-date. Will have to clone dynamic elements of systemplate to the jails. To restore optimal performance, make sure the files in [/opt/cool/systemplate/etc] are up-to-date.| common/JailUtil.cpp:585

wsd-00007-00028 2025-01-08 17:28:08.123105 +0200 [ websrv_poll ] ERR  FileServerRequestHandler: File not found: Invalid URI request (hash): [/browser/a4b67a7664/src/layer/tile/TileWorker.js].| wsd/FileServer.cpp:780

In both cases, however, either Collabora launches with an error being displayed regarding "corrupted files" (R/O case), whereas in the latter case (RW share), Collabora opens the document but its contents are empty.

Only files that are stored within the local Nextcloud storage can be opened/edited by Collabora, at this time.

Any help? ;)

[joshtrichards]

Do you have any log entries from your Nextcloud during these attempts?