Slightly OT:
If memory serves me correct that was supposed to be fixed in 12.0.2 (?). @LukasReschke feel free to correct me.
Both of those choices would be … bold. Not updating and potentially get pwned by a long fixed vulnerability.
So what’s your threat model? Why do you use encryption in the first place?
I’m all for it, but the server side encryption bit me in the ass a couple of times. I abandoned it long ago.
Privacy for a multi user Nextcloud instance or protection against someone physically reading from your drives?
Kudos for that. Everyone should, most people don’t.
Consider duplicity or rclone for encrypted off-site backups. Don’t invoke the wrath of lady luck.
well NC will we have any solution for this problem?
Its affecting many users and you should be paying attention to it.
I would like to inform future users of NC to NOT use the encryption because NC needs still a lot job to be done to use it in production and be stable and easy do correct any problems.
Hi! Same with my nextcloud "Falscher privater Schlüssel für die Verschlüsselungs-App. Bitte aktualisiere Deinen privaten Schlüssel in Deinen persönlichen Einstellungen um wieder Zugriff auf die verschlüsselten Dateien zu erhalten."
I’d really like to get rid of this.
Does someone know a solution? Or a workaround?
I really would like to read and test.
No, no solution or responces. I have left it that way and continue work it
like that. No affection at all with my installation. But wheeeen i find
time i will do a new install and move everything there if until then I
don’t find another more stable solution
I have the same problem, but I’m not sure if I had this after upgrade from 13.0.1 to 13.0.2 or after I did some disabling/enabling apps.
At least after disabling Default encryption module, I don’t get that line.
And I have never encrypted any files…
I have this issue, too. After upgrading from 12 to 13 on my old debian installation and after switching to Ubuntu with, of course, a fresh nextcloud installation.
I never used Encryption, too.
Still have the same problem here too.
Its annoying that no reply from the developers even not a small like, we are searching, we are trying or what ever
i do not know if this problem is still relevant for some people but:
i had the same error after transfering my nc to an other server and updating it from 13 to 14. i was able to fix the problem by correcting the instance id in the config file. i removed the ‘new’ id and replaced it with the id of my old instance and thats it.
OK, I just installed NC Today,
I installed the encryption module, then it prompted me to log out and log back in again,
Then I did and it has the same annoying error message,
I don’t know what’s going on, did someone report a bug?
Where do we report bugs?
I am going to close this topic. The reason is that there are likely many issues regarding the server-side encryption module that might or might not be related. However, it is very hard to follow up on this or reproduce errors.
If you can reproduce a bug on a new setup, it’s probably the best to submit this to the bug tracker https://github.com/nextcloud/server/issues, since the developers have problems in reproducing your errors.
On older systems, the search for errors can be much more painful and hard or impossible to reproduce. I had a lot of troubles myself with this app and I realized that I don’t really need it and the security benefits are very small if you don’t use it on external storage, it was designed for. Now it is even more true when the new client-side-encryption becomes available. If you can afford it, the enterprise subscription might be a way that Nextcloud gets some resources to further investigations in your problem.
