Super disappointed with JFBconnect today

If Facebook works now, it indicates something was wrong with the app settings. It's tough to know what if you simply deleted and replaced, but I'm glad that's working.

As for Google+ and Twitter, nothing changed in JFBConnect obviously. It sounds like things changed on the server. JFBConnect has been tested with PHP7 and definitely works with https, but it sounds like there's some sort of conflict there. There's a few possibilities, but no magic bullets I can provide by only seeing the front-end
* If you have any Joomla firewall/security extensions, please try disabling them (temporarily) to test
* Is your server running behind any kind of proxy? We recently ran into an issue with Twitter where the responses from their API were being incorrectly altered when behind a proxy. We have a fix for this ready for the next release planned.
* Can you double-check your server time. Please make sure it is very accurate. Social authentication relies on accurate timestamps to prevent spoofing of data. If your server timestamp is incorrect, some social networks will deny authentication attempts.
* Go to the Autotune -> Site Check section and make sure the PHP and cURL portions have green checkmarks

I hope that helps get you started, but if not, let us know and we'll help investigate however we can.

Thanks,
Alex

Regarding the Twitter error, the 3 most common causes of that issue are:
1) Your Twitter Application wasn't set up properly
2) You didn't copy the API Key and Secret properly to JFBConnect
3) Your server time is incorrect

Please double check #1 & 2 and go through our Twitter Application Setup guide for Joomla again.

Also, JFBConnect version 7.0.1 will have a fix for Twitter if you're behind a proxy (but unsure as you didn't provide an answer for Alex's above questions). After verifying the above are not the issue, you could try the following workaround in /components/com_jfbconnect/libraries/joomla/http/transport/curl.php . Around line 167, you'll see:Right *before* that line, add the following lines:
Let us know what you find out for trying the above suggestions.

-Melissa

After a bit of hair pulling and some code tweaks I have gotten it to work

Are these the above code changes that I mentioned, or was there something else required?

There is one thing you need to do however. The LinkedIn setup is out of date. They have recently changed their website. The Oauth2 codes are no longer entered as you have them described. Plus they have moved the Javascript off to a setting of it's own.

Thanks for letting us know. I will be working on updating documentation this week and already had plans on checking the application setup guides to make sure they are up-to-date.

-Melissa