Solid Security

Troubleshooting Kadence Security Site Scan Errors

Coming soon: Solid Security is becoming Kadence Security. You may see both names used while we update the product, documentation, and customer experience.

This guide covers common Site Scan failures and error codes in Security → Logs. To copy full log output, see Diagnosis Tips: Raw Details of Site Scanner Logs. For what Site Scans check, how to run manual scans, and how to enable scheduled scans, see All about Kadence Security Site Scans.

Whenever Kadence Security runs a Site Scan, a log for that activity is recorded on Security → Logs. Viewing the log’s Raw Details provides in-depth information about the scan.

In some cases, the scans may encounter an error, and you’ll be notified. Looking at the raw details is one of the best ways to troubleshoot these issues.

Here are some common errors that may occur during a scan:

cURL error 28

When you see the cURL error 28: Operation timed out after x milliseconds In your logs, this indicates that the scan timed out due to an issue with the server or other conditions. 

This error is server-related and might be temporary, but if it keeps appearing, it’s best to check the server logs for clues about why the timeout occurred. Some of the areas you can check with your host are:

  • Issues with WP Cron
  • Check if loopback is disabled
  • Server firewall or ModSecurity rule blocking the outgoing cURL requests

Exceeded rate limit

Getting a rate-limit error indicates that the scan ran too many times in a row. The logs would include this message: “Exceeded rate limit. Please wait x seconds.”. Waiting for the cooldown time should resolve it.

However, if you keep getting rate-limited, it’s most likely due to a combination of this setup:

  • Running the Basic version of Kadence Security
  • Shared hosting 

Kadence Security (free/basic) has a 10-minute rate limit that is tied to the server’s IP address, and when you install the plugin on your sites that are on a shared hosting setup, these sites will appear as a “single” site to Kadence Security, which makes it think all those scans were coming from the same site, thus, it triggers the rate limit.

To resolve this, it’s recommended to either increase server resources, modify the site scan cron jobs and stagger them (with the help of your host), or consider upgrading to the Pro version.

Invalid response or Invalid JSON

This means a NON-JSON response was encountered during the scan. Some tips to resolve this:

  • Ensure that your server allows the required REST HTTP methods: GET, POST, PUT, PATCH, DELETE, and OPTIONS.
  • Ensure that you’re not blocking the scanner’s IP address: 207.246.255.60 from your server firewall, security plugin, or CDN firewall.

Getting the site_verification_failed.invalid_json, the error code can also be related to a licensing issue, so double-check your plugin’s license and try to renew it. See SolidWP Licensing: How to make sure your site is licensed correctly.

Cloudflare 524 Timeout Error

In some cases, the “Invalid JSON” or “Temporary Server Error” messages in Site Scan logs may appear with additional details showing a Cloudflare 524 timeout response, such as:

invalid_json => Invalid JSON.  
itsec-temporary-server-error => Site Scanning is temporarily unavailable, please try again later.  
error_data => <!DOCTYPE html> ... <title>itsec-site-scanner.ithemes.com | 524: A timeout occurred</title>

This indicates that the Kadence Security Site Scanner successfully connected to the site, but the server took too long to respond, causing Cloudflare to terminate the connection.

How to resolve:

  • Check the server logs for possible performance issues or processes causing the delays.
  • Review Cloudflare’s guide on Error 524: A Timeout Occurred

403 Connection error

There are different cases where this error code: site_verification_failed.connection_error pops up in the logs and usually tells you which areas to check to resolve it.

For instance, the below indicates that the scanner’s IP is being blocked, preventing the scan from running successfully:

Unable to determine if the scan target is allowed: Target site returned invalid response. The site scanner was forbidden from accessing your site. Please check if the IP address 207.246.255.60 has been blocked.

The below indicates that something is disabling the REST API on your site:

Unable to determine if the scan target is allowed: Target site returned invalid response. Do you have a plugin that disables access to the REST API? For instance, Coming Soon Page, W3 Total Cache, Password Protected, Members, Profile Builder, Disable Login, Clearfy, Disable REST API, REST API Toolbox, Defender Security, Shield Security, or Force Login? Try turning off that feature and using Restricted REST API Access in Kadence Security instead.

Could not verify keypair: Token not found.

This means that when Kadence Security attempted to verify the key pair, the server timed out.

Keypair verification should only occur when the plugin isn’t licensed. If you’re using the Pro version and it’s licensed but you’re getting this error, it’s most often due to an old WP instance still up somewhere that’s running an unlicensed version of Kadence Security.

Double-check with your host (including previous hosts if you’ve migrated the site to a different server) and make sure the site is disabled/deleted properly and/or Kadence Security is disabled.

Pro tip: Clear the transients on your live site as part of troubleshooting to make sure old data of the keypair data aren’t being picked up by the scans.

Not Found 

When you see this kind of information on your scheduled site scans:

  • Error Message: Not Found
  • Error Code: not_found
  • Error Message: Internal Server Error
  • Error Code: internal_server_error

It can mean that the Kadence Security server may be having a temporary downtime. In this case, contact the Software Support team via your Software Portal account to notify them or check the status.

Missing scan URL

If you see the “Missing scan URL” or site_verification_failed.missing_url error, it means the Site Scanner could not verify your website’s URL, most likely due to a malformed Authorization header, which prevents Kadence Security from making a proper request.

Common causes of the site’s Authorization header being malformed are: a plugin (security, caching, or optimization) that modifies or blocks the header, or the server’s outgoing HTTP proxy interfering with the scan. In some cases, an incorrect or missing scan URL in Kadence Security’s settings can also lead to this error.

First, ensure that the Licensed URL is correct under Settings → Nexcess Licensing (legacy installs use this path: Settings → SolidWP Licensing; See SolidWP Licensing: How to Make sure your site is licensed correctly). If the issue persists, try disabling any security, caching, or optimization plugins one at a time, then manually run a scan to see if the error resolves.

If the problem is not related to a plugin, check with your hosting provider for possible restrictions on the Authorization header or blocking/filtering outgoing HTTP requests.

If your site uses a proxy service such as Cloudflare, review its settings to ensure they are not interfering with the scan request. You can also check your server logs (such as /wp-content/debug.log) for additional clues on what might be causing the error.

If none of these helped, reach out to the Software Support team with details on your site setup and the steps you’ve taken.

Invalid Signature

This is usually due to having incorrect or corrupted licensing details. To resolve this, double-check the plugin’s license credentials and the Licensed URL field. 

You can also try to remove the existing license and add it back: SolidWP Licensing: How to Make sure your site is licensed correctly

Your site’s SSL certificate is invalid

This error means that the scanner cannot validate the SSL certificate on your site, even if it appears fine in modern browsers. In Security Logs Raw Details, you might see:

Error Code: site_verification_failed.connection_error
Error Message: “Unable to determine if the scan target is allowed: Target site returned invalid response. Your site’s SSL certificate is invalid.”

Some tips to resolve this:

  • Double-check that your SSL certificate is valid, not expired, and installed correctly.
  • Ensure that TLS 1.2 alongside TLS 1.3 is enabled on your server and any mapped subdomains.
    • If using Cloudflare, follow this guide to enable TLS 1.2 support: Minimum TLS Version (see Zone-level).
  • Verify there are no SSL chain or hostname mismatch issues (you can use tools like SSL Labs or SSL Shopper to confirm).
Filed under Solid Security
Last updated: November 11, 2026
Was this page helpful?
Thanks for the feedback!