Your site may not be ready for Site Kit

  • Resolved CharlieHamu

    (@charliehamu)


    3 years, 2 months ago

    When I activate Site Kit, I get the message “Your site may not be ready for Site Kit” and “Data error in Search Console” / “You are probably offline.”

    I’ve turned off mod_security, turned off all plugins, switched the theme to Twenty Twenty-One, disabled, deleted, installed, and activated on a different computer in incognito mode.

    Could it be because these two don’t match?
    WordPress Address (URL): https://danforthgreens.ca/wordpress
    Site Address (URL): https://danforthgreens.ca

    Or because the Site Address doesn’t have a trailing slash?
    Or because when I first registered the property with Google Analytics it would have been http, not https? (But it shows as https in the Search Console now.)

    Here is my Site Health info:

    `
    ### wp-core ###

    version: 5.8
    site_language: en_US
    user_language: en_US
    timezone: America/Toronto
    permalink: /%postname%/
    https_status: true
    multisite: false
    user_registration: 0
    blog_public: 1
    default_comment_status: open
    environment_type: production
    user_count: 39
    dotorg_communication: true

    ### wp-paths-sizes ###

    wordpress_path: /home/charliehamu/danforthgreens.ca/wordpress
    wordpress_size: loading…
    uploads_path: /home/charliehamu/danforthgreens.ca/wordpress/wp-content/uploads
    uploads_size: loading…
    themes_path: /home/charliehamu/danforthgreens.ca/wordpress/wp-content/themes
    themes_size: loading…
    plugins_path: /home/charliehamu/danforthgreens.ca/wordpress/wp-content/plugins
    plugins_size: loading…
    database_size: loading…
    total_size: loading…

    ### wp-active-theme ###

    name: Twenty Twenty-One (twentytwentyone)
    version: 1.4
    author: the WordPress team
    author_website: https://www.ads-software.com/
    parent_theme: none
    theme_features: core-block-patterns, widgets-block-editor, automatic-feed-links, title-tag, post-formats, post-thumbnails, menus, html5, custom-logo, customize-selective-refresh-widgets, wp-block-styles, align-wide, editor-styles, editor-style, editor-font-sizes, custom-background, editor-color-palette, editor-gradient-presets, responsive-embeds, custom-line-height, experimental-link-color, custom-spacing, custom-units, widgets
    theme_path: /home/charliehamu/danforthgreens.ca/wordpress/wp-content/themes/twentytwentyone
    auto_update: Disabled

    ### wp-themes-inactive (3) ###

    Adriana: version: 1.0, author: Charlie Halpern-Hamu, Auto-updates disabled
    Astra: version: 3.6.9, author: Brainstorm Force, Auto-updates disabled
    Danforth: version: 1.0, author: Charlie Halpern-Hamu, Auto-updates disabled

    ### wp-plugins-active (1) ###

    Site Kit by Google: version: 1.40.0, author: Google, Auto-updates disabled

    ### wp-plugins-inactive (20) ###

    Adriana Widgets: version: 1, author: Charlie Halpern-Hamu, Auto-updates disabled
    Akismet Anti-Spam: version: 4.1.12, author: Automattic, Auto-updates disabled
    Broken Link Checker: version: 1.11.15, author: WPMU DEV, Auto-updates disabled
    Cache Feed for a Long Time: version: 0.1, author: Charlie Halpern-Hamu, Auto-updates disabled
    Classic Editor: version: 1.6.2, author: WordPress Contributors, Auto-updates disabled
    Classic Widgets: version: 0.2, author: WordPress Contributors, Auto-updates disabled
    Contact Form 7: version: 5.4.2, author: Takayuki Miyoshi, Auto-updates disabled
    Excerpt Editor: version: 1.4, author: Andrew Ozz, Auto-updates disabled
    Google XML Sitemaps: version: 4.1.1, author: Auctollo, Auto-updates disabled
    Jetpack: version: 10.0, author: Automattic, Auto-updates disabled
    Post-Plugin Library: version: 2.6.2.1, author: Rob Marsh, SJ, Auto-updates disabled
    Really Simple Sitemap cdhh: version: 1.2, author: Dominic Foster, Auto-updates disabled
    Recent Comments: version: 2.1, author: Automattic, Auto-updates disabled
    RS Event: version: 0.9.7, author: Robert Sargant, Auto-updates disabled
    Save to Internet Archive: version: 0.1, author: Charlie Halpern-Hamu, Auto-updates disabled
    TaxoPress: version: 3.2.2, author: TaxoPress, Auto-updates disabled
    Trim non-breaking spaces: version: 0.1, author: Charlie Halpern-Hamu, Auto-updates disabled
    WP-DBManager: version: 2.80.3, author: Lester ‘GaMerZ’ Chan, Auto-updates disabled
    WP Super Cache: version: 1.7.4, author: Automattic, Auto-updates disabled
    Yet Another Related Posts Plugin (YARPP): version: 5.27.4, author: YARPP, Auto-updates disabled

    ### wp-media ###

    image_editor: WP_Image_Editor_Imagick
    imagick_module_version: 1687
    imagemagick_version: ImageMagick 6.9.7-4 Q16 x86_64 20170114 https://www.imagemagick.org
    imagick_version: 3.5.0
    file_uploads: File uploads is turned off
    post_max_size: 650M
    upload_max_filesize: 600M
    max_effective_size: 600 MB
    max_file_uploads: 20
    imagick_limits:
    imagick::RESOURCETYPE_AREA: 62 GB
    imagick::RESOURCETYPE_DISK: 1.844674407371E+19
    imagick::RESOURCETYPE_FILE: 6144
    imagick::RESOURCETYPE_MAP: 62 GB
    imagick::RESOURCETYPE_MEMORY: 31 GB
    imagick::RESOURCETYPE_THREAD: 1
    imagemagick_file_formats: 3FR, AAI, AI, ART, ARW, AVI, AVS, BGR, BGRA, BGRO, BIE, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS, CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CRW, CUR, CUT, DATA, DCM, DCR, DCX, DDS, DFONT, DJVU, 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, GROUP4, GV, H, HALD, HDR, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICO, ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, JBG, JBIG, JNG, JNX, JPE, JPEG, JPG, JPS, 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, 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.26

    ### wp-server ###

    server_architecture: Linux 4.14.117-grsec-grsec+ x86_64
    httpd_software: Apache
    php_version: 7.4.20 64bit
    php_sapi: cgi-fcgi
    max_input_variables: 1000
    time_limit: 500
    memory_limit: 500M
    max_input_time: 500
    upload_max_filesize: 600M
    php_post_max_size: 650M
    curl_version: 7.58.0 OpenSSL/1.1.1
    suhosin: false
    imagick_availability: true
    pretty_permalinks: true

    ### wp-database ###

    extension: mysqli
    server_version: 5.7.28-log
    client_version: mysqlnd 7.4.20

    ### wp-constants ###

    WP_HOME: undefined
    WP_SITEURL: undefined
    WP_CONTENT_DIR: /home/charliehamu/danforthgreens.ca/wordpress/wp-content
    WP_PLUGIN_DIR: /home/charliehamu/danforthgreens.ca/wordpress/wp-content/plugins
    WP_MEMORY_LIMIT: 128M
    WP_MAX_MEMORY_LIMIT: 500M
    WP_DEBUG: false
    WP_DEBUG_DISPLAY: true
    WP_DEBUG_LOG: false
    SCRIPT_DEBUG: false
    WP_CACHE: false
    CONCATENATE_SCRIPTS: undefined
    COMPRESS_SCRIPTS: undefined
    COMPRESS_CSS: undefined
    WP_LOCAL_DEV: undefined
    DB_CHARSET: undefined
    DB_COLLATE: undefined

    ### wp-filesystem ###

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

    ### google-site-kit ###

    version: 1.40.0
    php_version: 7.4.20
    wp_version: 5.8
    reference_url: https://danforthgreens.ca
    amp_mode: no
    site_status: connected-site
    user_status: authenticated
    verification_status: verified-file
    connected_user_count: 1
    active_modules: site-verification, search-console
    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: ?
    capabilities:
    googlesitekit_authenticate: ?
    googlesitekit_setup: ?
    googlesitekit_view_posts_insights: ?
    googlesitekit_view_dashboard: ?
    googlesitekit_view_module_details: ?
    googlesitekit_manage_options: ?
    enabled_features:
    ga4setup: ?
    ideaHubModule: ?
    serviceSetupV2: ?
    userFeedback: ?
    userInput: ?
    search_console_property: https://danforthgreens.ca/

    The page I need help with: [log in to see the link]

Viewing 8 replies - 31 through 38 (of 38 total)
  • Thread Starter CharlieHamu

    (@charliehamu)

    Your direction to keep examining how http -> https redirects were handled differently between the site that works and the site that doesn’t work led me to realize that my .htaccess file had a great many redirects back to http for individual pages and sets of pages, even though there was an initial redirect to https.

    Some of the redirects were sufficiently general that they could have messed up the Site Kit plug-in’s ability to reference its own files securely, which seemed to be what the console errors were saying. And that explanation would also possibly make sense of why it worked when my Site URL matched my WordPress URL: it might have been provoking fewer of these redirects.

    So I fixed all of that and progressed to a new error:

    Your site may not be ready for Site Kit
    Looks like you may be using a caching plugin which could interfere with setup. Please deactivate any caching plugins before setting up Site Kit. You may reactivate them once setup has been completed.

    I have my cache off and emptied, but I haven’t tried incognito or troubleshooting mode yet. This, by the way, is why I’m not really thinking it’s the Contact Form 7 plug-in, because that would be disabled in troubleshooting mode anyway. But I will investigate it and fix any http that’s still there.

    Anyway, I still have several things to try, including reverting to a minimal .htaccess file. (Even the http -> https redirection is handled DreamHost, in some higher-level .htaccess file or reasonable facsimile, so I don’t need that redirection in my handcrafted file. It’s not in the .htaccess file for the WordPress site that works with Site Kit.)

    I post again in a day or two as soon as I either resolve the situation or hit the next impasse.

    • This reply was modified 3 years, 2 months ago by CharlieHamu.
    • This reply was modified 3 years, 2 months ago by CharlieHamu.
    • This reply was modified 3 years, 2 months ago by CharlieHamu.
    • This reply was modified 3 years, 2 months ago by CharlieHamu.
    Thread Starter CharlieHamu

    (@charliehamu)

    There was a lot of stuff in my .htaccess file, including but not limited to:

    # BEGIN	WP 2.5 image upload	http error fix
<IfModule mod_security.c>
<Files async-upload.php>
SecFilterEngine	Off
SecFilterScanPOST Off
</Files>
</IfModule>
# END WP 2.5 image upload http error fix

    And:

    #	Caching.
#		Server is providing both Last-Modified and ETag, so remove one.
Header unset ETag
FileETag none
#		Server sets both Cache-Control and Expires, so remove one.
Header unset Expires
#		1 year.
<FilesMatch	"\.(ico|pdf|flv|jpg|jpeg|png|gif|js|swf)$">
Header set Cache-Control "max-age=31556926, public"
</FilesMatch>

    I reverted to the minimum, only this:

    # BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

    The http -> https rewriting is being handled by the DreamHost Panel only.

    Later, I may figure out exactly which parts of my complicated .htaccess file were causing which problems.

    But now I’m getting this again when I click to connect to my Google account:

    Welcome to Site Kit! Let’s get you set up
    invalid parameter: ‘site_id’

    Ah, but that was resolved with incognito + troubleshooting mode. It’s all working now. If you leave this ticket open for a day or two, I’ll report the exact offending lines from my .htaccess file.

    Thanks!

    • This reply was modified 3 years, 2 months ago by CharlieHamu.
    Plugin Support James Osborne

    (@jamesosborne)

    Excellent troubleshooting, in particular with all the different methods redirects can be applied! And certainly, we’ll keep this open while you perform checks throughout the next couple of days.

    In relation to your troubleshooting with your .htaccess file if you had any third party plugins that add content or redirects to this file I would expect that while in troubleshooting mode using the Health Check & Troubleshooting plugin that these additional snippets would be removed. Some such plugins maybe overwrite the default .htaccess file. I’ll certainly do more testing to determine this.

    Let me know how you get on after some additional checks anyway.

    Plugin Support James Osborne

    (@jamesosborne)

    Hi @charliehamu, just following up with you to check whether Site Kit remains working for you as expected?

    Thread Starter CharlieHamu

    (@charliehamu)

    Yes, thanks. I haven’t yet had a chance to break it again.

    Hopefully this coming weekend. At the very least I’ll make a list of all the .htaccess directives that I removed, so that we can know that it was one or more of them that caused the problem.

    At any rate, in addition to your usual directions about incognito + no other plugins + default theme, you can add + stock WordPress .htaccess.

    Plugin Support James Osborne

    (@jamesosborne)

    Not a problem at all. I’ll keep the support topic open for when you get a chance to test! Thank you.

    Plugin Support James Osborne

    (@jamesosborne)

    @charliehamu Just following up with you on this. Would you like me to keep this support topic open for you to perform some additional checks?

    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.

Viewing 8 replies - 31 through 38 (of 38 total)
  • The topic ‘Your site may not be ready for Site Kit’ is closed to new replies.