Scan Failure

  • David

    (@dihetherington)


    10 months, 3 weeks ago

    Hello,

    I have multiple websites and from this morning I have received scan failure emails for all my sites, some use cloudflare, some do not. Below if I look in the log files (I replaced the actual website address with website):

    id => 5817 module => site-scanner type => warning code => scan-failure-client-error timestamp => 2025-05-22 10:32:48 init_timestamp => 2025-05-22 10:32:48 remote_ip => 217.181.22.6 user_id => 1 url => https://www.website/wp-json/ithemes-security/v1/site-scanner/scans?_locale=user memory_current => 10537368 memory_peak => 10941616 data =>Array results =>Object WP_Error errors =>Array site_verification_failed.missing_url =>Array 0 => Unable to determine if the scan target is allowed: Missing scan URL. error_data =>Array site_verification_failed.missing_url =>Array url => https://www.website cached =>[boolean] false

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter David

    (@dihetherington)

    10 months, 3 weeks ago

    Is this the Firewall API? tried that no difference

    Plugin Support chandelierrr

    (@shanedelierrr)

    10 months, 3 weeks ago

    Hi @dihetherington,

    Glad you reached out, and thank you for flagging this!

    We’re currently investigating this error with the Site Scanner. I’ll follow up here once I have an update on its nature or once it’s resolved.

    Thank you for your patience.

    Plugin Support Brent Wilson

    (@bwbama)

    10 months, 3 weeks ago

    Hello,

    Just wanted to give an update here. All issues related to the Site Scan should be resolved now.

    For context, we hit different errors related to the Site Scanner this week:
    1) invalid_json error last Monday (May 19th) due to a network issue, but it is now resolved according to our logs.

    2) site_verification_failed.missing_url error today, which is due to a configuration update that caused the Authorization header (which the Site Scanner needs) to not make it to the application. This is resolved now, too. To confirm, please run a manual scan on your site and confirm that it’s successful via Security > Logs page.

    3) Ongoing invalid_json error emails, which contain outdated results showing the May 19th scan result. We believe this is a case of stuck/cached data. If you’re still experiencing this, please follow these troubleshooting steps:

    1. Clear all plugin and server-level caches – including browser, page, and CDN caches where applicable.
    2. Clear all site transients using a plugin or wp transient delete --all via WP-CLI.
    3. Reset Solid Security’s scheduler after enabling debug mode, in Security > Debug, schedule tab > Reset.

    Another customer also mentioned that an outdated Google Analytics code was causing a JSON error that interrupted the scan, so if you have GA set up on your site, I’d recommend checking it, too.

    Please let me know how it goes with the scans and whether you’re still getting the errors.

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

The topic ‘Scan Failure’ is closed to new replies.