Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi @saraespana1986,

    Thanks for reaching out. This error generally appears if you’ve not registered ‘Authorized redirect URI’ (where the response is returned to) or registered incorrectly in the APIs console. Please make sure you’re using the keys of the same App, double-check the URL, save the settings and click on ‘Allow plugin to send emails..’ button.

    Alternatively, you can follow all the steps in the tutorial again.

    I hope this helps!

    Thread Starter saraespana1986

    (@saraespana1986)

    Good Morning. Thanks for your reply.

    I have already done all these steps but when I pressed ‘Allow plugin to send emails ..’ button the same error continues to appear.

    From the Plugin Administration section, I get this error when trying to send the form:

    EMAIL DELIVERY ERROR: The WP Mail SMTP v2.1.1 plugin logged this error the last time you tried to send an email:

    Mailer: Gmail
    {
    “error”: {
    “code”: 401,
    “message”: “Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.” ,
    “errors”: [
    {
    “message”: “Login Required.”,
    “domain”: “global”,
    “reason”: “required”,
    “location”: “Authorization”,
    “locationType”: “header”
    }
    ],
    “status”: “UNAUTHENTICATED”

    Please, I need to solve this problem. Could you help me to another way?

    Hi @saraespana1986,

    Thanks for the details. It looks like your site is unable to connect to google for some reason. Unfortunately, I don’t have a suggestion with full resolution. You might want to check for the plugin conflicts deactivating all other plugins temporarily or contact your hosting provider to see if any firewalls is blocking the request from google.

    I hope this helps!

    Hi @saraespana1986 – We haven’t heard from you in about a week, so I’m going to go ahead and mark this ticket resolved. If you still have questions, though, please feel welcome to continue the conversation.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Error 400: redirect_uri_mismatch’ is closed to new replies.