Hi @ingereck,
Thanks for reaching out, and appreciate you sharing all the troubleshooting steps you’ve undertaken. Based on your comments I suspect there may be something at host level impacting Site Kit setup, possibly a firewall or cURL configuration. So we can determine more, please share the following:
- Your Site Health information. You can use this form to share privately if preferred.
- When attempting set up from a Chrome browser incognito window do you see any browser console errors on the same screen where this notice appears? If so please share any such errors.
- To rule out any local software impacting setup, can you confirm that you have no problems setting up Site Kit on this disposable WordPress site?
While you’re sharing the above I’ll also see if I can perform a check from the same hosting platform. Let me know if you have any questions with the above.
2. From Chrome browser incognito window in the Google Site Kit Dashboard I see the error message: google_api_connection_fail, no errors in the browser console. When I hit the “Sign in with Google” button, I see a GET 500 error:
https://transform-schauspielschule.de/wp-admin/index.php?action=googlesitekit_proxy_setup_start&nonce= ….
3. No problems setting up Site Kit on the above mentioned disposable website.
Many thanks for your patience on this @ingereck. I’ve signed up to Webdoc.io myself and after setting a couple of servers I am finding some 403 errors when communicating directly with the Site Kit service from the host terminal.
Unfortunately I’ll need to check this further with the team. The problem from testing seems to occur if your webserver resolves the Site Kit service address using the IPv6 address only.
While I don’t have a workaround for this at this point, I will keep you updated as soon as I have more information on this.
Hi @ingereck,
Many thanks for your patience on this. After checking for blocks on the Google side from your hosting IP address we couldn’t can find any suck blocks or restrictions. Based on this, it’s possible that any blocks are as a result of your server or IP v6 configurations at host level.
Can you check with your hosting provider to see if you’re able to temporarily disable IPv6 address usage before attempting Site Kit set up once more? Here’s one guide that may be useful. I ask as I expect you to be able to complete set up if the connection to sitekit.withgoogle.com resolves to the IP v4 address.
I got the same problem and couldn’t fixed that unfortunately https://ingilizcepedia.com/
Hi @mahirbarut,
If you’d like to open an individual support topic we can communicate with you from there. Please include any details such as your Site Health information and the error message or screen recording of your experience. Thank you!
thank you. I contacted hosting provider to make ip v6 inactive. I will try again. İf It remains unsolved. I will contact you again
Now it worked 🙂 we inactivated ip v6 then, I deleted site kit, cached the website full, installed google site kit again. And that’s all. Now. I am asking because I don’t know what is ip v6. Should I ask my hosting provider to activate ip v6 again or not?
Glad to hear it @mahirbarut, greatly appreciate you sharing this update.
Now. I am asking because I don’t know what is ip v6. Should I ask my hosting provider to activate ip v6 again or not?
Now that your site is already set up with Site Kit, you can switch back to enabling IPv6 once more. I suspect your Site Kit dashboards will remain working as expected. IPv6 is a newer version of the IPv4 internet protocol, used to communicate between over the internet. In this case, your site needs to be able to communicate with sitekit.withgoogle.com. Connections to that address can resolve that address using IPv4 or IPv6. I can’t be sure what server configurations caused the IP v6 issue, but we did check and the blocks are not on the Google side.
I confirm that temporarily disabling IPv6 on a webdock.io server did fix the issue. In case someone is looking for instructions how to temporarily disable IPv6 on Ubuntu, I am sharing this post that worked for me: https://itsfoss.com/disable-ipv6-ubuntu-linux/
Many thanks for the update @ingereck, and also for kindly sharing the useful resource you used. As it’s not ideal to keep IPv6 disabled you can also try to activate once more now that you’re already connected. I say this as there is an update to the issue you reported, with more details added below:
https://github.com/google/site-kit-wp/issues/6095#issuecomment-1429580930
@jamesosborne
Thanks for sharing the Github Link. IPv6 are back in place (just had to restart the server). So far, I am not seeing any issues.
Excellent, let’s hope it stays like that! Thanks for the update, and best of luck with your site.
