google_api_connection_fail

Hi @grahambayne,

Thanks for getting in touch. So we can determine more on this, please share the following:

1. Your?Site Health information. You can?use this form?to share privately if preferred.?If using the form please be sure to include your current hosting provider. Note that although you’re Site Health may say everything is food, based on your comments, we require your full Site Health information which contains useful information on possible issues with your WordPress REST API.
2. 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.
3. To rule out any local software impacting setup, can you confirm that you have no problems setting up Site Kit on this disposable WordPress site?

While you’re sharing the above I’ll also see if I can perform a check from the same hosting platform. Let me know if you have any questions with the above.

Hi @grahambayne,

I’m just checking in to see if the same issue remains? If so, please share the information requested above and we can investigate this further.

Sorry for the delay, first vacation and then just very busy. Below you will see the pasted info and also a copy of the Site Health status page. The throwaway site let me set everything up OK and connect although after 10 minutes I still did not see any data.

Thank you for your help, this is low priority as I can check this information directly on the google services, it would just be nice to get this working again,

Graham

wp-core

version: 6.1.1
site_language: en_US
user_language: en_US
timezone: Europe/Rome
permalink: /%postname%/
https_status: true
multisite: false
user_registration: 0
blog_public: 1
default_comment_status: undefined
environment_type: production
user_count: 5
dotorg_communication: true

wp-paths-sizes

wordpress_path: /home/pugliapools/public_html
wordpress_size: 8.25 GB (8858521524 bytes)
uploads_path: /home/pugliapools/public_html/wp-content/uploads
uploads_size: 821.27 MB (861162418 bytes)
themes_path: /home/pugliapools/public_html/wp-content/themes
themes_size: 67.32 MB (70592656 bytes)
plugins_path: /home/pugliapools/public_html/wp-content/plugins
plugins_size: 152.19 MB (159582622 bytes)
database_size: 18.83 MB (19743239 bytes)
total_size: 9.28 GB (9969602459 bytes)

wp-dropins (2)

advanced-cache.php: true
maintenance.php: true

wp-active-theme

name: Enfold Child (enfold-child)
version: 1.0
author: Kriesi
author_website: https://www.kriesi.at
parent_theme: Enfold (enfold)
theme_features: core-block-patterns, block-templates, avia_exclude_bbPress, deactivate_tribe_events_calendar, avia_exclude_GFForms, avia_exclude_menu_exchange, avia_exclude_pojo_accessibility, avia_exclude_wp_accessibility, avia_exclude_relevanssi, avia_exclude_WooCommerce, avia_exclude_instagram_feed, avia_exclude_leaflet_map, avia_mega_menu, avia_improved_backend_style, avia_option_pages_toggles, avia_sidebar_manager, automatic-feed-links, nav_menus, menus, widgets, post-formats, avia_post_meta_compat, force-post-thumbnails-in-widget, post-thumbnails, widgets-block-editor, title-tag, editor-styles, editor-style, customize-selective-refresh-widgets, responsive-embeds, editor-color-palette, editor-font-sizes, avia_no_session_support
theme_path: /home/pugliapools/public_html/wp-content/themes/enfold-child
auto_update: Enabled

wp-parent-theme

name: Enfold (enfold)
version: 5.3.1.1
author: Kriesi
author_website: https://kriesi.at
theme_path: /home/pugliapools/public_html/wp-content/themes/enfold
auto_update: Enabled

wp-themes-inactive (1)

Twenty Twenty-Three: version: 1.0, author: the WordPress team, Auto-updates enabled

wp-plugins-active (13)

Advanced Custom Fields: version: 6.0.7, author: WP Engine, Auto-updates enabled
Duplicate Page: version: 4.5, author: mndpsingh287, Auto-updates enabled
Envato Market: version: 2.0.8, author: Envato, Auto-updates enabled
Imagify: version: 2.1, author: Imagify – Optimize Images & Convert WebP, Auto-updates enabled
Site Kit by Google: version: 1.92.0, author: Google, Auto-updates enabled
UpdraftPlus - Backup/Restore: version: 2.22.25.26, author: UpdraftPlus.Com, DavidAnderson, Auto-updates enabled
WPML Media: version: 2.7.1, author: OnTheGoSystems, Auto-updates enabled
WPML Multilingual CMS: version: 4.5.14, author: OnTheGoSystems, Auto-updates enabled
WPML SEO: version: 2.1.0, author: OnTheGoSystems, Auto-updates enabled
WPML String Translation: version: 3.2.3, author: OnTheGoSystems, Auto-updates enabled
WP Rocket: version: 3.12.4, author: WP Media, Auto-updates disabled
Yoast SEO: version: 19.14, author: Team Yoast, Auto-updates enabled
Yoast SEO Premium: version: 19.7, author: Team Yoast, Auto-updates enabled

