I had this problem using Meteor and Ngrok, while trying to login with Google. I put the Ngrok URL in the Google Developer Console as redirect URLs, and went to the Ngrok URL page. The thing was that I didn't use Meteor's ROOT_URL when executing the app, so any redirect would go to localhost:3000 insted of the Ngrok URL. Just fixed it by adding the Ngrok URL as ROOT_URL on Meteor's configuration or by exporting it before executing the app on the terminal like: export ROOT_URL=https://my_ngrok_url

在我的例子中，我的证书应用类型是“其他”。所以我无法在凭证页中找到授权重定向uri。它似乎出现在应用程序类型:“Web应用程序”。但是您可以单击Download JSON按钮来获取client_secret。json文件。

打开json文件，你可以找到这样的参数:"redirect_uri ":["urn:ietf:wg:oauth:2.0:oob"，"http://localhost"]。我选择使用http://localhost，它很适合我。

The trick is to input the right redirect url at the point of creating the ID. I found that updating the redirect url once the ID has been created via an 'Edit' just doesn't get the job done. What also worked for me is duplicating the entire 'vendor' folder and copying it to the same location where the 'oauth' file is (just until you successfully generate the token and then you can delete the duplicate 'vendor' folder). This is because trying to point to the vendor folder via '../vendor/autoload' didn't work for me.

因此，删除您现有的麻烦客户端OAuth ID，并尝试这种方法，它将工作。

小心url末尾多余的/ http://localhost:8000和http://localhost:8000/不同

重定向URI(返回响应的地方)必须在api控制台中注册，错误指示您没有这样做，或者没有正确地这样做。

转到项目的控制台，在API Access下查看。您应该在那里看到您的客户端ID和客户端秘密，以及一个重定向uri列表。如果您想要的URI没有列出，单击编辑设置并将URI添加到列表中。

编辑:(来自下面评价很高的评论)请注意，更新谷歌api控制台和当前的更改可能需要一些时间。通常只有几分钟，但有时似乎更长。

这个问题的主要原因只会来自chrome和chrome处理WWW和非WWW不同取决于你如何在浏览器中输入你的URL，它从谷歌搜索并直接显示结果，所以发送的重定向URL在不同的情况下是不同的

添加所有可能的组合，你可以找到确切的url从fiddler, 400错误弹出不会给你确切的http和www信息