I have a facebook app; as you know, facebook requires ssl certificates for app pages.
I've bought my SSL certificate from Godaddy. When I try to reach my app, it tries to access my https page but most of the time page takes very long time to load and then returns empty response error.
I am dealing with this problem most of the time and in only chrome, firefox and ie just works fine.
Is there any others who deal with this problem? How can I solve it?
Related
I am using Facebook's OAuth dialog to log in people in two of my websites.
Yesterday morning I discovered that the oauth dialog is failing for one of those two website, only when I try to connect with a mobile device (iphone and android).
The way I call the oauth dialog is identical in both websites, except from the App ID of course and the redirect url. Basically I redirect the user to:
https://www.facebook.com/dialog/oauth?client_id=xxxxxxxxxx&redirect_uri=http%3A%2F%2Fwww.xxxxx.xxx%2Ffbresult&response_type=code&scope=email
Normally the user is prompted for logging in with facebook and give permission to the app, and the be redirected back to my website.
This works perfectly fine on both sites if I use it from the Desktop.
When I call this url from my touch devices (iphone or android, they both fail) I am forcely redirected to the mobile version of the dialog (https://m.facebook.com/dialog/oauth?etc,etc).
However this dialog from m.facebook.com dies with 500 internal server error for one of the website. (so: one works perfectly with mobile oauth dialog, the other does not).
I tried to open the m.facebook.com/etc/etc from my desktop pc and I could indeed see the 500 internal server error response.
Should I try to login from the desktop (which does not redirect to mobile version) then the authentication procedure works perfectly.
At first I thought this might be a facebook bug and that it would have been fixed within few hours at most, but it's been now for at least 2 days and still does not work.
I think I could really appreciate some advice at this point. Thank you all in advance.
I'm using a self generated SSL certificate on my localhost IIS and pointed my facebook sercure Iframe app URL to https:\localhost but just get a blank page.
when browsing to it not within FB, it gives me the cert warning and then after i add it as an exception, it goes through to the site fine.
using http:\localhost for the non-secure url works fine
any ideas why i'm getting the blank page?
As I know FB checks your certificate and if it not valid it just wont load your app in the iframe. You can try this service that seams to be intended to exactly this kind of problems: http://www.social-server.com/.
Don't stress if you can't afford an SSL certificate for Facebook's SSL migration...
...Use this FREE service to adapt your Facebook pages so that it's viewable over an HTTPS connection.
I coded a stub application for Facebook.
When I'm trying access the app url (http://apps.facebook.com/myappname) it all works fine. It works from other servers as well.
However, a specific co-worker of mine is also trying to access it and he gets redirected to facebook.com
A day ago he was able to log-in, and we are not aware of any changes.
Thoughts, anyone?
This is common for when you don't have the required SSL server's url in the app settings. That other user that was redirected has allow only https set in his user preferences. Since you have no https version set, then he gets redirected away. If you do have the SSL server's url in your app settings, then the SSL cert may be bad. Many people try to get away with using a "fake" cheap SSL cert. The cert must be a real (read: expensive) one.
I have a Facebook page, but I dont have a SSL with me, so its always with the HTTP connection. So when I open the App Page (Canvas), I get an error within the iFrame Error 501 (net::ERR_INSECURE_RESPONSE): Unknown error. which is obvious due to the FB calling for HTTPS version of the page. But I noticed that some pages ask for "Switch to Regular HTTP Connection" to view the page. I was wondering how to do that, I googled a lot but couldn't find the relevant information.
Thanks
Do you have a url set for https on your app's settings page? You should leave it blank if you don't have a valid SSL page yet, and then it should give you the prompt to switch to regular http. However, you will want to get an SSL certificate soon as Facebook is recommending users switch to always-on SSL and at some point SSL may be the only option.
"Switch to Regular HTTP Connection" is limited to admins (at least without so many scary warnings) so it's important that you get an SSL connection running if you're going to have an app on FB now.
I've recently Discovered the following error because the SSL was expired.
This webpage is not available
The webpage at https://example.com/facebook/ might be temporarily down or it may have moved permanently to a new web address.
Error 501 (net::ERR_INSECURE_RESPONSE): Unknown error.
Renewed the SSL and all fixed
i am making a facebook tab which using iframe to show the tab content from other url. Everything work fine but when users use secure http connection (https) the tab no longer loads and shows error saying page not secure.
The pages that the iframe showing is not using ssl. Do i need to have a ssl to show the page in secure connection or i have to change some setting in facebook?
You will need to buy an SSL certificate, make sure it is properly installed on your server, and make sure your the page is properly working over SSL (no warnings). Once this is setup, plug the SSL url of your page onto your fan page tab application settings, and it will work. You will want to do this as Facebook is continually encouraging users to enable the always-on SSL option on their account, and at some point SSL may be the only option on Facebook and they probably won't give you much of a warning to enable it.
for now it's an option to have ssl certificate but starting from October the first, it will be required
i have set up my application, it works well for almost all browsers except google chrome, it seems to have a warning about my secure url of the ifram and doesnt load it, the only way i could work around it is visiting the actual url of the iframe, confirmed the ssl warning, then went back to the application on fb, so it finally worked
lousy solution i know, but there was nothing else i could do