Stuck pointing at staging site

Thanks for reaching out @safecolads. Given you already performed a reset, your old site records on the Site Kit service may not be reachable. So we can determine more on your experience, and maybe reset the records if necessary, please share the following:

1. Your Site Health information. You can use this form to share privately if preferred.??
2. What is the URL you land back on when attempting setup? I ask as this may contain a no longer valid callback URL, based on your previous site.?If it includes an invalid callback (with a /staging reference, you may be able to manually correct this in order to proceed.
3. Do you still have access to the site on the staging server, with the staging path? If so, should Site Kit remain connected, you can reset the plugin on this site, before them cloning once more and moving this to your top level domain/root directly. Once it’s reset on staging, before being cloned or migrated, you should be able to complete set up.

Note that if you’re happy to change your default site prefix from using a www path to a non-www path or vice versa, I can guide you through the steps in order to proceed. Do let me know if you’re happy to do so.

Let me know if you have any questions with the above.

Hi James,

Thanks for the quick response, so to your Q’s below:

1. Just sent through the form.
2. When I get to step one of the set up it used to say you are the owner of site.com/staging – but weirdly it now looks like it is pointing at the correct url…

So I may have jumped the gun a bit as it now appears to point at the correct url today…

Please leave this topic open while I check everything is as expected but I may just not have waited long enough for the backend to catch up ??

Many thanks for sharing the additional information @safecolads. Certainly I’ll keep this support topic open while you perform some checks. I don’t see any obvious issues that may be impacting Site Kit set up on your site, although I can see that the public REST endpoints I checks are not accessible. This shouldn’t impact Site Kit set up if it’s limited to public/non-logged in traffic.

I’m just following up with you to check whether the error remains? If so, let me know and we can perform some additional checks or request a review of your site records on the Site Kit service.

Hi James,

This all appears to be working, think it just took a while to catch up.

• This reply was modified 3 weeks ago by safecolads.

Many thanks for the update @safecolads, glad to hear all is working well. Be sure to reach out if you have any further queries.