There's a few things to check and some suggestions that should fix things. First, please check to see if the following file exists on your server:
/home/ohiovars/public_html/components/com_jfbconnect/includes/jfbconnect.js
If so, that means that JCH Optimize is having issues with the ?v=6 at the end. That ?v=6 is meant to prevent browsers from caching the file when you upgrade JFBConnect (so that the older version of the file isn't used. We haven't seen JCH Optimize have this issue before though, and we know of many sites that use JCH.
What I'd recommend is:
* Checking your settings in JCH. I haven't used it in a long time, but there may be a setting for query strings in files to ignore, or something like that.
* Contacting the JCH Optimize developers to see if they have any suggestions as to why the ?v=6 isn't being stripped from the filename properly to get the actual filename on your server.
Finally, you should be able to alter JFBConnect to remove the ?v=6 from the inclusion. However, this is something that will have to be done after every update, so it's not the most ideal solution. To do so, edit the /components/com_jfbconnect/libraries/provider/facebook.php file. In there, search for "?v=6" and you'll find a line like:
$doc->addScript(JURI::base(true) . '/components/com_jfbconnect/includes/jfbconnect.js?v=6');
Simply update that to:
$doc->addScript(JURI::base(true) . '/components/com_jfbconnect/includes/jfbconnect.js');
I hope that helps, but if not, let us know.
Thanks,
Alex