google_api_connection_fail when activating plugin

Thanks for the update @ochoppee. I’ll request a check for this IPv6 address now. Also please do go ahead and request a restart of your server, which seems to be a private VPS while I’m doing so.

Note that it may take a few days before I hear back from any potential IPv6 related block, but I’ll update you as soon as I hear back from this request.

Additional Info: Primary IPv4’s

Primary IP

54.39.23.128

Assigned IPs

54.39.23.128
54.39.84.129

@ochoppee Thanks for the additional information. We are still awaiting the check on your IPv6 address. Once we have the result we will update here.

@ochoppee?Just to let you know that we heard back from the request for your site. From doing so, it looks like your IPv6 address is indeed blocked. What I did was I reached out to your hosting provider, via the info@ email listed on the contact page of their website, with some suggestions on how to address this. You may wish to reach out to them asking whether there are any updates.

For additional context, blocks such as the one you are encountering are not any blocks at Site Kit level, they are more IPv6 only blocks to Google related URLs, based on the IP Range including IP addresses from regions where Google services are blocked.

Note also that such blocks can be temporary, however, they do fall outside the scope of what we can address here on the plugin site. I’ll keep you updated should we have any updates on this, thank you!

My hosting provider was wondering if there is a way in the plugin settings to force IPv4 was their question?

They are also wondering if the plugin has specific settings that tell it to use only IPv4?

Thanks for the update @ochoppee.

My hosting provider was wondering if there is a way in the plugin settings to force IPv4 was their question?

This is a great question, and something we have been discussing. The problem isn’t with the Site Kit service communication specifically, it’s an issue when connecting with the various Google API’s that Site Kit uses. We are still looking into this.

They are also wondering if the plugin has specific settings that tell it to use only IPv4?

There is no such setting at present, but I will keep you updated with any developments on these Google API limitations.

Note also that if you can temporarily deactivate IPv6, this may allow you to use complete setup. I also checked your site just now and I can also confirm that Site Kit has the Google Analytics snippet placed, despite the warning. This means you can view Analytics data from analytics.google.com with this Site Kit placed snippet.

Please do also let me know if you wish for me to perform another IPv6 check for your site once your hosting provider has added a Geofeed based on the instructions I provided.

Can you resend those instructions to CanSpace Solutions Tech Support [email protected]

with subject line as follows

Re: [Ticket ID: 382141] https://staging.therockiestours.ca/therockiestours.ca/ and https://therockiestours.ca/ [MERGED]

they seem to can’t find it in there info inbox no more.

No problem @ochoppee, that’s done now. I previously sent this on Tuesday, but to the info@ address. It’s forwarded now to the support@ address.

Let me know if you have any further questions on this.

Their answer!

Hello Peter,

The ticket was seen and replied to and there is a staff side note here referencing it. One of the solutions he provides has already been applied (removing your IPV6 address) and as noted in the ongoing thread you have and here in the earlier replies this resolved the issue and the Sitekit is working, per this Google representative in your VPS. None of the other suggestions would apply here.

Your VPS is not in a banned region nor are the IPs and as we do not control the IPV6 blocks directly we can not affect the published geolocation. We would not add an unsupported IPGeoFeed within the VPS itself and, as removing the address allowed the sitekit to work there would be no reason to do so.

The actual cause of the issue, as noted in the thread referenced in his email, is related to different google APIs that are not functioning as they should and are incorrectly blocking certain IPV6 ranges. That is something they need to resolve on their side.

As the sitekit is working in your service what else would you like us to assist with in this?

Support, CanSpace

@ochoppee Thank you for sharing the updates. Could I check with you once more if you are still encountering this issue as these blocks can over time clear. If you are still facing this then please note that we are now actively working on a solution for this to allow users to connect using IPv4 when IPv6 is blocked. Please feel free to follow this issue for further updates.

Sure that is fine

@ochoppee Just a check up to ask whether the issue remains on your site, or can you now connect as expected?

As we didn’t receive a response I’ll mark this as resolved @ochoppee. While we didn’t hear back from you, not that we have since created a mini plugin as a workaround for those impacted by an IPv6 block, as you were previously. The details of this can be found on this guide. Let me know if you have any further questions on this.

I believe the issue remains, but have not verified since the change by my hosting provider would need to be reversed. I will check out your mini plugin, and let you know.