Topic-icon http 500 error with facebook login

Active Subscriptions:

None
14 years 7 months ago #14747 by oliverious
The corresponding URL is:
smsitout.com/index.php/component/jfbconn...bookUser&return=Lw==

The corresponding API error is:
Facebook API Error: SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

The CA cert should be OK. (No error found. How can I definiteley check it?)

What concequences has it when I disable the cerficate validation?
The topic has been locked.
Support Specialist
14 years 7 months ago #14752 by alzander
The SSL cert error your getting isn't with the SSL cert on your site, it's with your server validating the cert that comes back from Facebook.

You should enable the "Disable SSL Certificate Validation" setting in the Facebook API tab of configuration. That setting is actually named poorly, as it's from the previous 3.x series. In 4.x, enabling that setting will simply use a file that we distribute with JFBConnect which will validate the certificate from Facebook.

Try it with that setting enabled, and you shouldn't run into any issues (or bad consequences). If you still run into issues, just let us know!
Alex
The topic has been locked.
Active Subscriptions:

None
14 years 7 months ago #14758 by oliverious
OK, so I disabled the certificate validation now.

I still get http 500 errors from time to time in the frontend when I try to login with facebook AND in the backend when calling the overview page. these are the urls:

backend:
smsitout.com/administrator/index.php?opt...nect&view=jfbconnect

frontend:
smsitout.com/index.php/component/jfbconn...bi1hbmQtaGVscC5odG1s
The topic has been locked.
Support Specialist
14 years 7 months ago #14763 by alzander
If you're getting a 500 error, it's likely that there was a PHP error occurring. If it's pretty repeatable, can you change the following settings in the global configuration area:
* Disable GZip compression (if enabled)
* Set error reporting to "Maximum"

Then, the 500 error will hopefully show any PHP errors that are occurring, which will help us narrow down the problem.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
14 years 7 months ago #14771 by oliverious
Unfortunately I am not getting something useful in the log file. (This could be resulting from my own disability with all this Plesk stuff.)
Anyway, I noticed that the error eventually occurs as a result from my testing, i. e. sometimes it happens that I try to login in Firefox while I have already logged in via Internet Explorer on the same client.
Could you imagine this as the cause of the http 500 error? If so, then it is solved because it is not a productive setting.

By the way, you deliver great support and I will leave a positive message on the Joomla Extensions Directory right now.
The topic has been locked.
Active Subscriptions:

None
14 years 7 months ago #14774 by oliverious
The error does not result from two parallel logins on the same client as I was supposing.

The only information I get on the UI is: "We were unable to retrieve your Facebook account information. Please try again"
The topic has been locked.
Support Specialist
14 years 7 months ago #14794 by alzander
Oliverious,
Sorry for the delay in getting back to you, and thank you so much for the review! We really appreciate it!

As for the PHP error you should see, it likely will be in the PHP log file, but I was mainly talking about seeing it on the site itself.

I just looked at the homepage on your site, and am seeing some oddities. Mainly, in the head section, our JFBConnect javascript code is being included twice. While that really shouldn't cause a problem, it's an indicator that something is going a little strange. Can you try the following things, which I think will likely fix your problem.. but not sure which one will do it:
* Disable caching on your site - Both in the "Global Configuration" area and the "System - Cache" plugin, if you have it enabled.
* Re-arrange the JFBCSystem plugin to be ordered first (lowest number) or last (highest number).

Test in both cases above, and let us know your results. If it's the caching, don't worry, we'll be able to help you re-enable it.. we just need to narrow down the conflict first.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
14 years 7 months ago #14805 by oliverious
Alex, thank you.

After turning off Caching in the Global Configuration area the http 500 error disappeared. Now the message "We were unable to retrieve your Facebook account information. Please try again" is displayed often but from time to time Login with Facebook succeeds. That is looking much better.

The System Cache plugin was already deactivated. And the JFBCSystem plugin also was already ordered first with number 0.

Thus, if you help me with the caching settings again I'll be very happy.


Oliver
The topic has been locked.
Support Specialist
14 years 7 months ago #14818 by alzander
I'm assuming you're using Joomla 1.7. If so, can you tell me what setting the Global Caching was enabled to? There's a few of like optimized, passive, etc.

You shouldn't really be getting the "We were unable to retrieve.." message either, so while things may have improved, something's still not right.

Would you have a problem sending me a set of admin credentials so we can look at the configuration of things on your site? You can private message them to me by clicking the arrow under my picture (<----) and hitting the mail icon. If you don't want to do that, I understand, we'll gladly continue trying to narrow things down however we can.

Thanks,
Alex
The topic has been locked.
Support Specialist
14 years 7 months ago #14862 by alzander
Oliverius,
Thanks for all your patience and help with getting access to your site.

I made a modification to JFBConnect to actually disable SSL verification instead of what we were trying to do before. I'm not sure why your site doesn't like the bundled certificate we supply, but it doesn't. The change I made should get you by for now without any problems, but if you run into anything, let us know.

We'll investigate possible solutions for our next release. Hopefully for now, this will get you going though.

Thanks again,
Alex
The topic has been locked.