Topic-icon JFBConnect Remote Error Check Facebook SSL Handshake failure

Active Subscriptions:

None

JFBConnect Remote Error Check
Checks performed on: site.com/
Error: Uh oh! We could not fetch that page.
error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure



If you are having Facebook authentication issues after correcting any warnings and errors above, please ensure your Facebook Application is "Live". You can enable that setting by:

Going to the Facebook Application Area
Go to the the "Status & Review" section
Make sure the top switch for "Do you want to make this app and all its live features available to the general public?" is set to YES.


I have recompiled curl to use gnutls instead of openssl. I'm not sure what else to do. I'm running FreeBSD, nginx, curl.

I'm using a Comodo SSL and aside from specific pages, all of my browsers register it on the root level as okay.
The topic has been locked.
Support Specialist
11 years 5 months ago #50212 by mel
I was able to run a few remote error checks with passing results on your page, without getting the error above. But it looks like your firewall kicked in and I am now receiving the following error:

Error: Could not fetch page. Server returned:
Error Code: 403 - Forbidden. Is a firewall enabled?


I also manually looked at your page and found no errors that the error checker would have caught. If you still would like to run the tool, please disable your firewalls including any Joomla security extensions. But unless you find that something is not functioning properly on your site for JFBConnect, or you aren't able to use the rest of the autotune configuration tool, this shouldn't be necessary currently.

-Melissa
The topic has been locked.
Active Subscriptions:

None
11 years 5 months ago #50214 by camp
Melissa,

Thank you for your prompt response. I value the support here at SourceCoast.

After much crawling around the web I noticed that my curl configuration from my package manager offered SSLv3 which is deprecated and apparently was highly vulnerable during the poodle exploit.

I'm a bit scatter-brained at the moment after covering other areas such as checking my SSL cert with OSCP stapling, but for SSL it seems (if this could help anyone else in the future) that TLS is all you want for protocols and RC4 is a no-no as it is a weak cipher.

My search began at : POODLE issue (CVE-2014-3566)
The topic has been locked.
Support Specialist
We're glad to hear you got things going. Keeping a server up to date and as least vulnerable as possible is always a taxing job.

As for the different SSL/TSL issues you found, those shouldn't have been causing the remote error check failures you're encountering. It's always good to patch out of date features and lock things down as best as you can, but I don't think those things will fix the error checker.

However, as Melissa mentioned, she already checked your page for all the things that the Error Checker would have found and your site looks fine. I'd keep going with configuring features. If you run into any other issues, just let us know and we'll gladly help however we can.

Thanks,
Alex
The topic has been locked.