If you are not the person who raised this support topic and if you need support then per the forum guidelines please start your own topic.
https://wordpress.org/support/forum-user-guide/faq/#i-have-the-same-problem-can-i-just-reply-to-someone-elses-post-with-me-too
The many “I have this problem too” replies have been removed. Start your own topics, this is how these support forums work.
As the person who raised this support topic, I have to say that I greatly appreciate people chiming in that they are having the exact same problem on what seems to have added up to at least thousands of websites so far. It lets me know that this is not because I f***ed something up, and it raises the profile of the issue with the plugin developer. It’s actually not beneficial to have dozens of people reporting the same issue in separate tickets as opposed to having a central location — the original ticket — where people can share information about the issue and follow to know when it’s fixed. It seems inefficient to have every one of what is probably every user of this plugin do the work of collecting information to separately report the exact same issue, and I don’t want to tie up the developers’ time responding to a thousand separate tickets when I’d rather they be spending that time addressing issues in their code.
Hello,
For anyone having issues with the site scan failing, please try the following:
First: Clear all caches
This step would help in clearing the caching layers that may interfere with the Site Scan data, as the logs seem to indicate that the result was from May 19th.
The first thing to clear is the server cache, which is usually available in your hosting panel. If you’re unsure where to find it, reaching out to your host is the fastest way to have it cleared.
Next, clear the site page cache from your caching plugin (if you have it installed in your site). And if you’re using CDN like Cloudflare, clear the cache there, too.
Second: Clear all site transients
This step would help remove all expired WordPress transients that may hold on to older data. You can use a plugin like the Transients Manager to clear transients.
Third: Reset Solid Security’s Scheduler
This step would help reset Solid Security’s scheduled tasks.
To proceed, enable the advanced Debug menu by following this guide: https://solidwp.com/documentation/security/how-it-works/all-about-solid-securitys-debug-mode/
After enabling the Debug mode, go to your Security > Debug page and find the Scheduler table. Find the “Reset” button, click it, and wait for the next scheduled scan to run.
Please let me know how it goes after following these steps.
Hello,
When was the last failed site scan for any of your sites? Has it failed for any as of today? If so, please provide a timestamp from the log if possible.
Also, if you could run through those steps I provided on one site where it failed and let me know if the next scan goes through that would be great!
After following Brent’s steps, the next scheduled scan sent email with a different error message, as follows (from the log):
The scan failed to properly scan the site.
Error Message: Unable to determine if the scan target is allowed: Missing scan URL.
Error Code: site_verification_failed.missing_url
Array code => site_verification_failed.missing_url
data =>Array
url => https://freelittleartgalleries.art
Incidentally, if you want people to “provide the following details” to support, it would be courteous to design the page in such a way that it was actually possible to copy the text to the clipboard.
This really seems to me like something was released without adequate testing. If we’re going to have to follow a process this involved to fix the problem on what, as others have reported, might be hundreds of sites, this will not result in a bunch of glowing reviews.
Hello Tyler,
That error message is new and was resolved early today. All site scan issues should be good now. Please let me know if you get another error!
Toujours la même erreur sur 2 sites encore. On va patienter 24h pour voir si c’est ok pour tout le monde. Sinon, merci au modérateur de supprimer les messages à la hache.
