• Resolved nikolas07

    (@nikolas07)


    Today I migrated my website to OVH, when I finished the migration and configured the plugins, notice that the Google Site KIT shows the error google_api_connection_fail

    How can I solve?

    Hoje fiz a migra??o do meu site para a OVH, ao finalizar toda a migra??o e configurar os plugins notei que o Google Site KIT apresenta o erro google_api_connection_fail

    Como posso resolver?

    ` wp-core
    
    version: 6.3.2
    site_language: pt_BR
    user_language: pt_BR
    timezone: America/Sao_Paulo
    permalink: /%postname%/
    https_status: true
    multisite: false
    user_registration: 0
    blog_public: 1
    default_comment_status: open
    environment_type: production
    user_count: 1
    dotorg_communication: true wp-paths-sizes
    
    wordpress_path: /home/jpagora/htdocs/jpagora.com
    wordpress_size: 11,43 GB (12277313007 bytes)
    uploads_path: /home/jpagora/htdocs/jpagora.com/wp-content/uploads
    uploads_size: 11,25 GB (12083619998 bytes)
    themes_path: /home/jpagora/htdocs/jpagora.com/wp-content/themes
    themes_size: 5,46 MB (5728549 bytes)
    plugins_path: /home/jpagora/htdocs/jpagora.com/wp-content/plugins
    plugins_size: 199,63 MB (209324917 bytes)
    database_size: 222,03 MB (232816640 bytes)
    total_size: 23,10 GB (24808803111 bytes) wp-dropins (1)
    
    advanced-cache.php: true wp-active-theme
    
    name: Newspaper (Newspaper)
    version: 12.5.1 (latest version: 12.6.1)
    author: tagDiv
    author_website: https://themeforest.net/user/tagDiv/portfolio
    parent_theme: none
    theme_features: core-block-patterns, post-formats, post-thumbnails, automatic-feed-links, html5, woocommerce, bbpress, align-wide, align-full, editor-font-sizes, widgets-block-editor, editor-style, menus, widgets
    theme_path: /home/jpagora/htdocs/jpagora.com/wp-content/themes/Newspaper
    auto_update: Desativado wp-themes-inactive (1)
    
    Twenty Twenty-Three: version: 1.2, author: a equipe do WordPress, Atualiza??es automáticas desativadas wp-plugins-active (19)
    
    Ad Inserter Pro: version: 2.7.31, author: Ad Inserter Pro, Atualiza??es automáticas desativadas
    Akismet Anti-spam: Spam Protection: version: 5.3, author: Automattic - Anti-spam Team, Atualiza??es automáticas desativadas
    CLP Varnish Cache: version: 1.0.0, author: cloudpanel.io, Atualiza??es automáticas desativadas
    GN Publisher: version: 1.5.10, author: Chris Andrews, Atualiza??es automáticas desativadas
    Health Check & Troubleshooting: version: 1.7.0, author: The www.remarpro.com community, Atualiza??es automáticas desativadas
    plugin load filter: version: 4.0.16, author: enomoto@celtislab, Atualiza??es automáticas desativadas
    SEOPress: version: 7.0.3, author: The SEO Guys at SEOPress, Atualiza??es automáticas desativadas
    SEOPress PRO: version: 7.0, author: The SEO Guys at SEOPress (latest version: 7.0.2), Atualiza??es automáticas desativadas
    Site Kit by Google: version: 1.111.0, author: Google, Atualiza??es automáticas ativadas
    Slider Revolution: version: 6.6.14, author: ThemePunch, Atualiza??es automáticas desativadas
    tagDiv Cloud Library: version: 2.8 | built on 25.07.2023 12:54, author: tagDiv, Atualiza??es automáticas desativadas
    tagDiv Composer: version: 4.3 | built on 10.08.2023 12:54, author: tagDiv, Atualiza??es automáticas desativadas
    tagDiv Mobile Theme: version: 2.3 | built on 25.07.2023 12:54, author: tagDiv, Atualiza??es automáticas desativadas
    tagDiv Standard Pack: version: 1.9 | built on 25.07.2023 12:54, author: tagDiv, Atualiza??es automáticas desativadas
    UpdraftPlus - Backup/Restore: version: 1.23.10, author: UpdraftPlus.Com, DavidAnderson, Atualiza??es automáticas desativadas
    WebP Express: version: 0.25.6, author: Bj?rn Rosell, Atualiza??es automáticas desativadas
    wpDiscuz: version: 7.6.10, author: gVectors Team, Atualiza??es automáticas desativadas
    wpDiscuz - Ads Manager: version: 7.0.7, author: gVectors Team, Atualiza??es automáticas desativadas
    WP Super Cache: version: 1.10.0, author: Automattic, Atualiza??es automáticas desativadas wp-media
    
    image_editor: WP_Image_Editor_Imagick
    imagick_module_version: 1691
    imagemagick_version: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
    imagick_version: 3.4.4
    file_uploads: File uploads is turned off
    post_max_size: 64M
    upload_max_filesize: 64M
    max_effective_size: 64 MB
    max_file_uploads: 20
    imagick_limits:
    imagick::RESOURCETYPE_AREA: 122 MB
    imagick::RESOURCETYPE_DISK: 1073741824
    imagick::RESOURCETYPE_FILE: 768
    imagick::RESOURCETYPE_MAP: 512 MB
    imagick::RESOURCETYPE_MEMORY: 256 MB
    imagick::RESOURCETYPE_THREAD: 4
    imagick::RESOURCETYPE_TIME: 9.2233720368548E+18
    imagemagick_file_formats: 3FR, 3G2, 3GP, AAI, AI, APNG, ART, ARW, AVI, AVIF, AVS, BGR, BGRA, BGRO, BIE, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS, CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CR3, CRW, CUR, CUT, DATA, DCM, DCR, DCX, DDS, DFONT, DNG, DPX, DXT1, DXT5, EPDF, EPI, EPS, EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, FAX, FILE, FITS, FRACTAL, FTP, FTS, G3, G4, GIF, GIF87, GRADIENT, GRAY, GRAYA, GROUP4, H, HALD, HDR, HEIC, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICO, ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, J2C, J2K, JBG, JBIG, 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, MPG, MRW, MSL, MTV, MVG, NEF, NRW, NULL, ORF, OTB, OTF, PAL, PALM, PAM, 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, POCKETMOD, 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, TEXT, TGA, THUMBNAIL, TIFF, TIFF64, TILE, TIM, TTC, TTF, TXT, UBRL, UBRL6, UIL, UYVY, VDA, VICAR, VID, VIDEO, VIFF, VIPS, VST, WBMP, WEBM, WEBP, WMV, WPG, X, X3F, XBM, XC, XCF, XPM, XPS, XV, XWD, YCbCr, YCbCrA, YUV
    gd_version: 2.3.0
    gd_formats: GIF, JPEG, PNG, WebP, BMP, XPM
    ghostscript_version: 9.53.3 wp-server
    
    server_architecture: Linux 5.10.0-26-cloud-amd64 x86_64
    httpd_software: nginx/1.21.4
    php_version: 7.4.33 64bit
    php_sapi: fpm-fcgi
    max_input_variables: 10000
    time_limit: 60
    memory_limit: 512M
    max_input_time: 60
    upload_max_filesize: 64M
    php_post_max_size: 64M
    curl_version: 7.74.0 OpenSSL/1.1.1w
    suhosin: false
    imagick_availability: true
    pretty_permalinks: true
    current: 2023-10-14T16:48:08+00:00
    utc-time: Saturday, 14-Oct-23 16:48:08 UTC
    server-time: 2023-10-14T13:48:08-03:00 wp-database
    
    extension: mysqli
    server_version: 10.11.5-MariaDB-1:10.11.5+maria~deb11
    client_version: mysqlnd 7.4.33
    max_allowed_packet: 67108864
    max_connections: 512 wp-constants
    
    WP_HOME: undefined
    WP_SITEURL: undefined
    WP_CONTENT_DIR: /home/jpagora/htdocs/jpagora.com/wp-content
    WP_PLUGIN_DIR: /home/jpagora/htdocs/jpagora.com/wp-content/plugins
    WP_MEMORY_LIMIT: 256M
    WP_MAX_MEMORY_LIMIT: 512M
    WP_DEBUG: false
    WP_DEBUG_DISPLAY: false
    WP_DEBUG_LOG: true
    SCRIPT_DEBUG: false
    WP_CACHE: true
    CONCATENATE_SCRIPTS: false
    COMPRESS_SCRIPTS: undefined
    COMPRESS_CSS: undefined
    WP_ENVIRONMENT_TYPE: Indefinido
    WP_DEVELOPMENT_MODE: undefined
    DB_CHARSET: utf8
    DB_COLLATE: undefined wp-filesystem
    
    wordpress: writable
    wp-content: writable
    uploads: writable
    plugins: writable
    themes: writable google-site-kit
    
    version: 1.111.0
    php_version: 7.4.33
    wp_version: 6.3.2
    reference_url: https://jpagora.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: ?
    https://www.googleapis.com/auth/userinfo.profile: ?
    https://www.googleapis.com/auth/userinfo.email: ?
    https://www.googleapis.com/auth/siteverification: ?
    https://www.googleapis.com/auth/webmasters: ?
    https://www.googleapis.com/auth/analytics.readonly: ?
    https://www.googleapis.com/auth/tagmanager.readonly: ?
    capabilities:
    googlesitekit_authenticate: ?
    googlesitekit_setup: ?
    googlesitekit_view_posts_insights: ?
    googlesitekit_view_dashboard: ?
    googlesitekit_manage_options: ?
    googlesitekit_update_plugins: ?
    googlesitekit_view_splash: ?
    googlesitekit_view_authenticated_dashboard: ?
    googlesitekit_view_wp_dashboard_widget: ?
    googlesitekit_view_admin_bar_menu: ?
    googlesitekit_view_shared_dashboard: ?
    googlesitekit_read_shared_module_data::["search-console"]: ?
    googlesitekit_read_shared_module_data::["pagespeed-insights"]: ?
    googlesitekit_manage_module_sharing_options::["search-console"]: ?
    googlesitekit_manage_module_sharing_options::["pagespeed-insights"]: ?
    googlesitekit_delegate_module_sharing_management::["search-console"]: ?
    googlesitekit_delegate_module_sharing_management::["pagespeed-insights"]: ?
    enabled_features:
    adsenseSetupV2: ?
    enhancedMeasurement: ?
    ga4Reporting: ?
    gm3Components: ?
    newsKeyMetrics: ?
    userInput: ?
    search-console_shared_roles: none
    search-console_management: owner
    pagespeed-insights_shared_roles: none
    pagespeed-insights_management: all_admins
    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
Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter nikolas07

    (@nikolas07)

    Follow the curl tests they did in the terminal

    Segue os testes de curl que fiz pelo terminal

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for reaching out @nikolas07, and for sharing the results of your check regarding communication with your site and the Site Kit service. From reviewing the details it looks like you can only access sitekit.withgoogle.com over IPv4 and not IPv6. What may be happening, based on other reports, is that your IPv6 address is within a range that contains other IP addresses from regions where Google services are blocked. This will result in the error message you’re describing, and changes must be made at host level in order to proceed.

    So we can confirm this is the case, please share the following:

    1. Have you reached out to OVH on this and asked for any particular block they may be aware of?
    2. As it looks like you may be a Cloudflare user, have you tried to temporarily pause Cloudflare before trying to set up Site Kit?
    3. Can you confirm your IPv6 address? From the AAAA records I performed this may be 2606:4700:3037::ac43:d175.

    Note also that as a workaround, you may wish to temporarily deactivate IPv6 while you’re setting up Site Kit. That way only IPv4 will be used and you should be able to proceed.

    Let me know if you have any questions with the above.

    Thread Starter nikolas07

    (@nikolas07)

    Good morning, I have already contacted OVH about this but no response so far.

    I temporarily disabled cloudflare and the problem persists, it is also unlikely that it is the problem, as my VULTR instance did not have this problem.

    Yes. The IPV6 address provided by OVH is this 2606:4700:3037::ac43:d175

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for sharing this additional information. I’ve requested a check for the IPv6 address you provided. Unfortunately blocked to Google URLs are not something I can check myself, but I will let you know as soon as I have an update, most likely later this week.

    Note also that if you are able to set up a clean WordPress install on the same IP, without Cloudflare, it might be worth attempting Site Kit setup. This can help determine if an origin host or Cloudflare block. Regardless, I will keep you informed here once I have an update on any blocks based on your sites IPv6 range.

    Plugin Support James Osborne

    (@jamesosborne)

    I have an update regarding your IPv6 address check. It looks like the 2606:4700:3037::ac43:d175 IPv6 address is not blocked at present. Can you attempt Site Kit setup once more, and if the same occurs please share if you’re able to setup another WordPress site on the same hosting platform, without Cloudflare in use. If so, please attempt Site Kit setup using this site, which will help to determine any original host related issue.

    Thread Starter nikolas07

    (@nikolas07)

    I created a cloud instance in the same region as the VPS in Canada, Beauharnois (BHS) on OVh and I was unable to activate the Site Kit, it gave the same error.

    Later using the same settings made in the same France, Gravelines (GRA) on Ovh, and I managed to activate SiteKIT. All attempts were made with CloudFlare active.

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for the update @nikolas07. For your jpagora.com site, can you confirm whether the same error appears? I ask as the check came back and it stated your IPv6 is not blocked.

    I created a cloud instance in the same region as the VPS in Canada, Beauharnois (BHS) on OVh and I was unable to activate the Site Kit, it gave the same error.

    Typically, when these IPv6 only errors occur, the issue may not be specific to your site, they can occur if another IPv6 address within the same range is from a region where Google services are blocked.

    Based on the telnet and cURL checks you previously shared you’ll also notice that the issue is the communication between your host server and a Google domain (sitekit.withgoogle.com). We may need to perform some additional checks with your hosting provider where such issues can be addressed. Can you confirm your origin host is ovhcloud.com, and have you reached out to them to enquire about any possible IPv6 issues, sharing the insights you provided?

    Plugin Support James Osborne

    (@jamesosborne)

    As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist.

    The same issue, the same VPS provider.

    2607:5300:201….

    Solution: Disabled IPv6 on VPS

    Plugin Support James Osborne

    (@jamesosborne)

    Sorry to hear that?@voleoo. If you’d like to?open an individual support topic?we can communicate with you from there and investigate further.

    As an alternative, you may also wish to download, install and activate?this mini plugin?before attempting Site Kit setup. If your problem is related to the same IPv6 issue, this mini plugin should address it. Let me know how you get on with this check, ideally from your own individual support topic.

    This mini plugin resolve issue, thanks, now all is working.
    https://buda-pets-space.com
    2607:5300:201:3100::48ab

    Plugin Support James Osborne

    (@jamesosborne)

    Glad to hear it @voleoo, appreciate the update. Best of luck, and you know where to find us should you have any further Site Kit queries.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘google_api_connection_fail’ is closed to new replies.