[Bug]:Einrichtungsfehler für verschlüsselte Metadateien

[Githopp192]

⚠️ Before submitting, please verify the following: ⚠️

• [X] This is a bug, not a question or a configuration issue.
• [X] This issue is not already reported on Github (I've searched it).
• [X] Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• [X] I agree to follow Nextcloud's Code of Conduct

Bug description

Nextcloud Desktop Agent on Windows 11 is reporting:

It seem's the Agent is not syncing anymore to and from the cloud

Steps to reproduce

1. After syncing some file on Browser - this error occurred
2. When disabling encryption from the Nexctloud Desktop Gui, the error disappears
3. When re-enabling encryption from the Nexctloud Desktop Gui, the error re-appears

Expected behavior

No sync errors

Which files are affected by this bug

IMG_1799.jpg

Operating system

Windows

Which version of the operating system you are running.

Windows 11 Home 22H2

Package

Other

Nextcloud Server version

29.00.4

Nextcloud Desktop Client version

3.13.2

Is this bug present after an update or on a fresh install?

Updated from a minor version (ex. 3.4.2 to 3.4.4)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

• [ ] Default internal user-backend
• [ ] LDAP/ Active Directory
• [ ] SSO - SAML
• [ ] Other

Nextcloud Server logs

No response

Additional info

No response

[Githopp192]

i had to 👍

1. after disabling e2e - syncing some folder got stuck a certain point .. and the sync process did not continue. re-starting the Agent did not solve this - repair install did not solve this, too - so i had to do the following ==>

2. logoff from Desktop Agent Account

3. Downgrade Agent from 3.13.2 (this agent has got other unresolved issues - not stable) to 3.13.1

see ==> https://github.com/nextcloud/desktop/issues/6917

4. Complete Re-Sync to new Folder
5. Re-Enable e2e with old/current key

Cause unknown - but seems to be a e2e issue ...

[Githopp192]

found this into the nextcloud.log ==>

{"file":"/var/www/html/nextcloud/lib/public/BackgroundJob/TimedJob.php","line":92,"function":"start","class":"OCP\BackgroundJob\TimedJob","type":"->"},{"file":"/var/www/html/nextcloud/cron.php","line":177,"function":"execute","class":"OCP\BackgroundJob\TimedJob","type":"->"}],"File":"/var/www/html/nextcloud/apps/files_antivirus/lib/Scanner/ExternalClam.php","Line":41,"message":"Error while generating metadata for fileid 864814","exception":{},"CustomMessage":"Error while generating metadata for fileid 864814"}}

May be AV also got issues with metadata file id ?