Site Kit cannot access the WordPress REST API. Please ensure it is enabled

  • Resolved cleebay

    (@cleebay)


    3 years, 4 months ago

    Hi,

    I have had sitekit on my websites (5) for a long time without any issues. A few days ago three of them stopped working with the error message……

    “Data error in Search Console

    <p>There has been a critical error on this website.</p><p>Learn more about troubleshooting WordPress.</p>

    Adsense placemements is not affected as ads are still showing and I am earning revenue. Analytics also working if I navigate to seacrh console etc…

    (The other two sites are working fine)….My sites run on the same server and with the same plugins and theme all updated to current versions.

    On one site this morning I decided to reset the sitekit and now have this error message when trying to set up…

    Site Kit cannot access the WordPress REST API. Please ensure it is enabled on your site.

    My site health is green with zero errors and healthcheck reports no plugin conflicts…the WordPress REST API is ENABLED….

    I have spoken to my hosts (Hostek, formerly Pickaweb) and they say there have been no changes to the server.

    I see by searching that many people are reporting this same issue.

    Any help would be appreciated as now I am unable to setup sitekit on this site and I am losing adsense revenue and analytics data.

    Thankyou

Viewing 6 replies - 16 through 21 (of 21 total)
  • Thread Starter cleebay

    (@cleebay)

    Hi @jamesosborne

    The previous message was not from me (the original poster on this topic)….

    I will take the steps you mentioned and let you know how it works out

    Thread Starter cleebay

    (@cleebay)

    @jamesosborne

    Hi and thanks for all the help and advice….

    On the second uninstall and re install attempt, clearing cache on my local machine I was able to re install and set up Sitekit correctly… All working fine so I’ll go ahead and uninstall and re install on the other sites with the same errors….

    Once again, thanks for your input and I hope that this topic helps others with the same or similar issue…

    Regards…

    Plugin Support James Osborne

    (@jamesosborne)

    @cleebay Great to hear it, many thanks for the follow up. I’m happy to keep this support topic open while you confirm the same fix for the other impacted sites. I wonder did this occur based on a particular Litespeed caching configuration, with unusual behavior from automatic plugin updates.

    Plugin Support James Osborne

    (@jamesosborne)

    @cleebay Just following up to see if you’ve had an opportunity to check whether the same fix applies for any of the other sites?

    Thread Starter cleebay

    (@cleebay)

    Yes @jamesosborne, thanks for keeping the topic open..

    The other two sites with the same issue are now fixed after uninstalling and re in stalling

    Its odd though that one needed three re install atempts and the other just one….

    I guess it must be server related but my hosts have no idea as to what caused the issue…

    The solution for poeple with similar issues in the future seems to be uninstall, reinstall and re connect with the sitekit services again… And if it doesn’t work first time try it again..

    Than you for your support @jamesosborne

    Plugin Support James Osborne

    (@jamesosborne)

    Very odd behaviour indeed, I can’t be sure what was the cause. We’ve also been in discussions with our engineers while testing impacted users hosting setups, without finding anything obvious that could be resulting in this notice. Impacted users such as yourself do seem to be have some type of Litespeed hosting integration, there may have been some caching interference during plugin updates.

    If you happen to encounter any further issue be sure to reach out, and if you’ve been using Site Kit for a while we’d love to hear how you’re finding the plugin so far.

Viewing 6 replies - 16 through 21 (of 21 total)
  • The topic ‘Site Kit cannot access the WordPress REST API. Please ensure it is enabled’ is closed to new replies.