Facebook OAuth could not acquire an access token

I'm not sure what to recommend here, as FBOAuth looks as though it's still working just fine for my sites (also running the 1.4 version). I don't have IIS to test on, but I'd be surprised if it was responsible for the problem.

I really don't have much else to recommend to fix the problem. Perhaps you could try deploying your same site on different hardware (such as your local machine running WAMP or XAMPP) and see if you have better luck from there, that would indicate a problem with the server configuration. Or try the opposite and install a fresh copy of Drupal on your production hardware and see if FBOAuth works any better on that install, to rule out it being a module conflict.

Hunch is, since facebook can't access my local dev site, it just rejects the request?

Yeah in order for Facebook to work locally, you need to make an entry in your computer's HOSTS file to make it so your local install appears like a real address. For example I have an entry in my hosts file like this:

127.0.0.1 example.quicksketch.org

That makes it when I go to "example.quicksketch.org", it loads my localhost, instead of a remote site. That way I can test my Facebook app that is set up at the same URL.

Sorry I didn't get back to you on this one. I didn't have any further suggestions as FBOAuth continues to operate just fine for me. DId you figure out this issue?

I have the same problem

Everything worked fine until yesterday. I haven't changed anything on the server side but all of the sudden fboauth stopped working

Facebook OAuth could not acquire an access token from Facebook. We queried the following URL:
https://graph.facebook.com/oauth/access_token?client_id=***&client_secre...
. Facebook's servers returned an error 400:
{"error":{"message":"Error validating verification code.","type":"OAuthException","code":100}}

I have just discovered that the problem was related to destination parameter.

On pages where destination parameter was blank, fboauth returned this error. However on all pages where destination was referring to a specific page, the issue didn't occur. I resolved it by putting destination=front (where front is the path alias for my front page) for the front page.

Seems like a dirty patch but it works... http://greenhabit.org - see the url's under Join & Log In buttons if you need an example of what I meant.

I have a similar problem.

It has been working fine for me only on the home page; on other pages it works intermittently, even after adding "?destination=front" in the URL.

I've noticed the redirect_url parameter for the Facebook Connect is set to: "/fboauth/connect". Is this correct? Should this be set to the home page URL instead, so we don't need to add "?destination=front"?

I have FBOauth on 2 sites.
On one site it works perfect.
On the other site it is same problem as below.
When I press the button "Connect with Facebook", I come to Facebook login where I can write email and password.
The problem is that the my drupalsite responds "The Facebook login could not be completed due to an error..."

On Facebook I have made the same settings for the two sites' groups.

I wonder why it works on one site and not on another...? - Could it be something on Facebook?

After some more testing, I notice there is a difference in behavior between browsers.

IE seems to work best. For FF and Chrome, there is #_=_ appended to the redicted URL, but there is no "#_=_" appened for IE after logging in. Anybody can confirm what I am seeing?

According to Facebook, adding "#_=_" means....

