Yeah, I've been trying to test curl w/https (in general, not Facebook) from the command prompt and haven't seen any errors. So, it's not like my entire CA file is missing.
What I haven't come up with yet is a valid Facebook URL to test w/curl from the command prompt. The next steps I can think of both seem kind of hard. Either:
* Dig into the code and determine the exact call IPS is making and try it from curl
* Somehow sniff the results of IPS's call and see what's actually happening with it
So, I was hoping someone would know more than I do. But, I should be able to accomplish one of those...
I had actually started moving in the direction of supporting https (thought hadn't flipped logins over https on yet), but disabled https altogether while troubleshooting this problem to make sure it wasn't a problem fetching an https resource from my site.
I've searched the forum a bit and haven't seen this exact problem. My Facebook Connect stopped working. Seems to be SSL-related. The error logged by Invision is:
Problem with the SSL CA cert (path? access rights?)
Google tells me that's an error curl sometimes throws when there's a bad certificate chain. The ca-bundle and ca-bundle.trust in /etc/ssl/certs are those that come from yum (I'm on centos) and haven't been modified recently; I haven't come up with any curl test that shows any certificate troubles loading remote https sites.