Why will it often happen to me?
As a customer of Bell Internet, you can have up to three different user identities: Bell Internet user ID (b1) Bell.ca username Bell Mail email address 1. Skip to main content Personal. How to find the wireless network name and password on my Connection Hub modem. Yeah it did but I was also messing around with ssh-keygen on all my servers and trying to figure out how to get the machines to authenticate without using username/password and RSA Pub keys only so after I scrubbed all the Knownhosts files, recreated all the Pub keys and copied them into the Authorizedkeys files and it STILL was saying that, it kinda tipped me off.
This occurs after my program verify for user user login and redirect user to the authentication web page:
https://www.facebook.com/dialog/oauth?clientid=XXXamp;redirecturi=http%3A%2F%2Fexample.com%2Fmyappname%2Famp;state=YYYYYYamp;scope=offlineaccess%2Cpublishactions
But rather of showing the documentation page, Facebook displays an error web page with
An mistake occurred. Please try again later on.
Is certainly there any settings I possess to perform before try to authenticate my customers?
All is usually accomplished with PHP using the PHP-SDK courses.
34 Answers
12following
I acquired the same issue after transforming the domain of my web site. Altough I correctly transformed the requesturi parameter and up to date my app configurations with the new site, the mistake kept displaying up. Then I recognized that the Identity and the SECRET Identity of my Facebook APP got automatically transformed with no caution!! The whole thing started functioning again making use of the brand-new Identity.
I have got got the exact same problem as you.
From the Facebook Designers Apps web page, make sure that the Sandbox Mode is disabled.
This was occurring to me furthermore but all the api secrets, secrets and things were right. What I discovered is that my app has been operating in sandbox mode. Go to your app settings in https://developers.facebook.com/ click the advanced settings tab and verify to discover if your app is definitely in sandbox mode. If it is certainly disable it and try again. Let us understand if it functions.
I had been getting this error because I was starting from
http://mysite.com
, but acquired describedhttp://WWW.mysite.com
in my Facebook settings - the world wide web mattered. I ended up solving by making use of.httpaccess to constantly eliminate the 'world wide web', and directed FB tohttp://mysite.com
worst. subdomain. actually. :u)
When working with Dialogues, Facebook provide a 'showerror' feature that defaults to
no
but can be fixed tocorrect
in a Development atmosphere and can be really useful for debugging reasons.showerror - If this is set to true, the mistake program code and error explanation will be shown in the event of an mistake.
Instructions of it'beds make use of can become found in the Facebook Docs.
I'd happen to be debugging 'An Error occurred. Make sure you try later on.' dialogue before i discovered this feature in the docs. Once i started making use of it, i could observe the pursuing message as well:
API Error Program code: 191
API Error Explanation: The chosen URL will be not owned by the application
Mistake Information: redirecturi is certainly not possessed by the program.
I got the same issue; it turned out FB requires alineappID and not anint.
For me this happened because the 'test user' I made was part of a split app. I produced a check user for THIS app, and it started working great.
Silly on my component I know, but this could save someone else some problems.
Create certain your app can be configured to make use of the appropriate Web link amp; area of your web site. That may end up being it.
Regarding to OAUTH Dialog documentation:
.redirecturi:The URL to refocus to after the user ticks of a switch in the dialog. The Website address you state must be a Web link of with the same Base Site as selected in your app't configurations, a Canvas Web link of the type https://apps.facebook.com/YOURAPPNAMESPACE.
I was developing oauth hyperlinks dynamically to consult a user for extra permissions if required and I understood, that actually if you are manipulating to https://apps.facebook.com/YOURAPPNAMESPACE you have to possess the App Domain name and Internet site settings arranged in your program management. I established area to facebook.com and Site to facebooks basic website address.
Right now my oauth discussion link works great - actually in sandbox mode.
I experienced this exact issue on a Page Tab app and for the daily life of me couldn't work out what the issue had been. It worked on my check web page but as soon as I produced it live it wouldn't function. I discovered in the finish that I set the problem by placing the actual Website to the Page Tab (i.y.
http://www.facebook.com/lt;'pagename'gt;/applt;'appid'gt;
) into 'Site URL' under 'Site'. This doesn't make any sense. But it worked well :-)Remedy for me can be to arranged choice 'Authenticated Recommendations' to enabled. Its realy fixed after that.
The issue solved after I up to date the 'appID' and 'magic formula' and then sent the shift back again to heroku (we.elizabeth. 'git push heroku get good at')
The key is not to forget about to press the modifications back to heroku expert. Very easy to neglect if you're use to tests on localhost.
Hope this helps.
For me the problem has been that the Facebook customers I was making use of to check the app did not have its email address confirmed by Facebook.
My customer had established up 2 artificial balances on Facebook and informed me that they had been not functioning. But he forgot to confirm the e-mail contact information of those accounts (the emails Facebook sent proceeded to go to his junk e-mail folder and he didn't notice).
Required me hrs to find this, therefore I hope it helps someone.
Regards!
Also acquired a issue with wrong redirect hyperlink: I acquired a hyperlink beginning with 'https://apps.facebook.com?myapplication'. but after authorization the redirection would bring me to 'apps.facebook.com/Myapplication' and therefore I would obtain a message referred to above:'Mistake occured. Attempt back later on.' since 'apps.facebook.com'. means 'http://apps.facebook.com/Myapp' and not really 'HTTPS://apps.facebook.com/,.'
The alternative: proceeded to go to my software configurations in facebook designers section. Clicked on 'Edit'. In the left-side Menu chosen 'Permissions' (by default the Menu is arranged to Simple) and in the newly opened place of environment changed my 'Auth Symbol Parameter' from 'Issue string' to 'Web link Fragment'.
It worked well! After documentation is completed the users are taken to 'https://apps.facebook.com/myapp.'
Another achievable mistake, if you straight duplicated the code from Facebook SDK illustration then you may obtain the exact same error despite of having everything correct. http://developers.facebook.com/docs/reference/php/
This is certainly because in their illustration they have utilized backquotes rather of single rates for the key of the variety. The right code can be as follows.
If your all code is functioning properly after that to get rid of such kind of mistake move to Facebook Programmers Apps and disablesandbox setting.
I simply found this problem myself. I'm establishing an app internally, so my sponsor is certainly 'localhost'. It wasn't apparent how to fixed 'localhost' up in the app construction. If you desire to create locally, fixed up your app by using these actions:
- Proceed to the location where you control your Facebook app. Specifically, you need to end up being in 'Fundamental' under the 'Settings' menu.
- Include 'localhost' to 'App Domain name'.
- Under 'Select how your app combines with Facebook', select 'Site', and get into 'http://localhost/'.
Save and wait a few of moments for the information to pass on, although it proved helpful right aside for me.
I had place the limitation on the app that just United Expresses residence could make use of the app. I had been operating from Europe at the time this mistake message made an appearance. After removing the restriction everything worked.
Came right here with a comparable problem and, yes, my Sandbox was allowed. I disabled it and, voila, the login problem went apart. I must alert that this issue does not affect programmers and website managers as Facebook enables those users to notice the app. For this cause, I couldn't even believe that customers complained about not really being able to login, as I had been capable to login with no problems at all.
I experienced the same problem, and fix it by incorporating param amp;display=touch to url
try, it may helps
Solution for 2015
Sandbox setting is eliminated.
Proceed to
My Apps -gt; Your App -gt; Standing amp; Review
and alter the slider to yes for:Perform you want to make this app and all its live life features accessible to the general public?
If you're also the app developer, you may find a even more specific error information, but usually that information means one of two stuff:
- Your server returned a HTTP mistake code (usually 5xback button)
- You tried to send the user, after login, to a Link not permitted by your app construction (though as an Admin of the app, you should notice a even more specific mistake message and Facebook error code in this situation)
I acquired this mistake because I had been using
redirecturl
as a parameter rather ofredirecturi
.The Server-Side Authentication doc page says to use
redirecturl
:But this will be incorrect. The OAuth Discussion doc states to use
redirecturi
rather, which works, so I'm supposing that you can just use one and not the other:I got tried all the solutions mentioned right here. But it didn't work. I got to remove and produce again. I are estimating it was credited to new the 'Authenticated Recommendation'. If you have got added Open up Graph items which are usually not authorized, it might give you an error.
I had the exact same problem and the basic cause has been different:
I was logged in as a Check Consumer of a various application. Therefore I wasn't capable to authorize an app that's not the one particular where the Test User had been produced for.
When I logged away and logged in as a regular user or a Test User for the app I tried to authorize, everything had been OK.
In my situation, there was an age group concern with the account being utilized with the app.
If the FB app has alcoholic content material after that FB customers who are younger than about 21 will toss an error when trying to authorize with it.
For me the issue was that the website of the app didn'testosterone levels completely go with the url I has been working it on (i actually.e different directories, same domains)
There is usually no probability to resolve this type of mistake. Therefore Its much better to use your custom made dialog same like demonstrated in facebook and posting information again amp; again without login. Actually though you remove your app from facebook, you can ask for login and write-up message effectively.
The reason in my case was completely different. I was trying to open up a Feed dialog automatically after web page fill. And 9 situations of 10 it displayed this error. Very first, I added
showerror: correct
parameter as recommended by @Philip Roome, but it didn't help, exhibiting104: Ill signature bank
, not really descriptive at all.After that I thought out the reason. The code had been in
$(document).ready
jQuery function. And it appears that some facebook things had not really yet been recently loaded at the stage the program code had been to be performed. I shifted the code to$(window).fill
block out (which can be performed after all web page content is usually loaded), and the issue has become resolved.12next
guardedby chridamMay 18 '16 at 14:09
Say thanks to you for your curiosity in this question. Because it has fascinated low-quality or junk solutions that acquired to become removed, publishing an response now requires 10 reputation on this web site (the association bonus will not count up).
Would you like to reply to one of these unanswered queries instead?
Would you like to reply to one of these unanswered queries instead?