Hi @rainboy72, thanks for getting in touch and sharing the information you have. As you suspect, it looks like your host IP address is blocked from your IPv6 address. This can happen if your IP is within a specific range that includes some users from regions where Google services are blocked.
To check this further, please could you confirm your IPv6 address. If you are unsure on how to get this then you’ll be able to get this from your hosting provider. Once shared, I will get this checked to see if we can find any such block.
You can also try temporarily disabling IPv6 at host level to see if you can set up Site Kit. Let me know if you have any questions.
Ipv6 is not the issue, as it works correctly to any other website, but a block at google is possible (would not know why as we did not have any technical issues which may cause such incident) ; The outgoing IP : 2a01:4f8:201:3e2:0:0:0:2
Other servers (with a different /64) do not have this issue, and this server did work before as well, it just suddenly stopped working.
@rainboy72 Thanks for sharing the IPv6 address. I have requested a check on this from the internal team and will update here as soon as I hear back.
@rainboy72 Thanks for your patience while this was being checked. The team have confirmed with me that your IPv6 was blocked previously and is now cleared as of 4th October.
Are you still encountering this issue when checking Site Kit on your site?
would really wonder why that IP was blocked, but that aside, it still does not work and gives an error with the title: Error 403 (Forbidden)!!1
as before only over the IPv6 connection.
@rainboy72 I’m sorry to hear that your IPv6 may still be blocked. At the time of our checks, your IPv6 address was not blocked by Google. It was blocked briefly prior to this check but had been unblocked at the time of the check.
Unfortunately these blocks are out of our control so there is little we can do to change the status of them. You can however as mentioned previously try temporarily disabling IPv6 at host level which should then allow you to setup Site Kit on your site.
If you do decide to disable IPv6 to complete your Site Kit setup I would suggest enabling it once more after you complete setup. If you then run into anymore similar issues after setup completion then you can do the following to resolve this at the host level:
In order to have the IP address allowed, you can add an “IPGeo Feed“. The specification for this can be found here: https://datatracker.ietf.org/doc/html/rfc8805
Add a feed via the ISP portal. If you don’t have an account yet, you can fill out the request form(https://isp.google.com/partner_request/?data.request_type=ISP%20Portal%20Access). With an account you can immediately see processing status and errors. You will need to submit a feed URL at Configuration -> IP geolocation.
If you already have a feed that isn’t being picked up, we can email the internal team to request their review.
Let me know if there is anything further I can help you with.
Adam,
While i understand your answer, its not viable to just disable ipv6 on a server because a plugin only wants to communicate through it, or that they have setup blocks somewhere on the road, the only viable solution to this is removing the plugin. If that is the goal of google it seems we will do just that.
Thank you for your time
@rainboy72 I am sorry to hear that. If you do have any further questions then please do let us know or if you choose to try Site Kit at another time and run into any other issues, please feel free to reach out and we will help wherever we can.
