Javascript Parse Facebook Login Issue

Question

I am getting:

Given URL is not whitelisted in Client OAuth Settings: This redirect failed because the redirect URI is not whitelisted in the app’s C

Answer 1

I'm also faced this problem. On my situation site url writen with "www". If you site adress http://example.com then http://www.example.com is different website for facebook sdk. In facebook application console go

Settings > Advanced > Client OAuth Settings >Valid OAuth redirect URIs

Write here www version also. It must work

Answer 2

I've just had the issue (November 5, 2017), after years of it working properly.

My issue was that the callback url was in the wrong place in the Facebook admin page. You need to put it in the "Facebook Login" "Products" (in the left menu, in the Facebook admin console, NOT in the "Advanced settings":

https://developers.facebook.com/apps/{{your FB app id}}/fb-login/settings/

You need to put the port number if you have one, e.g. in my case http://local.dishly.menu:3000/

Answer 3

After the new Developer portal updates, the OAuth redirect URIs can now be found under

Products > Facebook Login > Settings > Client OAuth Settings

or you can access via url: https://developers.facebook.com/apps/{appid}/fb-login/

Answer 4

I also faced the error while trying to integrate Facebook login on my localhost in a Rails app and fixed it by removing the trailing slash from the URL specified in Valid OAuth redirect URIs

It was: http://localhost:3000/auth/facebook/callback/

It was supposed to be http://localhost:3000/auth/facebook/callback

Thanks to @CBroe comment to check the redirect_uri and found that in the URL in the browser's address bar it was

https://www.facebook.com/dialog/oauth?client_id=<my_app_client_id>&redirect_uri=http://localhost:3000/auth/facebook/callback&response_type=code&scope=email&state=afcbee26c2ce5077f844ce864780082991d36e6c3e10863a

and in my Valid OAuth redirect URIs it was mentioned http://localhost:3000/auth/facebook/callback/ (note the trailing slash at the end)

Hope this helps anyone facing this problem with the URL problem I had.