wp-media

image_editor: WP_Image_Editor_Imagick
imagick_module_version: 1690
imagemagick_version: ImageMagick 6.9.10-68 Q16 x86_64 2021-10-14 https://imagemagick.org
imagick_version: 3.7.0
file_uploads: File uploads is turned off
post_max_size: 128M
upload_max_filesize: 128M
max_effective_size: 128 MB
max_file_uploads: 20
imagick_limits:
imagick::RESOURCETYPE_AREA: 4 GB
imagick::RESOURCETYPE_DISK: 9.2233720368548E+18
imagick::RESOURCETYPE_FILE: 12288
imagick::RESOURCETYPE_MAP: 4 GB
imagick::RESOURCETYPE_MEMORY: 2 GB
imagick::RESOURCETYPE_THREAD: 1
imagemagick_file_formats: 3FR, 3G2, 3GP, AAI, AI, ART, ARW, AVI, AVS, BGR, BGRA, BGRO, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS, CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CRW, CUR, CUT, DATA, DCM, DCR, DCX, DDS, DFONT, DNG, DOT, DPX, DXT1, DXT5, EPDF, EPI, EPS, EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, EXR, FAX, FILE, FITS, FRACTAL, FTP, FTS, G3, G4, GIF, GIF87, GRADIENT, GRAY, GRAYA, GROUP4, GV, H, HALD, HDR, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICO, ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, J2C, J2K, JNG, JNX, JP2, JPC, JPE, JPEG, JPG, JPM, JPS, JPT, JSON, K25, KDC, LABEL, M2V, M4V, MAC, MAGICK, MAP, MASK, MAT, MATTE, MEF, MIFF, MKV, MNG, MONO, MOV, MP4, MPC, MPEG, MPG, MRW, MSL, MSVG, MTV, MVG, NEF, NRW, NULL, ORF, OTB, OTF, PAL, PALM, PAM, PANGO, PATTERN, PBM, PCD, PCDS, PCL, PCT, PCX, PDB, PDF, PDFA, PEF, PES, PFA, PFB, PFM, PGM, PGX, PICON, PICT, PIX, PJPEG, PLASMA, PNG, PNG00, PNG24, PNG32, PNG48, PNG64, PNG8, PNM, PPM, PREVIEW, PS, PS2, PS3, PSB, PSD, PTIF, PWP, RADIAL-GRADIENT, RAF, RAS, RAW, RGB, RGBA, RGBO, RGF, RLA, RLE, RMF, RW2, SCR, SCT, SFW, SGI, SHTML, SIX, SIXEL, SPARSE-COLOR, SR2, SRF, STEGANO, SUN, SVG, SVGZ, TEXT, TGA, THUMBNAIL, TIFF, TIFF64, TILE, TIM, TTC, TTF, TXT, UBRL, UBRL6, UIL, UYVY, VDA, VICAR, VID, VIFF, VIPS, VST, WBMP, WMF, WMV, WMZ, WPG, X, X3F, XBM, XC, XCF, XPM, XPS, XV, XWD, YCbCr, YCbCrA, YUV
gd_version: bundled (2.1.0 compatible)
gd_formats: GIF, JPEG, PNG, WebP, BMP, XPM
ghostscript_version: 9.25

wp-server

server_architecture: Linux 3.10.0-1127.19.1.el7.centos.plus.x86_64 x86_64
httpd_software: Apache
php_version: 8.1.14 64bit
php_sapi: cgi-fcgi
max_input_variables: 5000
time_limit: 180
memory_limit: 256M
max_input_time: 60
upload_max_filesize: 128M
php_post_max_size: 128M
curl_version: 7.87.0 OpenSSL/1.1.1s
suhosin: false
imagick_availability: true
pretty_permalinks: true
htaccess_extra_rules: true

wp-database

extension: mysqli
server_version: 5.7.41
client_version: mysqlnd 8.1.14
max_allowed_packet: 268435456
max_connections: 151

wp-constants

WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: /home/pugliapools/public_html/wp-content
WP_PLUGIN_DIR: /home/pugliapools/public_html/wp-content/plugins
WP_MEMORY_LIMIT: 128M
WP_MAX_MEMORY_LIMIT: 256M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: true
CONCATENATE_SCRIPTS: false
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_ENVIRONMENT_TYPE: Undefined
DB_CHARSET: utf8
DB_COLLATE: undefined

