[solved] Collabora - "document can not be saved on storage"

Hello/Bonjour,

when clicking on “save” icon in collabora, i have the following message (translated from french) : “document can not be saved on storage. Check your permissions or contact administrator of your storage server”*. However, saving of new editing in documents is effective. Besides storage is made on my Raspi with the adequate rights/permissions. So it’s not a big problem but i’d like to avoid this message.
Thanks for your help!
Eric

  • “Le document ne peut pas être enregistré sur le stockage. Vérifiez vos
    permissions ou contactez l’administrateur du serveur de stockage.”

I’m running into the same issue. The document fully saves, and when downloaded, the changes are there. Its basically just a weird popup.

Some information on our configuration. We’re running a nextcloud Univention docker install and a Collabora online docker as per this documentation. We’re using valid certs but one of the CA’s in the cert isnt trusted by nextcloud. After adding it to the ca-bundle I resolved the “Forbidden” issue.

It seems like everything is functional just that strange error message.

Thanks for the answer. Can you detail what it consists in? (i’m not an expert). I have nextcloud on a raspi and collabora running on an ubuntu aws free tier instance (https://www.linuxbabe.com/cloud-storage/integrate-collabora-online-server-nextcloud-ubuntu-16-04). It worked well until there.

I have the same problem : Le document ne peut pas être enregistré sur le stockage. Vérifiez vos permissions ou contactez l’administrateur du serveur de stockage.

I dont understand why ?

Same issue since last collabora update :slight_smile:

I have the same problem. I’m running the Collabora Docker image on a separate VM from NextCloud 11 (snap), behind an Apache SSL Proxy, set up with the official instructions.

Docker logs have an error similar to this this repeated many times:

wsd-00027-00049 18:21:37.226975 [ docbroker_002 ] WRN  Attempted ping on non-upgraded websocket!| ./net/WebSocketHandler.hpp:285

Along with the occasional:

wsd-00027-00049 18:18:19.931128 [ docbroker_002 ] WRN  Missing JSON property [HidePrintOption]| wsd/Storage.cpp:387
wsd-00027-00049 18:18:19.931348 [ docbroker_002 ] WRN  Missing JSON property [HideSaveOption]| wsd/Storage.cpp:387
wsd-00027-00049 18:18:19.931429 [ docbroker_002 ] WRN  Missing JSON property [HideExportOption]| wsd/Storage.cpp:387
wsd-00027-00049 18:18:19.931507 [ docbroker_002 ] WRN  Missing JSON property [EnableOwnerTermination]| wsd/Storage.cpp:387
wsd-00027-00049 18:18:19.931808 [ docbroker_002 ] WRN  Missing JSON property [DisablePrint]| wsd/Storage.cpp:387
wsd-00027-00049 18:18:19.931954 [ docbroker_002 ] WRN  Missing JSON property [DisableExport]| wsd/Storage.cpp:387
wsd-00027-00049 18:18:19.932044 [ docbroker_002 ] WRN  Missing JSON property [DisableCopy]| wsd/Storage.cpp:387
wsd-00027-00049 18:18:19.932118 [ docbroker_002 ] WRN  Missing JSON property [LastModifiedTime]| wsd/Storage.cpp:387

And the save error appears to be:

wsd-00027-00049 18:12:27.794262 [ docbroker_002 ] ERR  Failed to save docKey [<removed>.com/index.php/apps/richdocuments/wopi/files/1143_oco4q0ztfsg5] to URI [https://<removed>.com/index.php/apps/richdocuments/wopi/files/1143_oco4q0ztfsg5?access_token=<removed>&access_token_ttl=0&permission=edit]. Notifying client.| wsd/DocumentBroker.cpp:670

Any ideas?

wsd-00027-00049 18:12:27.794262 [ docbroker_002 ] ERR Failed to save docKey [.com/index.php/apps/richdocuments/wopi/files/1143_oco4q0ztfsg5] to URI [https://.com/index.php/apps/richdocuments/wopi/files/1143_oco4q0ztfsg5?access_token=&access_token_ttl=0&permission=edit]. Notifying client.| wsd/DocumentBroker.cpp:670

This is the relevant part. Can you paste some more lines around this too ?

Also, nextcloud server logs would be helpful too.

Sorry for the late response.

I tried some more troubleshooting myself, but couldn’t get it to go.

The release Snap hasn’t been updated to Nextcloud 12 yet (it’s on 11), and I got sick of the Snap locking me down, so I backed up the data and rolled Nextcloud 12 on my own Server. Collabora is working fine.

Ok, i understand that by installing Nextcloud12, you fired this problem, did you?
I heard about N12 but i’m not proposed to install it by the stable canal, it’s said to be update with 11.0.3.

Edit : update to Nextcloud 12 (and corresponding version of collabora) fix this problem!

Hello
I still have this trouble w/ Collabora :

Document cannot be saved to storage. Check your permissions or contact the storage server administrator.

I use Nextcloud 15.
Am I the only one :wink: ?

1 Like

I also do still have this error on several nextcloud-instances and I’am searching urgent for a solution! Any news?

Hello,

I also get this error recently :
nextcloud 15.0.5
richdocuments 3.3.1
code 4.0.3

Thanks

No news on the Collabora issue :sleepy:

Take a look here …
Its seems to me that a regular working nextcloud cron job ist very importing.

Regards