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
while using owncloud CentOS 7 and migrating to Almalinux 8.9 all worked well.
Upgrade to Almalinux 9.3 was successfully done.
In all OSes the last ownCloud 10.13.4 (stable) from "isv:ownCloud:server:10.repo" with default encryption module 1.6.1 is installed.
Now, when trying to up- or download this error is shown in a yellow window: Failed to upload the file "xyz.cfg": Encryption not ready: multikeyencryption failed error:0480006C:PEM routines::no start line
I found something similar in #342 concerning Ubuntu 22.04 but no solution there.
The issue seems to be based in system-wide usage of openssl 3 and I found something what might solve the problem here, but I have no idea how to implement that into owncloud.
Could possibly someone help and post a method how precisely owncloud with file encryption can be brought back to work again?
Thanks in advance - Ingo
The text was updated successfully, but these errors were encountered:
Hi all,
while using owncloud CentOS 7 and migrating to Almalinux 8.9 all worked well.
Upgrade to Almalinux 9.3 was successfully done.
In all OSes the last ownCloud 10.13.4 (stable) from "isv:ownCloud:server:10.repo" with default encryption module 1.6.1 is installed.
Now, when trying to up- or download this error is shown in a yellow window:
Failed to upload the file "xyz.cfg": Encryption not ready: multikeyencryption failed error:0480006C:PEM routines::no start line
I found something similar in #342 concerning Ubuntu 22.04 but no solution there.
The issue seems to be based in system-wide usage of openssl 3 and I found something what might solve the problem here, but I have no idea how to implement that into owncloud.
Could possibly someone help and post a method how precisely owncloud with file encryption can be brought back to work again?
Thanks in advance - Ingo
The text was updated successfully, but these errors were encountered: