ochoppee

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.

Sure that is fine

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

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.

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

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

Additional Info: Primary IPv4’s

Primary IP

54.39.23.128

Assigned IPs

54.39.23.128
54.39.84.129

“One workaround is to temporarily disable IPv6 when setting up Site Kit. If you have web terminal access I can provide you with the steps to do so.”

Let me know if I need this after you check my IPv6 for a block! If so I can work with my hosting provider on this.

• This reply was modified 1 year ago by ochoppee.

Here is my hosting provider response, and I had them restart the server.

Posted by CanSpace Solutions G1 on 1st Nov 2023 (09:26)Operator

Hello Peter,

The IPV6 address assigned to your server is noted below. If you’d like a restart of the server we can take care of that for you as it is your private VPS as opposed to a shared host.

inet6 2607:5300:201:3100::82c1 prefixlen 64 scopeid 0x0<global>

-Guy H.
Support, CanSpace

So if IPv4 works and IPv6 is forbidden, what might be a solution?

Hello,

1. Your IPv6 address for the impacted sites. I suspect they are all within the same range.

Yes, I believe they are as they are hosted on a VPS, which has 2 IP’s assigned to it.

1. Are you using a shared hosting solution? If not have you tried restarting your server? I ask as I noticed some cURL errors reported in your Site Health status. With that may also wish to temporarily switch PHP version.?
   

No I have not tried restarting the server, I can ask my hosting provider to do so. Due to complex issues, switch PHP versions is not an easy task, as it may affect each site differently that is hosted on the server, I can do this as a last resort?

1. Did you have Site Kit successfully running on any of these sites before?

Yes I did on all my sites on the server, the other sites are either still connected and experiencing json error when trying to retrieve data or having issues connecting.

Re: Immunify360

I have disabled immunify360 for the site right now, and still have the issue as stated in the topic

Additional Info Curl

In regard to the response you posted, while the server does have an assigned IPV6 address it uses IPV4 for it’s main connection. The curl command defaults to IPV6 without the -4 flag they mention in the response. The output of the updated command is pasted for you below and does give a successful 200 connection code.

Your server does have a WAF in place (mod security) which can be disabled for testing (or completely) within cPanel in the security section under Mod Security. You can disable this for any specific site within the account.

[root@vps197 ~]# curl -4 -I https://sitekit.withgoogle.com
HTTP/2 200
content-type: text/html
vary: Accept-Encoding
x-cloud-trace-context: f040e5ffe9635f82a4d6deccf648c78b
date: Tue, 31 Oct 2023 18:39:15 GMT
server: Google Frontend
alt-svc: h3=”:443″; ma=2592000,h3-29=”:443″; ma=2592000

-Guy H.
Support, CanSpace

Re: Curl ipv4

[root@vps197 ~]# curl -4 -I?https://sitekit.withgoogle.com
HTTP/2 200
content-type: text/html
vary: Accept-Encoding
x-cloud-trace-context: f040e5ffe9635f82a4d6deccf648c78b
date: Tue, 31 Oct 2023 18:39:15 GMT
server: Google Frontend
alt-svc: h3=”:443″; ma=2592000,h3-29=”:443″; ma=2592000

Re: Demo Site and Web Application Firewall and curl

The Demo site works for me with my chrome browser! I might note that I use Immunify360, does this info help, and I am checking on curl