• Resolved CharlieHamu

    (@charliehamu)


    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://wordpress.org/
    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 http://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 15 replies - 1 through 15 (of 38 total)
  • Thread Starter CharlieHamu

    (@charliehamu)

    Also, with help from DreamHost support, these changes were made:

    /home/charliehamu/.php/7.4/phprc
    
          1 log_errors = 1
          2 error_log = /home/charliehamu/php.log
          3 upload_max_filesize = 600M
          4 post_max_size = 650M
          5 max_execution_time = 500
          6 max_input_time = 500
          7 memory_limit = 500M

    And I switched from php7.4 fastCGI to php7.4 CGI.

    Thread Starter CharlieHamu

    (@charliehamu)

    Also, I just tested this:

    wp eval 'print_r(wp_remote_head("https://sitekit.withgoogle.com"));'

    And got an extensive JSON-y looking result that includes both 200 and OK.

    Thread Starter CharlieHamu

    (@charliehamu)

    Thread Starter CharlieHamu

    (@charliehamu)

    Additional information, and a likely path to resolution:

    I temporarily changed:

    WordPress Address (URL)   https://danforthgreens.ca/wordpress
    Site Address (URL)        https://danforthgreens.ca

    to be

    WordPress Address (URL)   https://danforthgreens.ca/wordpress
    Site Address (URL)        https://danforthgreens.ca/wordpress

    And this seemed to work. (I got a message about search console needing some time to collect data.) But it messed up the URLs for my site, adding an unwanted /wordpress in the middle of the URLs.

    If this is the only solution, I can move my WordPress installation from the subdirectory up to the main directory. But I’d rather not, as there are other non-WordPress files in that directory as well.

    Thread Starter CharlieHamu

    (@charliehamu)

    According to this:

    https://github.com/google/site-kit-wp/issues/922

    It should not be a problem for WordPress to be installed in a subdirectory.

    Thread Starter CharlieHamu

    (@charliehamu)

    I verified in Google Search Console that I had three verified URL prefixes:

    1. http://danforthgreens.ca
    2. https://danforthgreens.ca
    3. https://danforthgreens.ca/wordpress

    (With or without trailing slashes, I do not recall.)

    And the domain danforthgreens.ca was not verified. I verified the domain using a DNS TXT record, reloaded, reconnected, etc, no success. I deleted the first three, so I only have the domain now, reloaded, reconnected, etc, still no success.

    I also turned off my browser’s ad-blocker, but that should only affect AdSense, I think. And I’ve tested on other machines, including a phone, and in incognito mode without Chrome extensions.

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for reaching out, and for sharing your Site Health information. From first inspection of your site it seems the http version of your site is accessible. Can you first of all ensure all http traffic is redirected to https? You may be able to do this from your Site Health status screen (Tools > Site Health > Status), with more information on this below:
    https://make.wordpress.org/core/files/2021/02/site-health-https-supported.png

    Alternatively you can use a plugin or check with your hosting provider to ensure all traffic is fully https.

    Let me know once you have this in place and we’ll perform some additional checks on your site. You’re correct that there should be no problem with your WordPress install in it’s own subdirectory.

    Thread Starter CharlieHamu

    (@charliehamu)

    I’m confused. HTTP is set to redirect to HTTPS in my hosting setup, and does so. Try visiting http://DanforthGreens.ca and you will be redirected to https://DanforthGreens.ca

    Site Health reads:

    Your website is using an active HTTPS connection.

    An HTTPS connection is needed for many features on the web today, it also gains the trust of your visitors by helping to protecting their online privacy.

    Read more about why you should use HTTPS (opens in a new tab)

    Specifically, the redirect is in my .htaccess file:

    RewriteEngine On
    
    # If HTTPS is off, turn it on.
    RewriteCond %{HTTPS} !=on
    RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301,NE]

    Is there something else I should do, such as completely disallowing HTTP? I wouldn’t want to break links that are coming in to HTTP, just redirect them.

    I see that there is a setting available in the DreamHost panel:

    AUTOMATIC HTTPS IS DISABLED FOR THIS SITE

    [_] Redirect all site content over a secure HTTPS connection.

    Disabling this setting will slow the loading of your site and will default to insecure connections. You should only disable this setting if your site requires special redirect settings in your .htaccess file or you want to allow mixed content on your site. (This is not common.) More Info

    I’m going to try turning this on.

    AUTOMATIC HTTPS IS ENABLED FOR THIS SITE

    [x] Redirect all site content over a secure HTTPS connection.

    Still no improvement after simple resets and full deactivate-reactivates.

    Thread Starter CharlieHamu

    (@charliehamu)

    Another possible clue. I deactivated Site Kit and activated JetPack. Inside JetPack, when I went to turn on stats, I got the response “Error updating settings. FetchNetworkError”. I’ve now deactivated JetPack.

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for the update. Your http site is redirecting now, so all good on that front! Thanks for performing that check.

    Now that your redirection is working as expected can you follow the steps below, which would help rule out caching or other plugins impacting Site Kit setup?

    1. Login to your site from a Chrome browser incognito window
    2. Install and activate the Health Check & Troubleshooting plugin.
    3. Navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot”.
    4. From the same screen click on the “Available Plugins” tab at the top right and then click on the “Enable” option next to “Site Kit by Google”
    5. Attempt to setup Site Kit once more

    You can exit troubleshooting mode afterwards.

    Let me know if you’re able to proceed with Site Kit setup with the above. If not please share at what point you’re unanble to proceed, and whether you encountered the “Your site may not be ready for Site Kit” during setup.

    Thread Starter CharlieHamu

    (@charliehamu)

    I only get the “Your site may not be ready for Site Kit” message, at the top of the plugins page, when I activate Site Kit. I can’t activate site kit when in troubleshooting mode, only enable it. When I enable it (either by first enabling troubleshooting mode as you suggest and then enabling Site Kit within troubleshooting mode, or by directly clicking “troubleshoot” next to Site Kit), I still get the same results on the Site Kit dashboard: “Data error in Search Console” / “You are probably offline.”

    Plugin Support James Osborne

    (@jamesosborne)

    Appreciate you going to the trouble of performing that check. As I’m unsure if you had Site Kit connected previously, before inserting WordPress files into it’s own subdirectory one additional check you can do is to perform a reset of the plugin (Tools > Available Tools > Reset Site Kit). After doing so you can attempt setup once more.

    Note that when resetting all services will be disconnected, at which point you would need to connect once more. All other connected users would also become disconnected.

    Also to answer your initial questions – which I never addressed, there should be no issue with having WordPress within a subdirectory. I suspect that if you moved the plugin to a subdirectory after Site Kit was successfully connected there may be situations whereby errors could be encountered depending on your setup. When connecting a site a users wp-admin and site URL are registered on the Site Kit service. Any changes to a users wp-admin path could for example result in issues if you were to attempt disconnecting Site Kit and connecting once more. As you’re the only connected user this shouldn’t be an issue.

    There should also be no issues in relation to the URLs not matching, as long as the WordPress address is based off your site address.

    Let me know how you get on with a reset anyway.

    Thread Starter CharlieHamu

    (@charliehamu)

    I’ve reset many times. Just did again now (while in troubleshooting incognito mode). No change.

    In detail:

    The “Reset Site Kit” link didn’t actually disconnect me: I still saw my face in the upper right-hand corner. But I did go there and “Disconnect”, as I had done several times in the past. This time, after disconnecting, I had a button to connect and a link to reset just to the right of that button. So I reset again for good measure. Then when I went to connect, I got the message that Site Kit already had some access to my site (as I had received multiple times in the past). This time, for the first time, I went to my Google Account and removed all of Site Kit’s permissions first. Then they got re-added when I reconnected. Same results. Same “Your site might not be ready” before and same “You are probably offline” after.

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for performing this check. While I’m going to check Site Kit setup with WordPress in it’s own subdirectory today can you perform one additional check? Please share whether the same “You are probably offline” notice occurs from another device, and if so does it also appear on this additional device while in troubleshooting mode.

    If so please share any console errors on the same screen. You can use a service such as Imgur to share images.

    I’ll let you know once I setup an environment similar to your own and check. This will be at some stage today.

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for your patience on this. I’ve been unable to encounter the same notice with WordPress in it’s own directory.

    I also performed some additional checks on your site and the cause may be mixed content on your site. I’m aware you made changes to address this although there may be some legacy references to http resources. There are plugins that can ensure all resources are served over https. Let me know once you’ve had a chance to review this. I’m happy to check your site once more after all your site and it’s resources are fully secure.

Viewing 15 replies - 1 through 15 (of 38 total)

The topic ‘Your site may not be ready for Site Kit’ is closed to new replies.