@raulmego Thanks for opening a support topic and for sharing the information. As nothing stands out here, this could be and based on the error you’re encountering, it is possible that your host IP address is blocked, however, this may only be from your IPv6 address (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. You can share this here or via the site health form privately. 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 perform the below cURL commands, which can help indicate whether this is a block specific to IPv6 if you are comfortable doing this:
curl -4 -I https://sitekit.withgoogle.com
The above will check the status if communication over IPv4
curl -6 -I https://sitekit.withgoogle.com
The above will check the status if communication over IPv6
If there is a block, I suspect this will be over IPv6 only, with a 500 error. Let me know if you have any questions about the above.
Thanks for the response, I alredy send the IPv6 thru the form
[root@miranda ~]# curl -6 -I https://sitekit.withgoogle.com
HTTP/2 403
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
[root@miranda ~]# curl -4 -I https://sitekit.withgoogle.com
HTTP/2 200
content-type: text/html
vary: Accept-Encoding
x-cloud-trace-context: 80f71628d9f9ec6aff347ee66713bd69
date: Tue, 28 Nov 2023 03:37:56 GMT
server: Google Frontend
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
@raulmego Thank you for sharing the information. From those responses you have shared it does look like your IPv6 address is blocked. I will confirm this first with the team and update you once I hear back from them.
@raulmego Thanks for your patience with this while I awaited the response from the check. I can confirm now that your IPv6 address is blocked. These blocks are out of our control unfortunately but we are currently working on a solution for users impacted by these. You can follow our GitHub issue for more updates here.
You may also be able to get around this if you have the option to disable IPv6 from your hosting platform. If this is an option, you can disable this while connecting Site Kit. It is recommended that you then enable once Site Kit is up and running.
GREAT!!!
Disable IPV6 on the server just temporaly if the server reboot IPV6 start again.
Only useful on CentOs Linux
echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6
- Uninstall SiteKit
- Reinstall
- Reconnect
Voila!
Thanks in advance, I prefer to keep IPV6 enable because the plugin fail when I enable IPV6 service. But is a start point to solve the issue.
Best Regards.
Raul Mendez
@raulmego Delighted to hear you were able to use this as a workaround in the meantime. Please do feel free to follow updates on the issue with regards to a solution but if you have any other questions then please let me know and I will be happy to help!
