We're in the site now and trying to narrow things down. I also downloaded the Massive Scale patch from the /root directory, as I'd like to see what's happening there. I hope that's ok with you, if not, let me know.
Unfortunately, I've been trying for about an hour and haven't been able to recreate the 500 error once. It was very easy to create a day or so ago. I'm assuming you didn't change anything. We'll test again in a little while to see if it starts up again. If you did change anything, let me know.
For sessions, I knew what you meant above about just being guest sessions. The problem is that JFBConnect uses guest sessions to store information about the user as they go through different login/registration paths. For instance, if you have the "Registration Component" set to "EasySocial", this is what happens:
* User clicks "Login with xyz"
* JFBConnect stores a session variable for that guest user stating that they were authenticating with Facebook, Google or Twitter
* JFBConnect redirects the user to the standard EasySocial registration page
* After the user goes through EasySocial and registers, JFBConnect is notified that a new user has been created
* At that point, we check if the session var above is set.. if so, we 'connect' the newly created user from EasySocial to their Facebook, Google, or Twitter account.
If that guest session variable doesn't exist, the connection won't be made.
That's one example of *many* cases where we use session variables to track a user from before they login/register until after.
Again, I'm looking into the cause of the problems, but i'm running into weird errors throughout the admin area of your site. Hopefully you can help me understand what may be happening:
* I can't access the Joomla Global Configuration area. It's a white page with some links. My guess is there's a PHP error on the page, but error reporting is off, so I can't see it.
* If I try to go to the JFBConnect -> Configuration or -> Profiles area, I get:
502 Bad Gateway
nginx/1.1.19
Social and some other configuration areas work fine.
* The version check at the bottom of the JFBConnect pages reads "Version: ", which means that JFBConnect can't read the XML file from it's own directory.
All of the above are likely due to read permission issues where JFBConnect can't read the XML files for the setup of those pages. Not sure why they would be incorrect though.
Miscellaneous Observations
Your site allows access from both www and non-www. I'd recommend setting up a redirect from www to non-www or the other way around. It's better for search engines and general accessibility.
I'll keep you posted on what I find as I test later.
Thanks,
Alex