ModSecurity: Multipart parsing error: Multipart: Failed to create file: /var/imunify360/tmp_modsec/
While trying to upload attachments greater than 1MB, users encounter a 400 bad request error.
Bad Request
Your browser sent a request that this server could not understand.
While looking at the apache error logs I see some errors about imunify360 failing to create a file in a temporary directory, and then failing to read it. I appreciate any advice on how to resolve this issue.
[security2:error] [pid 45365:tid 45365] [client x] [client x] ModSecurity: Multipart parsing error: Multipart: Failed to create file: /var/imunify360/tmp_modsec/x...
[Tue Dec 09 20:38:46.024178 2025] [security2:error] [pid 45365:tid 45365] [client x] [client x] ModSecurity: Failed to open temporary file for reading: /var/imunify360/tmp_modsec/x...
[Tue Dec 09 20:38:46.024216 2025] [proxy:error] [pid 45365:tid 45365] (20014)Internal error ( specific information not available): [client x] AH010 95: prefetch request body failed to /opt/cpanel/ea-php/root/usr/var/run/php-fpm/x...
[Tue Dec 09 20:38:46.026071 2025] [security2:error] [pid 45365:tid 45365] [client x] [client x] ModSecurity: Input filter: Failed to delete temporary file: /var/imunify360/tmp_modsec/x...
-
Hey there! I'm wondering if there is a custom ModSecurity ruleset being used on this system, as that is usually what is behind that particular error. Can you let me know what you have configured in WHM >> ModSecurity Vendors so we can rule that out as the issue?
0 -
The imunify360 ruleset is enabled and subscribed to updates. All rules enabled. No customizations.
0 -
I'm afraid I don't have other ideas on this one, as this doesn't seem to be a common error. It would probably be best to create a ticket so this can be investigated directly on the server.
0
Please sign in to leave a comment.
Comments
3 comments