-
Posts
-
We started this as a thread at:
We moved to a new shared webhosting provideer, and now we get this “A Site Check has failed” error, and we have followed all the recommended steps (CLI commands), checked Logs, and still we are not able to find what triggers it, and how to resolve it.
The log just shows:
2021-06-17 13:00:12 [ERR] Site Check: FailedPlease help.
Thanks.
Hi Manuel-
Thanks for starting a new thread, and thanks for using Total Upkeep.
I consulted with the developers, and we were able to find one rare case where you might receive a blank site check failure.
As a part of the routine Site Check process, one of the steps is an automated script that tests if WordPress is successfully loading from the command line of your server. If the server doesn’t provide any method for Total Upkeep to run a command, it might receive nothing but a blank response.
Can you check Total Upkeep > Preflight Check and tell me what’s listed under the General Tests > Execution Functions Available section?
All seems to be normal, I have a Functionality test status: PASS status.
And regarding the specific Execution Functions Available I get the following output:
popen, proc_open, exec, shell_exec, passthru, systemJesse, thank you very much for your support, indeed we do not see a reason for this to pass and Total Upkeep being such an amazing product, we want to be sure all is working perfectly fine.
Hi Manuel-
Thanks for confirming the execution functions! Everything looks good there.
One possibility that I can think of in this case is that your new web host might have some kind of security software, such as Apache mod_security or another Web Application Firewall (WAF), that could be blocking the execution of the self test.
If you’re on a shared hosting platform, your web host may be able to check their logs if you can provide them with the timestamp of the failed site check from your log. On a VPS, you should be able to check these yourself as well.
Another possibility I can think of is that your new host may have your PHP error_reporting or log_errors settings set to disable logging, or at least set to a very low level. You’ll need to have log_errors set to true, and error_reporting of at least E_ERROR and E_WARNING. Your host should either have documentation on how to set these up, or be able to assist you with making those changes.
- The topic ‘Total Upkeep reporting “A Site Check has failed” but no error is shown’ is closed to new replies.
