Hello @peterokereke97 ,
To troubleshoot this issue can you please help us in following questions:
1. Are you using free plan for namecheap hosting? Can you ask your host enable REST API(Or upgrade the plan which includes REST API enabled) if its not enabled in free plan?
2. Do you see any browser console errors where that message displays?
3. The REST API is used to communicate with the Site Kit service. When you go to Tools -> Site Health, does it say the REST API is available?
4. Could you confirm the URLs in the WordPress settings?
Thanks & Regards,
Hello @abdullahramzan,
Thank you for responding as fast as you can.
Now, as regards your questions,
1. I’m using a paid plan for my web hosting. The NameCheap EasyWP is a managed Hosting plan. It’s not free. Also, I’m on the EasyWP Supersonic plan (which offers more Disk space and bandwidth up to 500k visitors, according to them). It goes for nearly $12 per month.
2. As for browser console errors, I don’t see any one as far as I can tell. Also, I’m using a mobile device to manage and update my site, which hinders some of the features in Chrome available to Desktop users.
3. When I check my Site Health screen, I can see that the REST API is fully enabled on my site. Check the link for screenshots: Site Health screen
4. Yes, definitely! The URLs in my site are two: one for my WP installation URL and the other for the Accessible site homepage (accessible to users). They’re as follows;
(a) Installation URL, (b) Accessible Site URL
Thank you and Best Regards
Thanks for providing all the information.
Can you please apply basic troubleshooting steps:
- 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”
- Attempt to setup Site Kit once more
You can exit troubleshooting mode afterwards.
Let us know if you are able to setup Site Kit in troubleshoot mode.
Best Regards,
Hello @abdullahramzan,
When I tried the troubleshoot mode in the Health Check and Troubleshooting Plugin, I got an error message:
“We were unable to copy the plugin file required to enable the Troubleshooting Mode.”
Hello @peterokereke97 ,
Thanks for the update.
If you click on the Debug Information tab, does it mention anything about any directories not being writable?
Hello @abdullahramzan,
Yes, when I checked the “Info” section under the Health Check screen, I could see a list of directories it could write to: “writable”.
But I found one it couldn’t write to. It’s the Must Use Plugins directory.
Thanks for getting back to us. You need to make it writeable by setting up permission through FTP/cPanel to perform the basic troubleshooting.
Unfortunately, I’m on NameCheap Managed Hosting (EasyWP) which does not use cPanel. However, I think there is a provision to use FTP via my EasyWP dashboard, but I don’t know how.
@peterokereke97 ,
You can follow this article by official WordPress Team to change the permissions for the Must Use directory. Let us know if you are unable to do this.
You can ask your host provider as well to make these changes for you.
Best Regards,
Hello @abdullahramzan,
I’ve tried following the article but it appears I can really implement those instructions better on PC. I’m using a mobile device, so I contacted my Host.
So far, while they’ve reproduced the error on their end, it appears to me that they’re confused about what to do.
Any help or should I contact them again?
Thanks.
@peterokereke97 ,
Yes!!! please ask your host to disable MU plugin for a while as its tricky to make changes through mobile device.
After disabling the Must Use plugin you need to apply basic troubleshooting steps provided above.
Best Regards,
@peterokereke97 Hi there! Checking in here – were you able to work with your hosting provider to change the permissions for the Must Use directory?
Hello @shetheliving,
Thanks for checking in. Unfortunately, my host has been unable to resolve the issues on my end.
@peterokereke97 Thanks for sharing the additional insights. From inspecting the URLs you provided (including the accessible URL) your site seems to be not available.
Can you check your site once more and share any insights you may have on it’s status?
@peterokereke97 As we haven’t received a response, I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist. Thank you!
