Loading https

Kray,
Unfortunately, Facebook doesn't load all of it's assets over an SSL connection. While JFBConnect will load the main Javascript library over SSL if the current page is encrypted, if you use the social widgets from Facebook (Like button, comment box, Fan Box, etc), many of those will not fully load over SSL. When they are rendered on the page, they load an iFrame to Facebook's servers. That iFrame will then load user avatars and some other graphics over a non-SSL connection.

The reason this is done is because SSL requests can't be cached. For the heavy load Facebook obviously has, they have made the choice not to load that content over an SSL connection. Because of the iFrame method they are using, we have -no- control over what's loaded and they have no method to force SSL on some of those assets.

There are some widgets that likely can work over SSL without the mixed content warning, but not all of them. You may need to test what does and doesn't work and decide if the warning message is worth it or not.

Hope that explains, and sorry for the inconvenience. This is a common question, and big annoyance. We definitely hope Facebook allows SSL asset loading in the future, but we haven't heard any rumblings about that coming soon.

Thanks,
Alex

If you're just using the Login button, no Like buttons or other 'widgets', that shouldn't trigger the mixed-mode content warnings. The login functionality is capable of running in SSL mode without those warnings.

Can you post a page that we can see with the problem? We should be able to help narrow down where the issue lies.

Thanks,
Alex

Kray,
If you use Google Chrome, you can open your page and then open the Developer Tools (CNTRL-Shift-I), and then click the "Network" icon. On there, it will show all content that was loaded to render the page. The Facebook content seems to be coming over https properly. The content from b1.adbrite.com/iads is not. While the Javascript to load the ads is loaded over https, the images that the Javascript is loading is over http only.

I believe that's the issue. Try disabling (temporarily) those ads and see if the warning goes away. If not, check the other images and narrow things down. If you find something from Facebook, definitely let us know.

Hope that helps,
Alex