• Resolved solgudinde

    (@solgudinde)


    Hello,

    I’ve read several of these topics, but none of them seem to solve my problem, and I’ve been stuck with this issue for hours. I’ve followed the tutorial document carefully several times, but every time I try to authenticate on WordPress, I get the same error message:

    Error 400: redirect_uri_mismatch

    Screenshot

    Hopefully you can help!

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

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Laura – WPMU DEV Support

    (@wpmudev-support8)

    Hi @solgudinde

    I hope you’re well today!

    There are two very common reasons for this issue so let’s start with those:

    1. please access your app (that you created for it) in Google developers console and check OAuth configuration there; make sure that you have
    – added correct “authorized domain” there, matching your site’s domain
    – and provided e-mail address in “developer’s contact details section”
    – if the app and site is live also make sure that the “application home page” address and site itself uses “https://” prefix and has valid SSL certificate

    2. when authorizing application make sure that you are actually already logged in to correct Google account in your browser; if you are logged in to multiple accounts, make sure to switch to correct one or use a different browser where you login only to that one that you are using for app; this is one of the most common issues – integration set using one account but authorization attempted with another one due to it being default in browser

    Please double-check it and if it still doesn’t solve the issue, let us know here.

    Kind regards,
    Adam

    Thread Starter solgudinde

    (@solgudinde)

    Hi Adam,

    Thanks for the fast reply.
    I went through your instructions, but unfortunately I still experience the same error message.

    Can you tell me if what I’ve done here should suffice?
    Screenshot

    Best wishes

    Plugin Support Patrick – WPMU DEV Support

    (@wpmudevsupport12)

    Hi @solgudinde

    I hope you are doing well.

    It seems fine but just the prefix, it looks like the WordPress forum added some extra strings on Adam’s replies, it should be only https:// you can remove the &#8221 part

    https://monosnap.com/file/dBmlqVl5mGbn1XPLIbLkUmTXEEQXH4

    Also, an important note, when you try to connect it will generate a new ID in Forminator, make sure to have the updated Authorized redirect URIs:

    https://monosnap.com/file/g38I1SG6Qf9lRsrQkicZ8p97VsRzeo
    https://monosnap.com/file/vpz05DYVAae72DmFU14kWvGfBlnr2f

    Best Regards
    Patrick Freitas

    Plugin Support Amin – WPMU DEV Support

    (@wpmudev-support2)

    Hello @solgudinde ,

    We haven’t heard from you for several days now, so it looks like you don’t have any more questions for us.

    Feel free to re-open this ticket if needed.

    Kind regards
    Kasia

    Thread Starter solgudinde

    (@solgudinde)

    Hi Patrick and Adam,

    Sorry for not replying in time; I was on vacation.

    The issue is unfortunately still present, and I get the same error message even with following your instructions.

    Can I provide any information or screenshots for you to help me?

    Best wishes

    Plugin Support Imran – WPMU DEV Support

    (@wpmudev-support9)

    Hello @solgudinde !

    I’m sorry to hear that the issue is still there!

    In fact, in the meantime our Forminator team have identified the cause of the issue and they’ve already developed a fix for it. The fix is ready and it will be included in the upcoming update of the plugin which will be released shortly.

    Kind regards,
    Pawel

    Thread Starter solgudinde

    (@solgudinde)

    Hello again @wpmudev-support9

    I have tried again from scratch after having updated the Forminator plugin on my website, but unfortunately, I’m still getting the same error message.

    What can I do? I’m starting to give up here..

    Best wishes!

    Plugin Support Laura – WPMU DEV Support

    (@wpmudev-support8)

    Hi @solgudinde

    I have tested it with current version of Forminator just now and it worked fine for me but not if I tried to “re-authorize” from Forminator end or use existing OAuth key with new integration.

    First, I had to make sure that Google Sheets integration is not showing up on “Connected apps” list on “Forminator -> Integrations” page. So if you are seeing it there, do disconnect all the instances (even if they are not properly authorized).

    If you cannot disconnect them, try this:
    – regenerate secret key in Google
    – update it in Google Sheets integration and try to re-authorize
    – at some point it will say redirect_uri_mismatch error but then the integration popup in Forminator will keep the spinning wheel; if you close it now and reload the Integrations page – Google Sheets will be gone from the “Connected Apps” section.

    Once that’s done, go to your Google App and remove the OAuth key from there; if there are more than one, remove all of them.

    Then set the new one (just like when creating the app from scratch) and make sure to save it in Google before clicking authorize button in Forminator. It should work right away this way (note: if you are using multiple Google accounts make sure that the browser is logged in to correct one).

    Kind regards,
    Adam

    Thread Starter solgudinde

    (@solgudinde)

    Ah!!

    Thank you so much, it finally worked :’)))))

    It seemed that deleting my former projects and maybe, as well, saving before authorizing helped!

    I’m so happy we can finally have sheets! Thanks for all of your help and support!
    10/10

    Best wishes

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

The topic ‘Google Sheets Error 400: redirect_uri_mismatch’ is closed to new replies.