Error connecting

  • Resolved hostaan

    (@hostaan)


    2 years, 4 months ago

    Hi,

    Our customers have experienced problems connecting Site Kit this week. The “Set up Site Kit” page shows the following error:

    “Your site may not be ready for Site Kit
    Looks like your site is having a technical issue with requesting data from Google services.
    To get more help, ask a question on our support forum and include the text of the original error message:
    google_api_connection_fail”

    and after clicking “Sign in with Google”:

    “The request to the authentication proxy has failed with an error: request_failed”

    From the github issue page https://github.com/google/site-kit-wp/issues/1262 I found the suggestion to try calling the endpoint with curl:

    # curl -I https://sitekit.withgoogle.com
    HTTP/2 403
    alt-svc: h3=”:443″; ma=2592000,h3-29=”:443″; ma=2592000,h3-Q050=”:443″; ma=2592000,h3-Q046=”:443″; ma=2592000,h3-Q043=”:443″; ma=2592000,quic=”:443″; ma=2592000; v=”46,43″

    We a bunch of web servers in two different locations, and this issue occurs on seemingly all VPSs in one location, but on none in the other location.

    The other location resolves sitekit.withgoogle.com to different IP-addresses than the other, but if I force to lookups on the problematic server to resolve to the IP that the working hosts resolve to I get the same 403 reponse.

    Is this due to a geoblock or some such (even though the locations are geograhically near each other), and how would be go about fixing it?

    I have the details of DNS queries and IP addresses, but I won’t include them here at this time.

    The page I need help with: [log in to see the link]

Viewing 7 replies - 16 through 22 (of 22 total)
  • Thread Starter hostaan

    (@hostaan)

    Hi,

    I’m just checking in on this for an update: the issue still seems to persist, has there been any progress on your end?

    Plugin Support James Osborne

    (@jamesosborne)

    Hi @hostaan,

    We are still awaiting a check on this. Unfortunately I don’t have an update at this time, but as soon as I do, I’ll let you know. I can’t give you a timeframe unfortunately, as it’s not the support team who can perform further tests on this, but I certainly will let you know as soon as I have an update. Happy new year!

    Plugin Support James Osborne

    (@jamesosborne)

    Hi @hostaan,

    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.

    Can you temporarily disable IPv6 address usage before attempting Site Kit set up once more? Here’s one guide that may be useful in order to do so. 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.

    Thread Starter hostaan

    (@hostaan)

    Hi,

    On 2023-01-18 we noticed the IPv6 connections to SiteKit from Upcloud’s FI-HEL1 location succeeded again. Since then, the connections from there have been workin normally.

    The joy was short-lived, however, as yesterday we noticed the same block is in place on Upcloud’s HEL-2 location and thus affects the other half of our servers. The symptom is the same IPv4 connections work, IPv6 don’t:

    # curl -6 -I https://sitekit.withgoogle.com

    HTTP/2 403 alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"

    # curl -4 -I https://sitekit.withgoogle.com

    HTTP/2 200 content-type: text/htmlvary: Accept-Encodingx-cloud-trace-context: 856947cb8ecc7497f37698d158da9154date: Thu, 02 Feb 2023 08:22:25 GMTserver: Google Frontendalt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"

    I have no idea how the situation got resolved last time. Upcloud said they couldn’t even get a hold of anyone from the Google, and as far as I can tell no configuration changes were made. Prefering IPv4 over IPv6 is something we can do as a work-around, but that of course is not the solution.

    I wonder if there is something that was done on your end the fix this last time, and can something be done now for the HEL-2 IP-addresses.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @hostaan Thank you for the detailed update here. We are currently in the process of reaching out to hosting providers to get this resolved. Once we have an update on the matter we will drop it here for you. Thanks for your patience.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @hostaan We have been seeing some IPs that were previously blocked becoming unblocked over the last few days. Could you please check and confirm if you are still seeing the same message when attempting Site Kit setup or has this been resolved?

    Thread Starter hostaan

    (@hostaan)

    Hi,

    Sorry for my delayed response.

    I can confirm that block has disappeared, and connections to https://sitekit.withgoogle.com/ work with IPv6 just as they should.

    Thank you for your efforts!

Viewing 7 replies - 16 through 22 (of 22 total)
  • The topic ‘Error connecting’ is closed to new replies.