Can’t Authenticate, invalid OAuth request

  • Resolved Alexis Soucie

    (@adamsoucie)


    5 years, 2 months ago

    Having issues similar to several threads on here. On a fresh install of the plugin, I am unable to complete setup. After going through the guided steps, I am kicked back to the admin with the following error message:

    “Unable to receive access token because of an invalid OAuth request.”

    In reviewing other threads, I can confirm that my host is not the issue as I have another site with the plugin installed on the same server and they are working & authenticating just fine using the same version of the plugin. The only difference is that the site has been using Site Kit since before its full 1.0 release.

    No idea what’s going on, as this is happening with both my custom theme and the default Twenty Twenty theme and there are no noticeable plugin conflicts. I have set up Google Tag Manager separately since experiencing this issue, and am able to get Analytics info just fine without the plugin – no authentication issues.

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

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

    (@jamesosborne)

    @adamsoucie Thanks for reporting and adding additional context, very useful. We may need to troubleshoot further, any fix might possibly apply to others.

    Are you able to remove the Google Tag Manager implementation on your site once more, before then temporarily deactivating your other active plugins and attempting setup using a browser incognito window?

    If that fails please share your Site Health info. Please also inform me of how you have the property verified within Search Console.

    Thread Starter Alexis Soucie

    (@adamsoucie)

    I don’t know what happened, but after 4 days it’s now authenticating normally. No updates, no changes. Now it just works.

    @jamesosborne As for your questions, I do know there wasn’t a plugin conflict as I disabled all plugins and still experienced the issue.

    Either way, moot point now. Must have been a problem on Google’s end.

    @adamsoucie thanks for the update! Yes, we made some adjustments on our side. Glad to hear it’s resolved.

    MP

    (@therealmikep)

    @reneesoffice if there’s better place for this, let me know, and I’ll post there.

    I’ve been stuck with a similar issue for a few weeks. Here’s the behavior: SiteKit authenticates fine. Analytics fails with no on-screen errors (does toss a console violation message, more on that below.)

    When I click “Allow” on the oAuth Consent Summary screen, I’m just redirected back to the frontend of our site, Analytics doesn’t connect.

    Environment variables I’ve eliminated / troubleshat

    1. Deactivated all plugins except site kit
    2. Tried default theme (both twentynineteen and twentytwenty)
    3. New browser, hard cache clear, private tab (have tried this with Chrome, Safari, Firefox)
    4. Attempted on different WiFi networks
    5. Singed out of all Google accounts
    6. Added another email in Analytics, and attempted SiteKit connection using that account
    7. Uninstalled/Reinstalled SiteKit
    8. Moved site local, and to a subdomain
    9. No cache or security plugins enabled 4

    I’ve read and reviewed a handful of GitHub conversations about similarly sounding issues.

    Console violation shown when redirecting from oAuth to our site frontend is:
    [Violation] Forced reflow while executing JavaScript and
    webfont.js:25 [Violation] 'setTimeout'

    • This reply was modified 5 years, 1 month ago by MP.
    Plugin Support James Osborne

    (@jamesosborne)

    @therealmikep Thanks for the update, very useful context. As per WordPress support forum guidelines please open a new support topic and we can assist from there. In addition to what you’ve already provided if you want to also share your URL or Site Health information we may be able to identify something which is impacting setup.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Can’t Authenticate, invalid OAuth request’ is closed to new replies.