Facebook login “given URL not allowed by applicati

2019-01-06 12:02发布

问题:

I've added facebook login to my site. However, when I click the button, I get a red box that says:

Invalid Argument

Given URL is not allowed by the Application configuration.

If I continue to login then I get:

API Error Code: 100
API Error Description: Invalid parameter
Error Message: next is not owned by the application.

Not sure exactly what the problem is. Any thoughts are appreciated.

回答1:

Your settings must be incorrect.

Go to http://www.facebook.com/developers/ and edit the application you're working on.

On the "website" tab, look for "Site URL". This should be set to your website's URL "http://yoursite.com/"

Note that if you're using subdomains, you'll also need to update "Site Domain" to be "yoursite.com"



回答2:

You can set up a developer application and set the url to localhost.com:port Make sure to map localhost.com to localhost on your hosts file

Works for me



回答3:

Also check to see if you are missing the www in the url which was on my case

i was testing on http://www.mywebsite.com and in the facebook app i had set http://mywebsite.com



回答4:

I was getting this problem while using a tunnel because I:

  1. had the tunnel url:port set in the FB app settings
  2. but was accessing the local server by pointing my browser to "http://localhost:3000"

once i started punching the tunnel url:port into the browser, i was good to go.

i'm using Rails and Facebooker, but might help others just the same.



回答5:

According to http://developers.facebook.com/docs/reference/dialogs/oauth/

for me worked

https://apps.facebook.com/YOUR_APP_NAMESPACE (watch fot http:// or https:// issue)



回答6:

I kept getting this error, when using wildcard subdomains with my app. I had the site url set to: http://myapp.com and app domain also to http://myapp.com, and also the same value for the Valid OAuth redirect URIs in the advanced tab of the settings app. I tried different combinations but only setting the http://subdomain.myapp.com as the redirect value worked, of course only for that subdomain.

The solution was to empty the redirect fields, leave it blank, that worked! ;)