Updating apps: Missing required header for this request: Content-Md5 or Bad Request

[AlejandroFNadal]

I am sharing this in case it is useful to somebody, and also in case I have done something wrong and someone can show it to me.

We updated from a version 2 to 3 in budibase. We host with docker compose using the budi tool. We updated the budi tool as well, although we updated it after running budi hosting --update. That might have caused this problem, I don't know. I did allowed the tool to edit the docker compose. After updating the budi tool I run it again, just in case.

After the first update from 2 to 3, I could update the internal apps with the graphical interface. Afterwards however, I started getting either Bad Gateway or Missing required header for this request: Content-Md5.

Things I needed to do:

1. Clear up the Accordion plugin. This plugin is now replaced by an internal budibase component of the exact same name. I had to delete the orphan key at minio which holded the plugin. The error was shown in the stack from backupClientLibrary ending in NoSuchKey: app_<id>/chunks/Accordion-DBTbMjUC.js. The Bad Gateway was coming a minute after starting the update
2. Then that error dissapeared but I was still getting bad gateway, just two minutes after: I added the following keys to bbapps:

HTTP_SERVER_TIMEOUT_MS: "600000"             
HTTP_REQUEST_TIMEOUT_MS: "600000"            
HTTP_KEEPALIVE_TIMEOUT_MS: "120000" 

And then actually modified the docker to push the bbproxy's nginx config to higher values for old timeouts. I am aware that my next full update will break those changes and I will see if that continues to work after a docker image update
3. The error became now 504: Missing required header for this request: Content-Md5

That is a Minio error: the AWS SDK uses flexible checksums and the version from minio was expecting Content Md5. I checked here: https://raw.githubusercontent.com/Budibase/budibase/master/hosting/docker-compose.yaml and I saw no changes to the minio image. I risked it and updated it pinning it to minio/minio:RELEASE.2025-09-07T16-13-09Z in the docker compose file and recreated it.

And after that I could successfully update the apps themselves.

@melohagan @ConorWebb96 I tag you here so you could perhaps have a look and see if this is an actual bug or something I landed myself into somehow.
Anyway, if someone else has one or a few of these problems, perhaps this helps.

Have a good one!
Alejandro Nadal