wp-filesystem

wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable
mu-plugins: writable

google-site-kit

version: 1.92.0
php_version: 8.1.14
wp_version: 6.1.1
reference_url: https://pugliapools.com
amp_mode: no
site_status: not-connected
user_status: not authenticated
verification_status: not-verified
connected_user_count: none
active_modules: site-verification, search-console, analytics, analytics-4, pagespeed-insights
recoverable_modules: none
required_scopes:
openid: ?</img>
https://www.googleapis.com/auth/userinfo.profile: ?</img>
https://www.googleapis.com/auth/userinfo.email: ?</img>
https://www.googleapis.com/auth/siteverification: ?</img>
https://www.googleapis.com/auth/webmasters: ?</img>
https://www.googleapis.com/auth/analytics.readonly: ?</img>
capabilities:
googlesitekit_authenticate: ?</img>
googlesitekit_setup: ?</img>
googlesitekit_view_posts_insights: ?</img>
googlesitekit_view_dashboard: ?</img>
googlesitekit_manage_options: ?</img>
googlesitekit_view_splash: ?</img>
googlesitekit_view_authenticated_dashboard: ?</img>
googlesitekit_view_wp_dashboard_widget: ?</img>
googlesitekit_view_admin_bar_menu: ?</img>
enabled_features:
adsenseSetupV2: ?</img>
dashboardSharing: ?</img>
ga4ActivationBanner: ?</img>
ga4Reporting: ?</img>
gm3Components: ?</img>
gteSupport: ?</img>
userInput: ?</img>
search_console_property: none
analytics_account_id: none
analytics_property_id: none
analytics_profile_id: none
analytics_use_snippet: yes
analytics_4_property_id: none
analytics_4_web_data_stream_id: none
analytics_4_measurement_id: none
analytics_4_use_snippet: yes

No problem with the delay. I hope you’re nice and refreshed!

Great to hear that there was no problem with the disposable WordPress site. This rules out local or network level issues. It’s also normal that you won’t see data yet, as it’s a new site without Search Console or Analytics data. From reviewing the Site Health information you kindly shared I don’t see anything obvious that would be causing this error. The next steps are to check with your hosting provider, with the block you’re encountering resulting from your site not being able to communicate with sitekti.withgoogle.com.

Can you share your current hosting provider, and whether you’re on a shared hosting plan? I ask as if you have access to make some terminal commands I can provide some to confirm any issues, performing a cURL or ping check to the Site Kit service.

Hi there, my hosting provider is UK2.net and this site is on a VPS so we have terminal access to the server. Let me know what you need me to do and I can do that for you.

Thank you again for your help

Thanks for the update @grahambayne. In that case you can perform the below:
curl -6 -I https://sitekit.withgoogle.com
I suspect this check, which ensures IPv6 is used, will result in the same 403 error.

curl -4 -I https://sitekit.withgoogle.com
This check may allow you to connect, with a successful 200 error.

If the above is true, this indicates your host server is unable to communicate if the Site Kit server (sitekit.withgoogle.com) resolves via IPv6.

If you can share with me your server IPv6 address I can also I can gather some insights into your case along with other impacted users. I also couldn’t find any AAAA records for your domain name. While I don’t suspect AAAA records to be impacting set up, it might be useful to check with your hosting provider.

Here are the results of the tests you asked for.

[root@vps ~]# curl -6 -I https://sitekit.withgoogle.com
HTTP/1.1 403 Forbidden
Transfer-Encoding: chunked
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″

[root@vps ~]# curl -4 -I https://sitekit.withgoogle.com
HTTP/1.1 200 OK
Content-Type: text/html
Vary: Accept-Encoding
X-Cloud-Trace-Context: 03fa40bd6d601b34c616062b14369842
Date: Tue, 31 Jan 2023 18:43:46 GMT
Server: Google Frontend
Transfer-Encoding: chunked
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″

[root@vps ~]# ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:16:3e:d2:05:61 brd ff:ff:ff:ff:ff:ff
inet 82.163.73.75/24 brd 82.163.73.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 2a02:2498:e006:5:216:3eff:fed2:561/64 scope global mngtmpaddr dynamic
valid_lft 2591992sec preferred_lft 604792sec
inet6 fe80::216:3eff:fed2:561/64 scope link
valid_lft forever preferred_lft forever
3: eth1: mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:16:3e:aa:b1:0d brd ff:ff:ff:ff:ff:ff

I checked a few sites on the same server and I found that Site Kit fails on all of them, I have also just noticed that GA is currently not collecting data from the site on this VPS, thank you again for all your support.

@grahambayne Thank you for sharing this. We are in the process of reaching out to other hosts to work together to reach a solution on this. As soon as I have more information I will let you know.

@grahambayne Having reached out to your hosting provider UK2 about this issue their response states that this will be due to them not supporting IPv6 on their Shared Servers.

They also asked us to pass on to you that if you could reach out to them, they could explore this further if you share the same information you have here.

Thank you for your continued support, when I reached out to UK I got a different answer. On my other VPS with them there is no problem at all, it is just this one that is causing me problems. Below is the answer from them.

I am not sure if I mentioned that Site Kit used to be working fine all this server’s WP sites up until a few weeks ago.

Hello,

Thank you for waiting. So far I haven't found anything to suggest that IPv6 is failing in any way on the server. Connecting to google.com over IPv6 for example works perfectly:
[23:16:16 vps root@94526741 ~]cPs# curl -6 -LI google.com
HTTP/1.1 301 Moved Permanently
Location: https://www.google.com/
Content-Type: text/html; charset=UTF-8
Date: Tue, 31 Jan 2023 22:16:28 GMT
Expires: Thu, 02 Mar 2023 22:16:28 GMT
Cache-Control: public, max-age=2592000
Server: gws
Content-Length: 219
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN

HTTP/1.1 200 OK
Content-Type: text/html; charset=ISO-8859-1
P3P: CP="This is not a P3P policy! See g.co/p3phelp for more info."
Date: Tue, 31 Jan 2023 22:16:28 GMT
Server: gws
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Transfer-Encoding: chunked
Expires: Tue, 31 Jan 2023 22:16:28 GMT
Cache-Control: private
Set-Cookie: 1P_JAR=2023-01-31-22; expires=Thu, 02-Mar-2023 22:16:28 GMT; path=/; domain=.google.com; Secure
Set-Cookie: AEC=ARSKqsKcfc8yTA3zPQCrCJ7H_lUfBkZyrMiWhjMF7Yg5jVdo7Mkp0gAHmg; expires=Sun, 30-Jul-2023 22:16:28 GMT; path=/; domain=.google.com; Secure; HttpOnly; SameSite=lax
Set-Cookie: NID=511=C1uDjPkjzVMfQ8I1kmJtw4qBOaabvK_0LSecmEE_VJi4yepdCLY2qhZEXS3GctaRnJlfbag8EMRlJ3iYd-OWj-QsVnnybilmhmp1nLuQWyfE2aitV_kE1dkZSttGjUW2QH-X1fqaDHM7AAiI0GaTO7hmBtf-ztZphBoVQUFPxVs; expires=Wed, 02-Aug-2023 22:16:28 GMT; path=/; domain=.google.com; HttpOnly

The only problem is that the sitekit site provides a 403 error:
[23:15:50 vps root@94526741 ~]cPs# curl -6 -LI https://sitekit.withgoogle.com
HTTP/1.1 403 Forbidden
Transfer-Encoding: chunked
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"

This access issue is a result of the policy on the remote server. They would either need to update the remote server to stop blocking your access, or they would need to tell you what you need to change in order to meet their policy requirements. I don't see anything so far to suggest that IPv6 related problems are causing this issue.

Thanks for sharing these updates @grahambayne. Regarding the same not happening on other UK2 servers this is likely to them either being on a different IPv6 address range, or possibly connections to sitekit.withgoogle.com resolving over IPv4 and not IPv6.

My colleague is communicating with UK2 on this, and has passed on information regarding this. If you’re comfortable adding a rule to ensure that any communication with sitekit.withgoogle.com is done over IPv4 this will allow you to proceed.

We’ll keep you posted here with any updates on this.

Hello James, thank you for the ongoing help. I would be happy to add a rule to force connection by IPv4 would you be able to help me with how to do that or should I speak to UK2 about helping me to do that?

Hi @grahambayne. You would be best to speak with your host on this. Depending on your hosting account any such rule changes may involve edits to your hosts file or restarting the server.

Hello, the support guys at UK2 just disabled IPv6 on the server for me and now all is working as it used to be. Without the help from people like you and them I would never be able to host a website. Thank you very much for your support : )

@grahambayne Glad to hear this and you are very welcome, it’s been a pleasure helping you out. Good luck with your site.