[Bug]: Computed md5 hash is incorrect

[hammeractual]

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

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

Bug description

Error "Computed md5 hash is incorrect" thrown in Log, while sync files with Nextcloud Desktop App.

Steps to reproduce

1. Sync files with Nextcloud Desktop App
2. Error happened

Expected behavior

All files synced successfully without any error.

Which files are affected by this bug

No Info

Operating system

Windows

Which version of the operating system you are running.

Windows 10

Package

Appimage

Nextcloud Server version

28.0.3

Nextcloud Desktop Client version

3.9.2

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

Fresh desktop client install

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

{
  "reqId": "besBygdQGUBcpR9EWcvo",
  "level": 3,
  "time": "2024-03-05T14:22:44+07:00",
  "remoteAddr": "x.x.x.x",
  "user": "e2d350ce-6ebf-103d-84cd-addc165358a8",
  "app": "no app in context",
  "method": "POST",
  "url": "/remote.php/dav/bulk",
  "message": "Computed md5 hash is incorrect.",
  "userAgent": "Mozilla/5.0 (Windows) mirall/3.9.2stable-Win64 (build 20230808) (Nextcloud, windows-10.0.19045 ClientArchitecture: x86_64 OsArchitecture: x86_64)",
  "version": "28.0.3.2",
  "data": [],
  "id": "65e7e7f79d32c"
}

Additional info

No response

[egnrse]

I have the same problem. (I am on an old(ish) version though)

I'm not sure how helpful it is, but in case it can help here is my story.
Everything worked fine for me until I tried to sync my whole music library (>20GB) over nextcloud. After I got a BadRequest error a few times, whenever I try to sync up (this specific folder, the others that I previously set up work fine) from the machine with the original Data (there was data in the folder when I linked it to nextcloud over the gui) i get the "Computed md5 hash is incorrect." error and my nextcloud app on windows (that tried to do the uploading) freezes.

other infos:
17.8GB got uploaded before it crashes faster than any progress is done.
I am one version behind on the nextcloud server.
I can download the uploaded content on my linux machine with the native nextcloud app without problems.

"userAgent": "Mozilla/5.0 (Windows) mirall/3.12.1stable-Win64 (build 20240306) (Nextcloud, windows-10.0.19045 ClientArchitecture: x86_64 OsArchitecture: x86_64)",
"version": "28.0.2.5",

BadRequest Expected filesize of 6348595 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 3097600 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.

[joshtrichards]

Related: nextcloud/server#29984

[mwildam]

Same problem with server side Nextcloud 28.0.5.1 on debian 11 (bullseye) with php 8.2 and all updates applied.
On client side nextCloud Desktop client 3.4.2 (ubuntu-6.5.0-28-generic) on Ubuntu 22.04 (again all updates applied).

I do not have network limits set. Desktop client stands there showing "waiting..." in the settings dialog and I unfortunately I cannot find anywhere an information what it is waiting for. And actually it happens since I added (another) folder with a lot of subdirectories and files. I tried several times pausing, quitting, restarting the sync. Somehow by accident the client in the settings dialog where the sync process is shown, it showed me an error:

: server hat "404 Not Found" auf "MOVE https://" geantwortet"
which means server responded with 404 on the MOVE request.

I investigated the exact folder and found a lot of directories and subdirectories with 0-byte size (so no contents). I moved the folder on the client to a different location and deleted the folder via Nextcloud web interface. Then sync continued for a while but currently hanging again at different point - again with "Warte..." (=waiting). It would already help a lot if the client would show some information on what it is waiting for. -
But it had a different error then shown in the server logs:
PHP Request Startup: POST Content-Length of 87320780 bytes exceeds the limit of 52428800 bytes at Unknown#0
Last operation found was syncing a very old .url file (from very old windows days). I deleted that and again sync continued for a while. Then it hanged again with content length error. I tried again in smaller pieces which worked. Then I experienced "Too many open files" errors on the desktop client. However, after a few seconds on such errors the sync process continous - but not very convincing...

But finally - with the hint of the "too many open files" error I was able to solve the problem by
sudo vim /var/www/html/nextcloud/config/config.php
and adding this line::
'bulkupload.enabled' => false,
followed by command
sudo systemctl restart apache2
I cannot even see really a performance difference and a further positive side effect is, that the displayed approximate upload remaining time and bytes is correctly shown. Before it was changing all the time, sometimes to something totally different.

I do now get a warning from time to time in the server logs:

DeadlockException An exception occurred while executing a query: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction
Error while updating parent storage_mtime, should be safe to ignore

But that looks save.

[PhilippSchlesinger]

Same problem with server side Nextcloud 28.0.5.1 on debian 11 (bullseye) with php 8.2 and all updates applied. On client side nextCloud Desktop client 3.4.2 (ubuntu-6.5.0-28-generic) on Ubuntu 22.04 (again all updates applied).

@mwildam The client version you use is more than three years old and at least some of the problems you describe should be resolved since.
The recent stable version is 3.12.4 (3.13.0 being just released but facing some bugs). Maybe you have the possibility to retest with a recent version? (On Ubuntu you can use this PPA https://launchpad.net/~nextcloud-devs/+archive/ubuntu/client)

[mwildam]

Oh, on my daily driver I have a current version - the one where 3.4.2 is running is the PC of my wife. Wondering, why - although all updates applied, she still got that 3.4.2. ... - OK, I have the appropriate extra repository added on my machine. Anyway, disabling the bulkupload solved the problem even for the old client.

[EddyXorb]

i have the same issue using client 3.12.6 and server 29.0.3

[MightyCreak]

Same issue, I have 342 errors in the log in the past 7 days.

Clients:

• Desktop: 3.13.2 (Linux - Fedora 40)
• Android: 3.29.1 (Android - F-Droid)

Server:

• 29.0.4 (Linux - Ubuntu 20.04)

[gregorij89]

Hi, the same issue here. NC server version 30.0.1.2, windows desktop client 3.14. Network limit disabled, but still this error was presented and upload stucked. Adding 'bulkupload.enabled' => false, helped, but the upload is way slower than before.

[BC48329]

I had to turn off "bulkupload" as well. Uploads are slower but doesn't pause and throw as many errors, although still have a few.

nc 29.0.1