Sep 4th, 2012, 10:40 AM
I have resolved this problem. Some dedicated server hosts have certain settings set to where it's almost impossible to run an application without running into one issue or another. It's mostly due to security. Thankfully, there are configuration settings that can be tweaked and there are .htaccess rules that may be set in order to resolve certain issues.
In this case, the error didn't show up in my CPanel error logs but rather in the Mod Security log which is accessible only through WHM. This was the error:
ModSecurity: Output filter: Response body too large (over limit of 1024288, total not specified)
I have access to my server's root so I had gone into the apache directory and located this file: modsec2.conf
(Path on my server is: /usr/local/apache/conf/ - may not be the same on all dedicated servers)
I edited this line:
SecResponseBodyLimit 1024288
Just added 2 - 0's at the end so it would be 102428800 (Bytes)
I restarted apache then accessed formtools. I reset the clients per page to 25 and it worked! No more Internal Server Error.
If you don't manage your own dedicated server and are hosted and you run into this problem, you may need to contact your host and have him set this for you. He may be able to localize it to just your account through .htaccess rather than compromise his entire server's security.
In this case, the error didn't show up in my CPanel error logs but rather in the Mod Security log which is accessible only through WHM. This was the error:
ModSecurity: Output filter: Response body too large (over limit of 1024288, total not specified)
I have access to my server's root so I had gone into the apache directory and located this file: modsec2.conf
(Path on my server is: /usr/local/apache/conf/ - may not be the same on all dedicated servers)
I edited this line:
SecResponseBodyLimit 1024288
Just added 2 - 0's at the end so it would be 102428800 (Bytes)
I restarted apache then accessed formtools. I reset the clients per page to 25 and it worked! No more Internal Server Error.
If you don't manage your own dedicated server and are hosted and you run into this problem, you may need to contact your host and have him set this for you. He may be able to localize it to just your account through .htaccess rather than compromise his entire server's security.