Thread Starter
Joanna
(@joannacraig)
Having looked through other posts, I can now see that others are reporting the same issue. My errors started on 19 May as well. So it seems to be an issue that is not related to individual sites but the plugin/scanning service as its impacting so many across different hosts etc.
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:
- 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.
Thread Starter
Joanna
(@joannacraig)
I have so far 3 sites with the same error. I also can’t find the debug menu item.
When “chatting” with the online help of Solid Security I found that the following has to be entered in wp-config.php to enable debugging.
define( 'ITSEC_DEBUG', true );
After that I found the debug-menu and was able to reset the schedule.
Hopefully this will prevent new mails with this old data being sent…
