nextcloud / richdocuments

📑 Collabora Online for Nextcloud
https://nextcloud.com/collaboraonline
355 stars 116 forks source link

Server Side Encryption corrupts nextcloud office files #3116

Closed DenuxPlays closed 1 year ago

DenuxPlays commented 1 year ago

Steps to reproduce

  1. enable SSE
  2. create an odt document
  3. wait for a few days
  4. try to open it

Expected behavior

File opens normally

Actual behavior

image

Host OS

Fedora 38

Nextcloud AIO version

v7.0.0

Current channel

Beta

Other valuable info

Logs: image

Last error:

{"reqId":"AhdptbLrLWOI1WKkbxHY","level":3,"time":"2023-08-16T12:06:44+00:00","remoteAddr":"172.18.0.2","user":"--","app":"no app in context","method":"GET","url":"/index.php/apps/richdocuments/wopi/files/59427_ocr5zuv0acj4/contents?access_token=0LIpjPC1fPDU6fzabZpu9KeNULlgSnh0&access_token_ttl=1692223601000","message":"Cannot decrypt this file, probably this is a shared file. Please ask the file owner to reshare the file with you.","userAgent":"COOLWSD HTTP Agent 23.05.2.2","version":"27.0.2.1","data":[],"id":"64dcbc96d7eaf"}
michelleDeko commented 1 year ago

I have a similar problem with Nextcloud 27.0.2. Create a word / excel file, some hours later it gets corrupted (I encrypted all files). I can still open it but everything is gone (including the timelined files) And when downloading the file and open it with Word, it says its corrupted

DenuxPlays commented 1 year ago

I have a similar problem with Nextcloud 27.0.2. Create a word / excel file, some hours later it gets corrupted (I encrypted all files).

I can still open it but everything is gone (including the timelined files)

And when downloading the file and open it with Word, it says its corrupted

I disabled SSE but all corrupted files are gone. They couldn't be decrypted and there's nothing I can do. But disabling SSE saves more files from being corrupted.

juliusknorr commented 1 year ago

I cannot reproduce this anymore, I'll close this as a duplicate of https://github.com/nextcloud/richdocuments/issues/2996#issuecomment-1702546036. If you still encounter this please check the referenced comment for more details to provide.