You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Hi there, I am running an encrypted Nextcloud. After an update from NC 29.0.8 to NC 30.0.2 some collectives did not open anymore. In the logs there were errors about: "Cannot decrypt this file"
I did a rollback to 29.0.8. but still I could not open these collectives anymore.
After further investigation of encryption, I found out, collectives has a special folder for keys "files_encryption/keys/files/Collectives". But my affected collectives did not show up there. So I looked into backups, from a time when it definitely worked fine, and those collectives also did not have their own keys in that folder, but did open after some strange long loading time.
Describe the bug
Hi there, I am running an encrypted Nextcloud. After an update from NC 29.0.8 to NC 30.0.2 some collectives did not open anymore. In the logs there were errors about: "Cannot decrypt this file"
I did a rollback to 29.0.8. but still I could not open these collectives anymore.
After further investigation of encryption, I found out, collectives has a special folder for keys "files_encryption/keys/files/Collectives". But my affected collectives did not show up there. So I looked into backups, from a time when it definitely worked fine, and those collectives also did not have their own keys in that folder, but did open after some strange long loading time.
Any ideas how to get my collectives working again?
I discribed it with some more details here: https://help.nextcloud.com/t/encryption-fails-after-update-nc-29-0-8-to-nc-30-0-2/211434
To Reproduce
I don't know how to reproduce
Expected behavior
There are no keys under "files_encryption/keys/files/Collectives", expected them to be there.
Screenshots
https://help.nextcloud.com/t/encryption-fails-after-update-nc-29-0-8-to-nc-30-0-2/211434
Server details:
The text was updated successfully, but these errors were encountered: