Site Kit Stucking at “Checking compatibility”

  • Resolved onurparlar

    (@onurparlar)


    3 years, 9 months ago

    Site Kit setup a user is stuck at the “Checking compatibility” stage. The “Start setup” button doesn’t appear.

    It was working before, after new WP update problem started.

    I check everythink in this topic

    But didnt working…

    • This topic was modified 3 years, 9 months ago by onurparlar.

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

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Thanks for opening a support topic. From inspecting your site source code it looks like your using an optimisation plugin to minify and combining assets. Can you try and follow the steps below and inform me if you’re able to proceed?

    1. Install and activate the Health Check & Troubleshooting plugin.
    2. Navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot”.
    3. 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”
    4. Attempt to setup Site Kit once more

    You can exit troubleshooting mode afterwards. The above steps will temporarily deactivate all plugins for you only, as a logged in user, while switching to a core theme.

    Let me know how you get on after attempting the above.

    Thread Starter onurparlar

    (@onurparlar)

    Hey @jamesosborne
    Thank you for your fast respone.

    I tried your steps but problem still exist…

    Plugin Support James Osborne

    (@jamesosborne)

    That’s unfortunate. Can you share any console errors you encounter when attempting setup using a Chrome browser incognito window?

    Thread Starter onurparlar

    (@onurparlar)

    POST https://www.sanalsergi.com/wp-json/google-site-kit/v1/core/site/data/setup-tag?_locale=user 403

    this error is looping…

    also this one;

    GET https://www.sanalsergi.com/wp-json/google-site-kit/v1/core/site/data/health-checks?_locale=user 403

    • This reply was modified 3 years, 9 months ago by onurparlar.
    Thread Starter onurparlar

    (@onurparlar)

    also them;

    

googlesitekit-vendor.55a2eea67c06c394593b.js:1 POST https://www.sanalsergi.com/wp-json/google-site-kit/v1/core/site/data/setup-tag?_locale=user 403
j @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
s @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
forEach.e.<computed> @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
n @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
_next @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
s @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
a @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
o @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
t @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
s @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
a @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-api.c3305021ff3630c5df8d.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.then (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.catch (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.then (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.catch (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.then (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.catch (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.then (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.catch (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.then (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.catch (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.then (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.catch (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.then (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.catch (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.then (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.catch (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.then (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.catch (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.then (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.catch (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.then (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.catch (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.then (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.catch (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.then (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.catch (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.then (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.catch (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.then (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.catch (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.then (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
Promise.catch (async)
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
E @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
(anonymous) @ googlesitekit-vendor.55a2eea67c06c394593b.js:1
googlesitekit-vendor.55a2eea67c06c394593b.js:1 GET https://www.sanalsergi.com/wp-json/google-site-kit/v1/core/site/data/health-checks?_locale=user 403
    • This reply was modified 3 years, 9 months ago by Yui.
    • This reply was modified 3 years, 9 months ago by Yui.
    Thread Starter onurparlar

    (@onurparlar)

    Also I found this:

    WebSocket connection to ‘wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data’ failed: Error during WebSocket handshake: Unexpected response code: 403

    Plugin Support James Osborne

    (@jamesosborne)

    Interesting, thanks for the update. The 403 error may indicate a hosting or firewall restriction. Do you have any additional sites on the same hosting provider which we can check with, or preferably can you temporary disable any WAF such as ModSecurity temporarily at host level?

    If you can fill in this form and include your hosting provider I can also see if I can check from my side.

    Thread Starter onurparlar

    (@onurparlar)

    @jamesosborne I’ve filled form.

    Thank you

    I’m waiting your answer.

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for sharing. Can you try and temporarily deactivated the your hosting provider CDN and Firewall before attempting Site Kit setup once more?

    Thread Starter onurparlar

    (@onurparlar)

    @jamesosborne,
    I’m not using CDN and firewall ??

    but i tried disable cloudflare…

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

    (@jamesosborne)

    Interesting, I may need to contact Namecheap in order to check this to ensure you’re able to proceed with setup. I believe ModSecurity is enabled by default with your hosting provider and I suspect this may be impacting setup in your case.

    While I check this with your hosting provider can you share whether you encounter the same issue during setup on another site with the same hosting provider?

    Thread Starter onurparlar

    (@onurparlar)

    yeah it was all about ModSecurity…
    now everything is working.

    thank tou @jamesosborne

    Plugin Support James Osborne

    (@jamesosborne)

    No problem at all, thanks for the update. This is great to know should other users also encounter the same issue.

    If you have a moment free please consider sharing your thoughts on using Site Kit so far, we’d love to hear your feedback.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Site Kit Stucking at “Checking compatibility”’ is closed to new replies.