URL error 7: Failed to connect to sitekit.withgoogle.com port 443:

Thanks for reaching out @apoorvsam007,

So we can determine more on this and ensure you can use Site Kit as expected please share the following:

1. Your Site Health information. You can use this form to share privately if preferred.
2. At what stage does this occur on your site? For example does this appear directly after clicking on Sign in with Google during the initial set up process?
3. Do you see any warnings or errors when checking your Site Health status (Tools > Site Health > Status), which differs from your Site Health information requested above? Such errors may include REST endpoint references.

Let me know if you have any questions with the above.

Suggestion for @apoorvsam007:
If you can open ssh console, test your connection using this command:
curl -I https://sitekit.withgoogle.com
if you will get 403 error, you should contact your host provider

@jamesosborne
As I read on Github, that problem some time ago was on Frankfurt server location.
Today I found that in server location in Prague there is the same problem (4 servers checked).
Seems that some IPs blocks were banned on google side.
Any ideas?

• This reply was modified 1 year, 11 months ago by ontario777.

In my case the problem was that requests via ipv6 returns 403, but ipv4 works fine.
Finally I turned off vpv6 on my VPS hosting and now its runs good.

@ontario777 Thanks for the contribution. We found the same results in tests last week, with IP v6 checks resulting in 403 errors from a specific hosting provider. We were not, however, able to reproduce consistent results from another hosting provider who reported the same.

May I ask your hosting provider and your Site Health information, which you can share using this form?

@apoorvsam007 If you’re still encountering the same please share the information requested above, or ask if you have any questions.

@jamesosborn Im too lazy to fill in forms. This 403 found by curl execution (not depending by site but by ipv6) in friendhosting.net provider but _only_ on VPS in location Prague. Also found on o2 (internet provider, not hosting) in 2 locations in Prague.

Thanks for the insights @ontario777. When discussing with the team I’ll refer them to your comments. Thank you.

You are welcome.
BTW, in case that your sever reply code is not 200 or 301, but 40x or 50x it’s for sure not user’s problem.
My suggestion is keep one proxy server for the project, and in case of 403 try to reach via proxy. If it works, that its problem of the hosting or IP is banned. So users will not loose 3-4 h as I did yesterday to find that the problem is on the google edge…

@apoorvsam007 I’m just following up with you here to check whether the error you’re encountering persists? If so, please share the information requested and we can investigate further. We’re already looking into other reports from others so these insights may be useful to determine more.

As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist.