• Resolved kmp2

    (@kmp2)


    Hello.

    Next scheduled scan: October 28, 2024 9:36 am (4 days from now).

    “Now” is 31 October 2024. At this rate, Ninja will never scan my site’s files again, since its “future” scan date is in fact in the past by four days. See screenshot: https://u.pcloud.link/publink/show?code=XZTuKX5Zr3SVg8B79rVq6VbRUJhNfbCBYGik

    Furthermore, it’s giving a message identifying 19,409 files in a red numeral, but when I hit scan, NOTHING comes up, no pages are produced for me to delete. The scan icon just spins and spins and spins around. Maybe due to the date issue? Is this fixable?

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author Lars Koudal

    (@lkoudal)

    Hello kmp2,

    Thank you for reaching out and providing details on the issue.

    This is indeed unusual behavior, and we’d like to help you troubleshoot it. Could you check for any error messages in the JavaScript console? These might offer clues as to why the scan isn’t progressing as expected.

    The Security Ninja scan is triggered daily through a WordPress cron job (secnin_run_core_scanner), which relies on WordPress’s internal cron system to execute. If you’re seeing a past date for the “Next scheduled scan,” it’s possible there’s an issue with cron jobs on your site.

    To investigate further, you might try using a plugin like WP Crontrol. This tool can help you locate the secnin_run_core_scanner cron job. If you find it, delete it and then reload the Security Ninja page to recreate and reschedule the job to run as soon as possible.

    Please note, however, that if your WordPress cron jobs aren’t running as they should (for example, if they’re delayed or stuck), WP Crontrol should flag any delayed jobs. In that case, you may want to investigate server-related cron settings or consult your hosting provider to ensure they’re correctly configured.

    Let us know if these steps help or if you encounter any issues along the way. We’re here to assist until this is resolved.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.