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.

@Jim M I have contacted the administrator, we tried many different configurations of php, nginx and apache2 but unfortunately the problem still exists. We are out of ideas on how to solve this issue hence this topic. Why does it look like only 1 fragment is being sent and the connection is interrupted with a larger file than 100mb. How can I diagnose the problem? We tried higher and lower php configurations to no avail. I need to transfer larger files for my community.

2 minutes ago, PanSevence said:

@Jim M I have contacted the administrator, we tried many different configurations of php, nginx and apache2 but unfortunately the problem still exists. We are out of ideas on how to solve this issue hence this topic. Why does it look like only 1 fragment is being sent and the connection is interrupted with a larger file than 100mb. How can I diagnose the problem? We tried higher and lower php configurations to no avail. I need to transfer larger files for my community.

You would need to diagnose this at a server-level, I'm afraid. As it is a server error, we cannot tell you what and why this is happening.

If you use a WAF, like CloudFlare, ensure you're not exceeding any pre-set limits inherent in that service either.

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. 

I understand that I probably won't get any tips here that would solve the problem, but thank you for trying to help. I will continue to try to solve this issue. It's unfortunate that there's nobody in support who handles your cloud, as I might then get more technical guidance.

5 minutes ago, PanSevence said:

It's unfortunate that there's nobody in support who handles your cloud, as I might then get more technical guidance.

I'm not quite sure what you mean here as I do provide support to our Cloud, as well. We would only provide software support for our Classic (self-hosted) licensed individuals. Supplying PHP configurations, like you are asking for, would be outside of that support as it is supporting servers, rather than software.

Outside of the information already provided, working with your hosting provider on why you are having issues here would be the best method of support as they should be able to capture the error which is happening here while the upload is being processed on the server and help you troubleshoot it.

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

17 minutes ago, PanSevence said:

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