Mattermost large file upload issue

[potemkin_ai]

Hello!

I believe I faced some issue: I needed to upload 195Mb file to my local hosted Mattermost with S3 to host files (from my virtual machine provider, not AWS). The file was reported to be uploaded Ok (after I adjusted the settings on Console to upload such a large uploads, but then we try to download it, it just give 8Mb file.

If try to download it via public link, it gives back all 195Mb, but the archive is corrupted.

I also checked my S3 storage, and there are 39 files - all of them of 5Mb, except for one (the last one), which 1,35Mb (screenshot attached).

I tried to Google the issue, and it says it could be something related to nginx upload settings.

Any glue?

[girish]

@potemkin_ai said in Mattermost large file upload issue:

I needed to upload 195Mb file to my local hosted Mattermost with S3 to host files

If I understand correctly, you have configured mattermost to store files on s3. You then uploaded file via mattermost and you are finding that the uploaded files are corrupt. Is this the case?

[potemkin_ai]

@girish said in Mattermost large file upload issue:

@potemkin_ai said in Mattermost large file upload issue:

I needed to upload 195Mb file to my local hosted Mattermost with S3 to host files

If I understand correctly, you have configured mattermost to store files on s3. You then uploaded file via mattermost and you are finding that the uploaded files are corrupt. Is this the case?

Thank you for the clarification! Not sure that it's corrupt - it doesn't download in full; and when it does - it is corrupt, indeed.

[girish]

@potemkin_ai https://docs.mattermost.com/configure/configuration-settings.html?highlight=s3#file-storage says that they haven't tested with many S3 providers - just DO spaces and minio other than s3. So, maybe that's the issue.

[potemkin_ai]

@girish thanks for getting back! I guess it could be the issue, but I don’t expect things to be very different and this provider is used by quite a lot of the clients without any issues.

Let me see if I will be able to get some history in here and shall I then send a feedback to Mattermost, I guess?

[girish]

@potemkin_ai yes, correct, letting the mattermost folks know would be the next step since this does not look like a packaging issue.