Hello and thanks for getting in touch. Sorry to hear you are having these issues. To help troubleshoot this would you please be able to provide the following:
- Your Site Health information. You can share here or privately via this form.
- Was Site Kit working before you experienced this issue?
I can also see looking at your site that you have mixed content console errors. Could you go to Settings > General and check that your WordPress Address (URL) and Site Address (URL) are both the same using https? If not then changing them both to https will resolve the mixed content errors.
Once I have this information I can assist further.
I am facing the same problem! What is the procedure to resolve?
@comendadormaranhao If you’d like to open a new support topic we’d be happy to assist with your case individually. Thank you!
Many thanks for sharing the additional insights @drewsan44. From checking your public REST Endpoints at present I do see some errors output.
With that can you you share the following:
- Does the same occur when you temporarily deactivate the “WPS Hide Login” plugin?
- Can you share any warnings or errors when checking your Site Health status, which differs to your Site Health information previously shared (Tools > Site Health > Status)?
Once we know the above we can then advise further. We may need to perform additional checks using the Health Check & Troubleshooting plugin.
Here’s the screenshot of site health. https://nimb.ws/gouLSX
I don’t intend to disable WPS Hide Login. It has prevented many attacks on my website. I’d disable/uninstall site kit before I do that.
Hi @drewsan44,
Thanks for sharing this additional information. It looks like there are issues with your REST API for this site. It may be something at host level or with your environment resulting in the REST error.
I don’t intend to disable WPS Hide Login. It has prevented many attacks on my website. I’d disable/uninstall site kit before I do that.
I understand. It was a temporarily check as opposed to permanently disabling, given some of the errors in your REST endpoints referenced this plugin. What you can do is use the Health Check & Troubleshooting as an alternative to deactivating other plugins if you wish, to check do the same errors appear with only Site Kit active. The instructions are below:
- Login to your site from a Chrome browser incognito window
- Install and activate the Health Check & Troubleshooting plugin.
- Navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot”.
- From the same screen click on the “Available Plugins” tab at the top right and then click on the “Enable” option next to “Site Kit by Google”
- Vie your Site Kit dashboards once more while also checking for any REST errors in your Site Health status
Let me know how you get on with the above. This will help rule out any third party plugins impacting your WordPress REST API, which Site Kit and other plugins depend on. I also found some fixing WordPress topics with the same error reported in your Site Health status. We can perform some additional checks with your hosting environment once we know more on the above.
@drewsan44 Checking in here – were you able to run through the checks above, and are you still having issues with the REST API issue?
Thanks for the followup. The issues/resolutions you suggested didn’t help at all really. The issue was resolved by this article: https://buildyourblog.net/problems/how-fix-deprecated-directive-allow_url_include-deprecated-unknown-line-0
Glad to hear you were able to resolve this. Thanks for the update.
