Site Health Errors
I have been seeing issues with my site where some products are not processing correctly.
In "Tools/Site Health" there are two Critical Issues showing up:
1) AN ACTIVE PHP SESSION WAS DETECTED
A PHP session was created by a session_start() function call. This interferes with REST API and loopback requests. The session should be closed by session_write_close() before making any HTTP requests.
2) THE REST API ENCOUNTERED AN ERROR
The REST API is one way WordPress, and other applications, communicate with the server. One example is the block editor screen, which relies on this to display, and save, your posts and pages.
The REST API request failed due to an error.
Error: cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received (http_request_failed)
This only happened after the last couple of BETHeme updates were applied, so does anyone know where to look to fix these issues?
Comments
Hello,
1) Please turn off all of the plugins, refresh your cache, and check if the problem persists.
Moreover, if you are using a child theme, switch to parent, and recheck it.
2) You can see that this issue is about connection timeout, and the problem is not theme-related. It is all about the hosting provider. He should already recognize and amend this issue by looking at the error message.
Please read these related links:
https://github.com/anhskohbo/no-captcha/issues/87
https://github.com/docksal/docksal/issues/312
https://wordpress.org/support/topic/curl-error-28-operation-timed-out-after-30001-milliseconds-with-0-bytes-receive/
https://toolset.com/forums/topic/update-failed-download-failed-curl-error-28-operation-timed-out-after-300000/
This is not a new issue. Many users have this problem, and it always gets fixed with the help of the hosting provider. Therefore, we assure you that the problem is not on our side.
Thanks
I started turning off my plugins one at a time, and it appears that the rogue plugin is the CaptainForm one, as when i turned it off, the error messages went away, and when i re-enabled the CaptainForm plugin, the errors returned.
I have written to the Captain Form support team to see if they know why.
I am glad that you found the root cause.
If I can help you with anything else, please, let me know.
Thanks