Hi, I have a problem with sending large files as an attachment. When the file is below 100MB, I can send it without any issues. However, when the file exceeds 100MB, the upload process starts for a second and then suddenly stops. I don't get any error messages. In the admin control panel, I have set an unlimited file size limit and allowed all extensions. I am sending a .rar package, but the file extension does not matter. The server configuration is correctly set up for sending large files with options like client_max_body_size = 2048m, post_max_size = 2048M, upload_max_filesize = 1024M. I am attaching a gif to illustrate the problem. Please help.

 

GIF TEST UPLOAD BIG FILE AND NORMAL

 

@Jim M

Edited October 17, 20231 yr by PanSevence

Would recommend disabling all third party applications/plugins and switching to an unmodified theme to just rule these items out. There should be an error which pops up at some juncture to warn the user the upload failed. If you are refreshing prior to that happening, I would just sit and await that to happen.

We have countless clients who run communities on our Cloud and self hosted which are able to. I’m afraid, you would need to continue to troubleshoot this with your hosting provider. 

When I set the column to big int, I can transfer the file without any issues. However, then I receive a critical error in the ACP database. Is there an option to prevent this so that after changing to big int I won't get this message?

The reason for the original issue is that 2180291008 is higher than 2147483647, which is the maximum value of an INT column if the column is signed, which is the default for INT - unsigned (for zero and positive numbers only) allows that limit to be doubled.

https://dev.mysql.com/doc/refman/5.7/en/integer-types.html

https://dev.mysql.com/doc/refman/8.0/en/integer-types.html

 

When I set the column to big int, I can transfer the file without any issues. However, then I receive a critical error in the ACP database. Is there an option to prevent this so that after changing to big int I won't get this message?

There is no way around it telling you that your table column is incorrect, as its not the original. I have reported internally as a bug however

Yes, the problem is that when I set it to unsigned, I can send a large file, but then in acp I receive a critical error.

@Marc Stridgen Is there a possibility that you will consider a larger column value as the default in the near future?

 

That would be for our developers to look into when looking at the bug report 🙂 

Is there any progress in this area? We cannot upload files larger than 2GB due to the column size limitation in the database. Manually changing these settings causes a significant issue with the database.

This is still an open bug report at present. I will see if we can get an update for you