Support » Plugin: Wordfence Security - Firewall & Malware Scan » No logs on scanning feature after upgrade.

  • Resolved Shah Ahmad Yusof

    (@shahahmadyusof)


    Hi WordFence.

    I’m hosting with SiteGround and would like to use the latest PHP version available provided by my hosting company which is PHP v7.2.9. Currently, I’m using PHP v7.0.32 and have no issue with WordFence scanning feature.

    But as soon as I’m switching to upgrade to PHP v7.1.22 or v7.2.10, the scan stop giving me the log. Moreover, I have to keep refreshing the scan page (to see the blue ticks added) or otherwise, it will do nothing (freeze). Please take a look at below screenshots.

    Screenshot:-
    Scanning log with PHP v7.0.32: https://prnt.sc/l1yjjw
    Scanning log with PHP v7.1.22 & v7.2.10: https://prnt.sc/l1yjqh

    This log only come back if I switch back to PHP v7.0.32. Is there anything I can do to upgrade my PHP version while keeping this log? Thanks in advance.

    Shah.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi @shahahmadyusof,
    The log is fetched from the database. Can you please check two things

    1. Check the PHP error logs to see if any errors are happening.
    2. When you load the Scan page, keep the browser console open to see if there are any JavaScript errors or if any resources are failing to load on the page.

    Let me know how it goes!

    Hi @wfasa,

    Thank you for your reply. I already check it as you requested.

    Check the PHP error logs to see if any errors are happening.

    I don’t see any error on my PHP log.

    When you load the Scan page, keep the browser console open to see if there are any JavaScript errors or if any resources are failing to load on the page.

    This is the error I get when I switch to PHP v7.2.10. But there’s no error on current PHP v7.0.32. https://prnt.sc/l3qave

    Hi again,
    the screenshot shows a 500 Internal Server Error when attempting to load the Wordfence scan page. This error should be getting logged somewhere. Are you sure that your error log is actually logging the errors? We really need to know what that error is in order to figure out how to prevent it.

    Do you think you can try to provoke a PHP error just to make sure it get’s logged? You could also try enabling WP_DEBUG to see if you can catch errors in the debug.log that is created. You would add this to your wp-config.php file to get the debug.log.

    define( ‘WP_DEBUG’, true );
    define( ‘WP_DEBUG_LOG’, true );
    define( ‘WP_DEBUG_DISPLAY’, false );

    Theoretically a 500 error could also have something to do with .htaccess and in that case, the error would not get logged in PHP error logs. So one thing you could try is make sure you have a standard .htaccess file for WordPress and nothing more in it when you swap. If this was the case I would have expected it to affect all your pages though, not just the Wordfence pages. But I still wanted to mention it.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘No logs on scanning feature after upgrade.’ is closed to new replies.