Hi @arielesp Thanks for reaching out. So we can determine more on this and ensure Site Kit works as expected for you please share the following:
- Your Site Health information. You can use this form to share privately if preferred.
- Before you moved your site to a new server, did you reset Site Kit? I ask as if not Site Kit may have remained connected on your previous site, referencing the same URL.
-
Did you use a plugin to migrate your site to your new server, or just copy the files over and move the database?
After we received the above we can suggest some troubleshooting suggestions, which may include not selecting Analytics in the set up process, should you be unable to complete set up, checking for hosting or third party plugin conflicts, or resetting Site Kit if you are the only connected user.
Looking forward to hearing from you.
I already sent the form above
I moved site from another host using all-in-one migration
I sent in form about error in browser console api permission 401
Many thanks for sharing these additional insights, very useful indeed. We do have an open GitHub issue in relation to the error you’re encountering, although we’ve been unable to recreate the exact same error or determine the cause so far. From checking the Site Health information report you kindly shared nothing obvious stands out.
As you’ve migrated the plugin, and you’re the only connected user, based on the information provided, what we can do next is reset Site Kit (Tools > Available Tools > Reset Site Kit). Note that this will result in you having to set up the plugin once more, and connect all previously connected services. This may help determine whether something went wrong during your site migration, in particular if the Site Kit dashboard works as exacted after resetting.
Let me know how you get on after resetting, or ask if you have any questions with the above.
@arielesp Just checking in here to see if you still require any assistance with this?
Hi @arielesp,
I’m just following up with you on this error which has since been resolved. Can you confirm that this no longer occurred after you reset the plugin, or was there another action you performed?