(from https://developers.facebook.com/blog/post/552/ By Douglas Purdy - Friday, September 2, 2011 at 12:00pm)

Change in Session Redirect Behavior
This week, we started adding a fragment #_=_ to the redirect_uri when this field is left blank. Please ensure that your app can handle this behavior.

Does this mean the redirect_uri field is missing?

Thanks @cosmos11, that's interesting and useful to know. I hadn't be able to pin down where/why that was being added.

To clarify, I've whittled it down. It seems to be related to cookies/cache. I reset Chrome and all works again, must just be Facebook being very particular with security when you switch servers and the like.

Thank you ilya.bezdelev, your comment made me find the solution:

I was getting the same error when I was trying to get the token using "redirect_uri=http://localhost:3000" as parameter.
I just added a "/" at the end of the url and now it works...

I have a live site that used to be able to acquire tokens from Facebook and login and create users.

Now. What the user will see when pushing the F Connect-button:

30 seconds of silence and the error

"Facebook connect
The Facebook login could not be completed due to an error. Please create an account or contact us directly. Details about this error have already been recorded to the error log. "

What I see when the users push the F Connect button (obfuscated a little for security reasons)

The link on the button:
https://www.facebook.com/dialog/oauth?client_id=123456055203140&redirect...

The error in the error log:

"Facebook OAuth could not acquire an access token from Facebook. We queried the following URL:

https://graph.facebook.com/oauth/access_token?client_id=123456055203140&...

. Facebook's servers returned an error -110: "

I'm not convinced that Facebook's servers are to blame, though.

Pasting the above https://graph.facebook.com/oauth/access_token?client_id=123456055203140[... into a browser will deliver a beautiful access token.

Also, when using https://addons.mozilla.org/de/firefox/addon/tamper-data/ I see this

[total 1079ms] Status: 302[Found]
POST https://www.facebook.com/login.php?login_attempt=1&fbconnect=1&display=page&next=https%3A%2F%2Fwww.facebook.com%2Fdialog%2Fpermissions.request%3F_path%3Dpermissions.request%26app_id%3D12256523420340%26redirect_uri%3Dhttp%253A%252F%252Fwelovecuteanimals.de%252Ffboauth%252Fconnect%26display%3Dpage%26response_type%3Dcode%26perms%3Demail%252Cuser_about_me%26fbconnect%3D1%26from_login%3D1%26client_id%3D12256523420340&legacy_return=1 Load Flags[LOAD_DOCUMENT_URI  LOAD_INITIAL_DOCUMENT_URI  ] Content Size[0] Mime Type[text/html]
   Request Headers:
      Referer[https://www.facebook.com/login.php?api_key=12256523420340&skip_api_login=1&display=page&cancel_url=http%3A%2F%2Fwelovecuteanimals.de%2Ffboauth%2Fconnect%3Ferror_reason%3Duser_denied%26error%3Daccess_denied%26error_description%3DThe%2Buser%2Bdenied%2Byour%2Brequest.&fbconnect=1&next=https%3A%2F%2Fwww.facebook.com%2Fdialog%2Fpermissions.request%3F_path%3Dpermissions.request%26app_id%3D12256523420340%26redirect_uri%3Dhttp%253A%252F%252Fwelovecuteanimals.de%252Ffboauth%252Fconnect%26display%3Dpage%26response_type%3Dcode%26perms%3Demail%252Cuser_about_me%26fbconnect%3D1%26from_login%3D1%26client_id%3D12256523420340&rcount=1]
   Response Headers:
      Location[https://www.facebook.com/dialog/permissions.request?_path=permissions.request&app_id=12256523420340&redirect_uri=http%3A%2F%2Fwelovecuteanimals.de%2Ffboauth%2Fconnect&display=page&response_type=code&perms=email%2Cuser_about_me&fbconnect=1&from_login=1&client_id=12256523420340]
      

      
[total 177ms] Status: 302[Found]
GET https://www.facebook.com/dialog/permissions.request?_path=permissions.request&app_id=12256523420340&redirect_uri=http%3A%2F%2Fwelovecuteanimals.de%2Ffboauth%2Fconnect&display=page&response_type=code&perms=email%2Cuser_about_me&fbconnect=1&from_login=1&client_id=12256523420340 Load Flags[LOAD_DOCUMENT_URI  LOAD_REPLACE  LOAD_INITIAL_DOCUMENT_URI  ] Content Size[0] Mime Type[text/html]
      Referer[https://www.facebook.com/login.php?api_key=12256523420340&skip_api_login=1&display=page&cancel_url=http%3A%2F%2Fwelovecuteanimals.de%2Ffboauth%2Fconnect%3Ferror_reason%3Duser_denied%26error%3Daccess_denied%26error_description%3DThe%2Buser%2Bdenied%2Byour%2Brequest.&fbconnect=1&next=https%3A%2F%2Fwww.facebook.com%2Fdialog%2Fpermissions.request%3F_path%3Dpermissions.request%26app_id%3D12256523420340%26redirect_uri%3Dhttp%253A%252F%252Fwelovecuteanimals.de%252Ffboauth%252Fconnect%26display%3Dpage%26response_type%3Dcode%26perms%3Demail%252Cuser_about_me%26fbconnect%3D1%26from_login%3D1%26client_id%3D12256523420340&rcount=1]
   Response Headers:
      
      Expires[Sat, 01 Jan 2000 00:00:00 GMT]
      Location[http://welovecuteanimals.de/fboauth/connect?code=AQCeMq61jcJj4ZZv722YhWBbesBrDqYrhZPsnRCrD4GUnPXq9tI19pa1tdm3kw7AmPpf7B3zi3TTZDsVWYE3OEt-mc7xz3JzD1GhjtCcLYjD8ZNhn_yk0clnD_rtLjKn83fYiSIkr_4rqJhd9rhOGGJCqzO4KRnfHXpkPP6NqG_zGDZ-fZahKthIk6jeV7ZoAQg#_=_]
      
      
      
[total 35232ms] Status: 200[OK]
GET http://welovecuteanimals.de/fboauth/connect?code=AQCeMq61jcJj4ZZv722YhWBbesBrDqYrhZPsnRCrD4GUnPXq9tI19pa1tdm3kw7AmPpf7B3zi3TTZDsVWYE3OEt-mc7xz3JzD1GhjtCcLYjD8ZNhn_yk0clnD_rtLjKn83fYiSIkr_4rqJhd9rhOGGJCqzO4KRnfHXpkPP6NqG_zGDZ-fZahKthIk6jeV7ZoAQgQg#_=_ Load Flags[LOAD_DOCUMENT_URI  LOAD_REPLACE  LOAD_INITIAL_DOCUMENT_URI  ] Content Size[-1] Mime Type[text/html]
 

35232 ms - it looks like my own setup is at fault.

What on earth can provoke this error?

I suspect something serverside.

Hi everyone. I was hitting the same problem as the OP, and it turned out to be the uc_ssl module that was breaking it for me. The /user page has enforced SSL, meaning that the return url from Facebook was https://www.mysite.com/fboauth/connect which would then be denied and redirected to http://www.mysite.com/fboauth/connect (probably without the querystring or post data). I had to add 'FBOauth' => '/fboauth*', to the array inside uc_ssl_include_ssl_paths() , and now everything works great.

Hope that helps someone.

Cheers,
Matt

Thanks to @mattimck for pointing me to the right direction --
I had Secure Pages installed, needed to add fboath/* to "force HTTPS" in addition to users/*

hope this helps others!

Moving this back to a support request. As of right now it looks like these problems were caused by server misconfiguration or problems introduced by other modules. If there's a problem specifically we can fix in FBOAuth, please reopen or file a new issue.

Hello dear,
I got the solution,the solution is that,go to your App settings and just OFF the sandbox Mode,in this way you will newer get the error message.

I am getting the same issue but only with certain users. I, myself, cannot reproduce the error at all, in any browser. But I do see in the logs that it is happening to others. Would an update from 1.5 to 1.6 resolve the issue?

Solution:
CentOS 5: Disabling IPv6 on the ethernet card
CentOS 6: no such problem.

So "-110" is a serverside bug.

Here are the steps how you can resolve this :

1. Go to your app and "disabled" the sandbox mode.

2. When you disable it and click on save, it will ask for secure url .

3. open the "App on Facebook" tab and in "Secure Canvas URL:" add secure url of your website. For example if you have http://something.com . So enter https://something.com

4. Save and thats it.

--Sahil

At https://developers.facebook.com/apps/--yourappnumber--/settings/advanced/
Set all those things to -NO- then it will work.

Client OAuth Login

Embedded browser OAuth Login

App Secret Proof for Server API

Require 2-factor reauthorization