500 Error After PHP Upgrade

  • Resolved Nikole Garcia

    (@nhgnikole)


    2 years, 11 months ago

    After upgrading to PHP 8, the plugin’s firewall is blocking access wp-admin with a 500 error.

    [Wed Mar 23 13:32:37.172600 2022] [authz_core:error] [pid 31818:tid 47316316722944] [client 67.227.186.90:50810] AH01630: client denied by server configuration: /home/user/public_html/.user.ini, referer: https://www.domain.com/.user.ini

    Removed .user.ini, removed lines from htaccess, removed wordfence-waf.php.
    Admin loads fine.
    Tried setting up firewall again – same issue.

    Latest version of everything on the site. Only other plugin data in htaccess is from Wp Rocket.

Viewing 3 replies - 1 through 3 (of 3 total)

  • Hi @nhgnikole,

    Thanks for reaching out!

    Despite many WordPress sites being able to run on PHP8 without issue, there are some circumstances where we have also had to recommend rolling back to PHP7.4.

    Security support for PHP7.4 will continue until November 2022 so there is still time to run on this configuration until all active plugin developers have caught up with PHP8 issues that may be occurring. This may point to a conflict or a previous PHP 7.4 “warning” now being upgraded to a “fatal” error in PHP8.

    The 500 error you were seeing should be appearing in your PHP and/or server error logs, which should explain more detail around why exactly the error was thrown.

    If you visit Wordfence > Tools > Diagnostics and scroll down to Log Files you may be able to see ones that are available. If you don’t have log files there, your host may not allow you to see them by default. You may be able to get in touch with their support channels however to request any PHP errors that may have occurred at the timestamp the error 500 occurred.

    Please let me know how it goes?

    Thanks,

    Joshua

    Thread Starter Nikole Garcia

    (@nhgnikole)

    The error isn’t from a plugin and it’s not adding anything from the logs. The only error is the one I am posting above, and it happens directly after I try to enable the WordFence Firewall.

    Thread Starter Nikole Garcia

    (@nhgnikole)

    I reset all the logs and reloaded many times to discover that the memory was being exceeded with the addition of the firewall. Expanding PHP memory has fixed this.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘500 Error After PHP Upgrade’ is closed to new replies.