WF 6.3.3 causes Server error 500

Have you tried putting the WF firewall in learning mode to learn the activity from those apps?

Thanks, I’ll try that. Meanwhile, I manually updated the .htaccess file to get my apps working again.

@meljturner more details regarding this “Server Error 500” should be in the server error log file, I suggest checking this file and let me know about any related error message, I want also to ask if you have the firewall configured to “Extended Protection” on this website?

Thanks.

The error 500 messages indicated a problem in a PHP class auto-loader from the F3 package (not my code) but I think the message was spurious and due to some memory problem with PHP. The log files were replete with entries like:
ALERT – script tried to increase memory_limit to 134217728 bytes which is above the allowed value (attacker ‘216.244.66.240’, file ‘/hsphere/local/home/c293684/mvtm.ca/mvt2/wp-content/plugins/wordfence/wordfence.php’, line 40)
ALERT – script tried to increase memory_limit to 134217728 bytes which is above the allowed value (attacker ‘216.244.66.240’, file ‘/hsphere/local/home/c293684/mvtm.ca/mvt2/wp-content/plugins/wordfence/wordfence.php’, line 40)
ALERT – script tried to increase memory_limit to 134217728 bytes which is above the allowed value (attacker ‘98.130.147.189’, file ‘/hsphere/local/home/c293684/mvtm.ca/mvt2/wp-content/plugins/wordfence/wordfence.php’, line 40)
[Sat Mar 11 03:07:52 2017] [error] [client 82.178.186.222] mod_machinegun: 82.178.186.222 -> mvtm.ca (wp-xmlrpc) rejected
ALERT – script tried to increase memory_limit to 134217728 bytes which is above the allowed value (attacker ‘82.178.186.222’, file ‘/hsphere/local/home/c293684/mvtm.ca/mvt2/wp-content/plugins/wordfence/wordfence.php’, line 40)
ALERT – script tried to increase memory_limit to 134217728 bytes which is above the allowed value (attacker ‘82.178.186.222’, file ‘/hsphere/local/home/c293684/mvtm.ca/mvt2/wp-content/plugins/wordfence/wordfence.php’, line 40)
[Sat Mar 11 03:08:01 2017] [error] [client 82.178.186.222] mod_machinegun: 82.178.186.222 -> mvtm.ca (wordpress) rejected

Do you have “memory_limit” set to lower than 128MB in php.ini file? also it seems that you are using “suhosin”, so you should also check “suhosin.memory_limit” value.

Both limits were set to 64M; I have increased them to 128M.

I left configuration in learning mode for a few days and retried the set up but the error 500 on my apps returned. Restoring the .htaccess and removing .user.ini cleared the error. Not retrying this.

I’ll need more details this “error 500” as it doesn’t seem to be related to a memory limit problem any more, I can see you mentioned auto-loader class error? perhaps you have the full error statement? was any of the Wordfence files referenced there?

Thanks.

• This reply was modified 7 years, 11 months ago by wfalaa.

I briefly reconfigured the wordfence firewall. The error 500 returned in my docroot-level apps though the wordpress site in a subdirectory (mvt2) continues to operate correctly.

Regarding the app error: it was reported as function call error:
Fatal error: unpack(): Type V: not enough input, need 4, have 0
I think this is a spurious message

this was within a framework autoload function that is stable code. On removal of the user.ini file in the docroot the error disappeared.

the log file contained these entries:
ALERT – script tried to increase memory_limit to 268435456 bytes which is above the allowed value (attacker ‘98.130.147.189’, file ‘/hsphere/local/home/c293684/mvtm.ca/mvt2/wp-content/plugins/wordfence/lib/wfUtils.php’, line 1128)
[Tue Mar 21 05:26:16 2017] [error] [client 81.26.136.136] mod_machinegun: 81.26.136.136 -> mvtm.ca (wp-xmlrpc) rejected
[Tue Mar 21 05:26:25 2017] [error] [client 81.26.136.136] mod_machinegun: 81.26.136.136 -> mvtm.ca (wordpress) rejected
[Tue Mar 21 05:26:34 2017] [error] [client 81.26.136.136] mod_machinegun: 81.26.136.136 -> mvtm.ca (wordpress) rejected
ALERT – script tried to increase memory_limit to 268435456 bytes which is above the allowed value (attacker ‘174.112.47.100’, file ‘/hsphere/local/home/c293684/mvtm.ca/mvt2/wp-includes/functions.php’, line 5595)
ALERT – script tried to increase memory_limit to 268435456 bytes which is above the allowed value (attacker ‘174.112.47.100’, file ‘/hsphere/local/home/c293684/mvtm.ca/mvt2/wp-includes/functions.php’, line 5595)
ALERT – script tried to increase memory_limit to 268435456 bytes which is above the allowed value (attacker ‘174.112.47.100’, file ‘/hsphere/local/home/c293684/mvtm.ca/mvt2/wp-includes/functions.php’, line 5595)
ALERT – script tried to increase memory_limit to 268435456 bytes which is above the allowed value (attacker ‘174.112.47.100’, file ‘/hsphere/local/home/c293684/mvtm.ca/mvt2/wp-includes/functions.php’, line 5595)
ALERT – script tried to increase memory_limit to 268435456 bytes which is above the allowed value (attacker ‘174.112.47.100’, file ‘/hsphere/local/home/c293684/mvtm.ca/mvt2/wp-includes/functions.php’, line 5595)
ALERT – script tried to increase memory_limit to 268435456 bytes which is above the allowed value (attacker ‘174.112.47.100’, file ‘/hsphere/local/home/c293684/mvtm.ca/mvt2/wp-includes/functions.php’, line 5595)
ALERT – script tried to increase memory_limit to 268435456 bytes which is above the allowed value (attacker ‘174.112.47.100’, file ‘/hsphere/local/home/c293684/mvtm.ca/mvt2/wp-includes/functions.php’, line 5595)
ALERT – script tried to increase memory_limit to 268435456 bytes which is above the allowed value (attacker ‘174.112.47.100’, file ‘/hsphere/local/home/c293684/mvtm.ca/mvt2/wp-includes/functions.php’, line 5595)
ALERT – script tried to increase memory_limit to 268435456 bytes which is above the allowed value (attacker ‘174.112.47.100’, file ‘/hsphere/local/home/c293684/mvtm.ca/mvt2/wp-includes/functions.php’, line 5595)

My IP at the time was 174.112.47.100 so still appears to me as a memory issue

I think in this “.user.ini” file in the root directory there is a line like that:
php_value auto_prepend_file 'path_to/wordfence-waf.php'

could you please confirm? because in the next update of the plugin there will be a fix for a similar “unpack(): Type V: not enough input, need 4, have 0” error related to the firewall, that’s why I asked if this error was referencing any Wordfence related files or not? I suggest waiting till the new update is released and re-check this issue.

Thanks.

Yes, the .user.ini file was:
; Wordfence WAF
auto_prepend_file = ‘/hsphere/local/home/c293684/mvtm.ca/mvt2/wordfence-waf.php’
; END Wordfence WAF

I have removed the file.

Hi @meljturner
Since I haven’t heard back from you I am assuming that the instructions helped you solve your issue so I am marking this topic as resolved.

If however, for whatever reason, you are still experiencing this issue and it is not resolved please respond to the post, which will move it back up the queue, and mark this topic as “not resolved”.

Thank you.