Nexcloud server error with recent package release V4.9.1-1

[privsec]

I am using the nextcloud windows desktop client v 3.2.5.

I have had no issues with syncing my audio/video files now for over a month or so.

Nextcloud app on cloudron updated to v4.9.1-1, no I keep getting a HTTP 500 error (Bad Signature) on almost all files its trying to sync.

I have reverted Nextcloud app to v4.9.0 to confirm, issue resolution.

[privsec]

@privsec

Please see my comments here https://forum.cloudron.io/post/32106

The recent auto update really hosed all my and my users data.

Nothing is accessible.

[girish]

@privsec So, there is some issue with 4.9.1 but not 4.9.0 ? 4.9.1 essentially updated Nextcloud to 21.0.2. I am not on Windows but we haven't heard to any sync issues on our support with the latest update. All our instances are on the latest nextcloud and I don't see any issues on linux/android as well. Are you see the 500 error in the nextcloud logs ? Can you post the entire error?

[privsec]

@girish Ill restart the syncing, and once it pops back up, ill send it your way.

Rolling back to 4.9.0 however did not resolve the issue.

[necrevistonnezr]

@privsec said in Nexcloud server error with recent package release V4.9.1-1:

I am using the nextcloud windows desktop client v 3.2.5.

Maybe stay away from unstable daily versions? Current stable is 3.2.1.

[girish]

Indeed, per https://nextcloud.com/install/#install-clients the latest windows client version is 3.2.1

[privsec]

@girish @necrevistonnezr I understand that there are unstable desktop apps. The issue has grown. The issue is not that the desktop app cant access the files, the issue is now that nextclouds update to v4.9.1 has corrupted something on the connection side to my wasabi storage.

I rolled back to v4.9.0 and I am getting this error for every file

To be clear this did not happen until the cloudron package updated to v4.9.1

I will test with the "stable version" of the desktop nextcloud app, however, I can replicate this exact same issue online directly within nextcloud. So the problem isnt the client side app.

The issue is that when the app upgraded from v4.9.0 to v4.9.1-1 something botched the encryption keys for the cloud storage to the point that even rolling back to v4.9.0 OR cloning the app from v4.9.0 doesnt work.

Emphasis added to highlight the root issue

[necrevistonnezr]

@privsec
It’s still very likely that the changes coming with the update itself are ok but not in combination with the „daily“ builds. Those releases are tested by Nextcloud staff with the stable versions of clients, not beta/alpha builds.
And again - did you use encryption and if so, which one? The e2e or the „standard“ encryption?

[privsec]

@necrevistonnezr
I use both for on prem storage and for wasabi storage