Title: Error 400: invalid_request
Last modified: March 11, 2022

---

# Error 400: invalid_request

 *  Resolved [Julian Song](https://wordpress.org/support/users/julians3/)
 * (@julians3)
 * [4 years, 2 months ago](https://wordpress.org/support/topic/error-400-invalid_request-2/)
 * Follow the website & youtube to setting for Google Workspace and receive this
   error.
 *     ```
       Error 400: invalid_request
   
       You can't sign in to this app because it doesn't comply with Google's OAuth 2.0 policy for keeping apps secure.
   
       You can let the app developer know that this app doesn't comply with one or more Google validation rules.
   
       Request Details
       The content in this section has been provided by the app developer. This content has not been reviewed or verified by Google.
       If you’re the app developer, make sure that these request details comply with Google policies.
   
       redirect_uri: urn:ietf:wg:oauth:2.0:oob
       ```
   

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

 *  [Nikolaiii](https://wordpress.org/support/users/nikolaiii/)
 * (@nikolaiii)
 * [4 years, 2 months ago](https://wordpress.org/support/topic/error-400-invalid_request-2/#post-15451116)
 * I have successfully configured a few Google Workspace accounts with Fluent SMTP
   until now and never had an issue. But this morning I got the same error. I wonder
   if did anything changed on the Google side?
 *  [balticsamurai](https://wordpress.org/support/users/balticsamurai/)
 * (@balticsamurai)
 * [4 years, 2 months ago](https://wordpress.org/support/topic/error-400-invalid_request-2/#post-15459465)
 * Yep, same problem. Suddenly, stopped working. When I try to authenticate token,
   get error
 *     ```
       Authorisation Error
       Error 400: invalid_request
   
       You can't sign in to this app because it doesn't comply with Google's OAuth 2.0 policy for keeping apps secure.
   
       You can let the app developer know that this app doesn't comply with one or more Google validation rules.
       ```
   
 * The content in this section has been provided by the app developer. This content
   has not been reviewed or verified by Google.
    If you’re the app developer, make
   sure that these request details comply with Google policies. redirect_uri: urn:
   ietf:wg:oauth:2.0:oob
 *  [thrivingnow](https://wordpress.org/support/users/thrivingnow/)
 * (@thrivingnow)
 * [4 years, 2 months ago](https://wordpress.org/support/topic/error-400-invalid_request-2/#post-15470335)
 * Yes, same issue here. First time install. Not… encouraging. Anyone figured this
   one out?
 *  [felixhtoo30](https://wordpress.org/support/users/felixhtoo30/)
 * (@felixhtoo30)
 * [4 years, 1 month ago](https://wordpress.org/support/topic/error-400-invalid_request-2/#post-15602840)
 * Yep, I also got this problem when I click the “Authenticate with Google & Get
   Access Token” button. That issue is still happening.
 *  [nickwe](https://wordpress.org/support/users/nickwe/)
 * (@nickwe)
 * [4 years ago](https://wordpress.org/support/topic/error-400-invalid_request-2/#post-15615416)
 * Same for me, have configured multiple gmail account in the past for FluentSMTP,
   and now it get stuck for the same reason at the same step 🙁
 *  [balticsamurai](https://wordpress.org/support/users/balticsamurai/)
 * (@balticsamurai)
 * [4 years ago](https://wordpress.org/support/topic/error-400-invalid_request-2/#post-15616896)
 * For those who are interested, I personally solved it by using Post SMTP plugin
   instead of FluentSMTP. I think they use a different way to connect to Google 
   Account but it works. I hope I’m not stepping on the FluentSMTP team’s toes here.
   Overall, I think they are doing a great job with all their plugins (we’ve set
   up some of their other plugins for clients) but I had to resolve it for the client
   fast, and I was left with no options.
 *  Plugin Support [Amimul Ihsan](https://wordpress.org/support/users/amimulihsanmahdi/)
 * (@amimulihsanmahdi)
 * [3 years, 12 months ago](https://wordpress.org/support/topic/error-400-invalid_request-2/#post-15694772)
 * Hi,
 * Sorry, we missed your ticket earlier. For any further queries, please open a 
   support ticket in our dedicated support channel.
 * As Google has updated the API settings the error is coming. According to our 
   investigation, it appears that if you are a Google WorkSpace user then you need
   to set the user type to internal.
 * Furthermore, if you are a free Google user, you must connect to the app in test
   mode as an external user. After connecting the app, you must publish it from 
   testing so that your API key does not expire. We will update our documentation
   soon.
 * Thank you

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

The topic ‘Error 400: invalid_request’ is closed to new replies.

 * ![](https://ps.w.org/fluent-smtp/assets/icon.svg?rev=2458343)
 * [FluentSMTP - WP SMTP Plugin with Amazon SES, SendGrid, MailGun, Postmark, Google and Any SMTP Provider](https://wordpress.org/plugins/fluent-smtp/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/fluent-smtp/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/fluent-smtp/)
 * [Active Topics](https://wordpress.org/support/plugin/fluent-smtp/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/fluent-smtp/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/fluent-smtp/reviews/)

 * 7 replies
 * 7 participants
 * Last reply from: [Amimul Ihsan](https://wordpress.org/support/users/amimulihsanmahdi/)
 * Last activity: [3 years, 12 months ago](https://wordpress.org/support/topic/error-400-invalid_request-2/#post-15694772)
 * Status: resolved