12
votes

yep, getting the 191 error. I've researched and found this question to be helpful: Facebook API error 191

My URL looks like:

https://www.facebook.com/dialog/oauth?client_id=&redirect_uri=http%3a%2f%2flocalhost%2fFb.201109Birthday%2fOAuth2.aspx

However, I get an error:

API Error Code: 191 API Error Description: The specified URL is not owned by the application Error Message: Invalid redirect_uri: Given URL is not allowed by the Application configuration.

I've read everywhere that the urls must match up to what's listed in the application's setting page. I've got

I've also tried local.facebook-apps.com (replaced "localhost" everywhere above with "local.facebook-apps.com") with a hosts file entry to point to 127.0.0.1. But all of these scenarios still give the 191.

5
possible duplicate of Facebook API error 191genesis

5 Answers

6
votes

Remove the Birthday.aspx from the Canvas URLs.

3
votes

I was also getting this error when i created a facebook application that was going to be installed onto a tab on a fan page. It turns out that when i first created my facebook application i only filled out the section for "Page Tab" but i didn't fill out the section for "App on Facebook".

i didn't fill out the App on Facebook section because i didn't want users trying to add the app from the app profile page. Anyway, it turns out that by not filling out the App on Facebook section and adding a canvas URL and secure canvas URL i was getting the Error: 191 when trying to make a javascript call to FB.Login().

Once i filled out the App on Facebook section the error went away.

1
votes

Filling up the "App on Facebook" page, with Canvas url, ended with / solvet it for me

ex: canvas url.

1
votes

above issue can be removed via providing the URL for the web site or localhost you are working on, at https://developers.facebook.com/apps/ under Edit-->Website with Facebook Login

Website with Facebook Login

-1
votes

Web forwarding occurs 191 problem.

I used web forwarding for app's domain.

I had problem 191 and solved by fixing original url.