Hi @lovefoti,
Thanks for reaching out. We are aware that some users are reporting the same error when trying to connect Site Kit at present. We’ve been doing testing on this, where we were able to recreate the same error but only in cases whereby hosting providers resolve the the Site Kit service domain (sitekit.withgoogle.com) using the services IPv6 address.
From our testing these blocks occur also without using the plugin, when performing ping or cURL checks, again only arising if resolving the domain using IPv6.
If you’re comfortable with cURL commands can you check both the below:
curl -6 -I https://sitekit.withgoogle.com
If you are unsure on how to perform this check then you can check with a website admin or your hosting provider. I suspect this check, which ensures IPv6 is used, will result in the same 403 error.
curl -4 -I https://sitekit.withgoogle.com
This check may allow you to connect, with a successful 200 error.
Let me know how you get on with the above commands. If you are able to communicate with the second command, an IPv4 check, please share your Site Health information. You can use this form to share privately if preferred and I can inspect your environment. Please include your hosting provider where requested.
We have checked for any blocks on the Google side for impacted users similar to your own, checking their host IPv6 address. There were no blocks from the IP addressed we checked. In addition, the IPv6 address for the Site Kit service may change, which is why it’s more suitable to perform a check with sitekit.withgoogle.com rather than the IP address. If you wish to include your own server IPv6 address I can also see if we can perform another check on our side.
Note also that for users like you, who were previously impacted, from those who were able to temporarily deactivate IPv6 at host level, they confirmed that after doing so they were able to complete set up. If you have the ability to do so, you may wish to check the same, before then enabling IPv6 once more after set up. This isn’t ideal of course, in particular as you have hundreds of sites, but it may be useful to help determine a more underlying issue.
Looking forward to hearing from you. Let me know if you have any questions with the above.
