Studio99

Thank you so much @jamesosborne for your prompt replies.

Actually I did not think about forcing IPV4 on connections to sitekit.withgoogle.com.

I’ll try this one, anyway if you have any kind of developments on this matter please keep me posted.

Hope you’ll have a great day.

Good morning @jamesosborne ,
I launched the 2 commands you suggested, and it happened as you described.

So when I launched the command with -6 I got error 403 and when I launched the Curl with -4 I got status 200.

Now I have a small issue, because I cannot permanently disable the IPV6 on that machine.

I investigated a little bit and found 2 solutions:

• I can temporarely disable IPV6, configure Site Kit (hoping that after the configuration Site Kit won’t have to use Curl call anymore) and then re-enable IPV6. In this case I would have to do the same procedure for every new website I’ll install on that machine (kinda frustrating).
• If your plugin user php-curl command you could add the following code to set the the preferred IP protocol on each curl call (also adding a dropdown option in the configuration page)

if (defined('CURLOPT_IPRESOLVE') && defined('CURL_IPRESOLVE_V4')){
   curl_setopt($ch, CURLOPT_IPRESOLVE, CURL_IPRESOLVE_V4);
}

Please let me know what you think.

I think I found the issue but I don’t know how to fix.

The database is 900MB (that’s weird because it’s a year old web site and did not generated such amount of text). Infact the posts and postmeta tables are only 20 MB.
The options table is 850 MB. What could this table happen? Is there a way to reduce it to its normal size?

I allocated 128M and also tried with 256M but nothing changes…