Please see associated completed form with Site Health Info
Thanks for reaching out, and sharing your Site Health information. Based on the troubleshooting steps you’ve undertaken, I suspect that what’s happened was Site Kit has some invalid records for your current site, gathered when your site was hosted elsewhere. So we can determine more on this, please share the following:
- Did you have a different wp-admin path on your previous host when Site Kit was successfully setup, before migrating? I ask as it looks like you’re not using the standard wp-admin path at present.
- Does the same occur if you temporarily deactivate WP Hide & Security Enhancer and WPS Hide Login? This works differently to when you used the Health Check & Troubleshooting plugin before.
- Do you see any warnings or errors when checking your Site Health status (Tools > Site Health > Status), which differs from your Site Health information previously shared?
Let me know if you have any questions with the above.
Hi James,
Thanks for getting back to me. In answering your questions:
1 – Yes it did have a dofferent path. Hide My WP Ghost was previously installed, but it caused some issues after the migration and was removed in favour of WP Hide & Security Enhancer.
2 – Yes, exactly the same. I just ran through that exercise again.
3 – No, only some recommendations. I completed a new site health check and form after those two plugins were disabled. I have include the details within the form.
Thanks again for your help.
Appreciate you sharing the additional insights @shootmanagement. Are you able to revert to the same custom wp-admin path temporarily, and attempt Site Kit setup from there? By that I mean the last custom wp-admin path you had active when you had Site Kit successfully connected, possibly with the Hide My WP Ghost plugin. If so, set up may possibly proceed.
If not, I can reset a reset of all your site records on the service, which may include your invalid callback URLs.
Thanks also for sharing your Site Health information. I didn’t see anything obvious that may be causing this loop, but it does seem to be based on a pervious set up and now invalid callback URLs.
Hi, thanks for getting back to me.
is it possible to advise what the login url is that sitekit is trying to use? There are a few possibilities, but likely would have started with /p or /s or /n if you could let me know the first letter I’d be able to change the path back.
Thanks again for your help.
Unfortunately it’s not something I can check @shootmanagement. For site checks like this we submit a request for such checks. If you’re happy for me to request a site check let me know. As it may take a few days for this to be complete, you may wish to check any of the possible paths you may have used before. If you can revert to the same path, it’s very possible you can complete Site Kit setup. After doing so you can reset the plugin from there, before then switching back to any custom wp-admin path you like.
Let me know if you have any questions with the above.