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

    (@jamesosborne)

    @inigo Thanks for reporting, and apologies for the late response. Nice troubleshooting. In your case that error is likely due to your hosting provider blocking incoming REST API requests. The REST API needs to be enabled and accept incoming POST requests from the “Site Kit by Google/1.0” user agent.

    You can contact your hosting provider and confirm with them. Once resolved at host level we can check to ensure setup completes successfully. I can keep this support thread open until you check.

    Thread Starter inigo

    (@inigo)

    @jamesosborne thx for your reply
    As I said I can reach the api with a POST request using postman.

    {
        "code": "rest_not_logged_in",
        "message": "You are not currently logged in.",
        "data": {
            "status": 401
        }
    }

    It gives the same reply as the error in SiteKit

    I am wondering how authorizes SiteKit itself?
    That is by using the wp_nonce isn’t it?
    And some other parameters which are send to SiteKit by the url which I pasted in.

    Can you specify which params I should send along with the POST request for it to authenticate?
    i.e.
    _wp_nonce XXXX
    user user_ID

    so I can mimic in POSTMan
    the request.

    I was wondering if this: admin_root=%2Fwp-admin%2F is correct.
    It represents nothing resembling me as current user

    Plugin Support James Osborne

    (@jamesosborne)

    @inigo The proxy service currently in use makes a nonce-authorized REST API request back to the site to pass back the OAuth credentials. You can see the current flow here.

    We are currently updating the mechanism to exchange credentials in the next release, which should be this week. You can find out more about this here.

    Thread Starter inigo

    (@inigo)

    @jamesosborne Ok
    Most wise thing: wait, update and try again?

    Plugin Support James Osborne

    (@jamesosborne)

    @inigo Yes indeed, and I’m confident we won’t have to keep you waiting long!

    Plugin Support James Osborne

    (@jamesosborne)

    @inigo Just following up with you in relation to your previous issue with Site Kit setup. We have made some significant updates to the plugin as of version 1.1.2, which should address the issue you were encountering.

    Can you update to this latest version and confirm everything is working as expected?

    Thread Starter inigo

    (@inigo)

    @jamesosborne
    GREAT
    Now it works like a charm
    Thx a bunch

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

    (@jamesosborne)

    @inigo Great to hear, and thanks for the update. Thankfully you didn’t have to wait too long.

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Sitekit installation: An error occurred: We were unable to send credentials to y’ is closed to new replies.