• Resolved SchaOn

    (@schaon)


    “An error occurred: We are unable to send credentials to your WordPress site. This may be caused by a plugin or your hosting provider blocking incoming POST requests or restricting REST API access. Please check your plugins or reach out to your hosting provider.”

    Also having the same issue just like https://www.ads-software.com/support/topic/error-on-sign-in-with-google/. I am able to get to the /?rest_route=/ no problem (even when testing from Google Page Insights – https://developers.google.com/speed/pagespeed/insights/?url=)

    CDN: Cloudflare (which we do have a bunch of ASNs blocked for things like Amazon, GoDaddy and other hosts that should not be sending us traffic essentially – basically we’ve found that traffic from those type of providers normally are just scanning for vulnerabilities or attempting hacking, or scanning our sites to see what they can sell about us)
    Host: Namehero

    Also, nothing is showing in the firewall logs for CF or Wordfence… but curious, is there a specific IP address(es) that should be whitelisted?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Renee Johnson

    (@reneesoffice)

    @schaon thanks so much for opening a new topic! Really appreciate the details as well.

    1) Are you on the latest version of Site Kit version 1.0.4?

    2) Site Kit sends an incoming REST API (POST) request with the user agent “Site Kit by Google/1.0”. Allowances for that is required for setup.

    3) Alternatively, you can disable security and caching mechanisms temporarily during the setup process which has helped some users. See our document here for more tips and known limitations.

    Please let me know if any of these help in your case?

    Thread Starter SchaOn

    (@schaon)

    OK… I’ve done all that:

    Yes, version 1.0.4

    I don’t know what you mean by “2) Site Kit sends an incoming REST API (POST) request with the user agent “Site Kit by Google/1.0”. Allowances for that is required for setup.”

    So, I had disabled MOD Security, All caching plugins, Wordfence, bypassed Cloudflare, everything is HTTPS, using PHP 7.3.11… and still unable to sign in.

    Renee Johnson

    (@reneesoffice)

    @schaon we’ve just released version 1.1.0 and advise updating.

    That’s the method and the user agent Site Kit uses to send the setup request, so there might be something still blocking this. I’m going to set up an instance at Namehero to see if we can debug it further on our side. Thanks!

    Thread Starter SchaOn

    (@schaon)

    Updated to 1.1.0, disabled all those things previous, put CF into development mode, nada.

    Oh… also now… all I get is a blank screen when I go in. I don’t even get transferred to the sign on screen to even attempt logging in.

    Renee Johnson

    (@reneesoffice)

    Any browser console errors you can provide? Try a hard refresh (on Mac, shift + command + r). Thanks!

    Renee Johnson

    (@reneesoffice)

    @schaon were you able to clear out that blank screen? Plugin deactivation and reactivation may help too.

    Regarding Namehero, I didn’t experience anything blocking the request from my testing, so there seems to be something specific with your setup that’s interfering. I know you mentioned temporarily disabling Wordfence, but would you perhaps have Wordfence and its WAF active on site in the root directory and applied to all subdirectories like in these instructions? If the site you’re installing Site Kit on is in a subdirectory this can block the request.

    Please also note that we have plans to improve the the request method, but feel free to follow up regarding the above. Thank you.

    Plugin Support James Osborne

    (@jamesosborne)

    @schaon 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 addresses the issue you were encountering.

    With this update I will mark this support topic as resolved. As an early Site Kit user we value your input, please let me know if the latest update doesn’t resolve your issue, whereby I would be happy to assist further.?

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Unable to “Sign in with Google” during setup’ is closed to new replies.