Hi @nicelydonesites,
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 or it’s resolved.
Thank you for your patience.
Running an update to newest version yielded this error displayed. This happened on the site that needed the key re-added and verified.
Cannot run Solid Security. Error encountered during setup. Please try deactivating and reactivating Solid Security. Contact support if the error persists.
- Table ‘wp_itsec_dashboard_lockouts’ already exists
- Table ‘wp_itsec_vulnerabilities’ already exists
- Table ‘wp_itsec_firewall_rules’ already exists
- Table ‘wp_itsec_webauthn_users’ already exists
- Table ‘wp_itsec_webauthn_credentials’ already exists
- Duplicate column name ‘location_meta’
-
This reply was modified 1 year ago by
nicelydonesites. Reason: Added notes on which site was impacted
Yes, ALL my monitored sites same issue
We’re seeing the same thing. I have found that Enabling XML-RPC seems to allow the scan to run successfully, but obviously that introduces additional security risks.
Hello,
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:
- Clear all plugin and server-level caches – including browser, page, and CDN caches where applicable.
- Clear all site transients using a plugin or
wp transient delete --all via WP-CLI.
- 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.
