Wasabi S3 Backend File Upload Problem

[myaspm]

Wasabi S3 Backend File Upload Problem

[amyblais]

Opened: https://mattermost.atlassian.net/browse/MM-58677

[RiffleHatch]

Hi,
I am also using Wasabi and facing the same issue.
The problem started on version 9.8.0 and continues in 9.8.1.
It began on June 5th.
The OS is Ubuntu 22.04.4.
Mattermost is the Enterprise Edition.

[amyblais]

Hi @myaspm, what Mattermost server version are you on? Do you see errors in the Mattermost server logs?

[myaspm]

Hi, i'm on 9.8.1 now but the problem is also on 9.2 and 9.0. I even downgraded one instance to 8.X but can't remember now what the specific version vas.

The full error message i'm getting is below:

{"timestamp":"2024-06-06 14:34:13.180 Z","level":"error","msg":"Unable to write the file.","caller":"web/context.go:115","path":"/api/v4/files","request_id":"p4gdbqhbntdyibnzdiw5czt5jr","ip_addr":"X.X.X.X","user_id":"1grwc17gdt8b8fimz7c47su4fy","method":"POST","err_where":"WriteFile","http_code":500,"error":"WriteFile: Unable to write the file., unable write the data in the file 20240606/teams/noteam/channels/oyee43whatgj7m4qmdoni7yyhh/users/1grwc17gdt8b8fimz7c47su4fy/xgr9jct9ipbqtem3icwsxtwo9y/XXX: Value for x-amz-checksum-crc32c header is invalid."}

[hibobmaster]

Same here. Tested on mattermost v9.8.0~v9.9.0

error [2024-06-11 12:24:22.993 +08:00] Unable to write the file. caller="web/context.go:115" path=/api/v4/files request_id=6o71wtgtf3g6pxrshfdgfp7pco ip_addr=(redacted) user_id=5ojjqyzc8p8u8n1wow53oh8eia method=POST err_where=WriteFile http_code=500 error="WriteFile: Unable to write the file., unable write the data in the file 20240611/teams/noteam/channels/toez5ibyopri5d7twtc5sm5axh/users/5ojjqyzc8p8u8n1wow53oh8eia/qmeczk8fp3b1mkewj46mkgn6xc/Snipaste_2024-06-11_00-16-08.jpg: Value for x-amz-checksum-crc32c header is invalid."
debug [2024-06-11 12:24:22.993 +08:00] Received HTTP request caller="web/handlers.go:187" method=POST url=/api/v4/files request_id=6o71wtgtf3g6pxrshfdgfp7pco user_id=5ojjqyzc8p8u8n1wow53oh8eia status_code=500