JFBConnect Current Version Installed and Joomla Current Giving me 502

Question: would slow MySQL queries cause this related to communications from jfb to google sclogin ? I understand it's communications between to servers.

I am no longer getting slow queries so is that a possibility that slow queries might be causing the issue? My database is very big.

There shouldn't be any slow queries caused by JFBConnect, especially on common page loads. As noted, there's very little that JFBConnect 'does', especially concerning the database, when the page is loaded. Our heavy lifting is normally done during the actual authentication process. We also have a caching layer in our extension which saves a lot of the heavy processing tasks to disk to speed up page load times overall. In the distant past, JFBConnect was considerably slower. We've gone to great pains to make it as efficient as possible. All of our tables use primary keys for almost all lookups and there shouldn't be any slow queries caused by JFBConnect directly.

There are ways to enable the 'slow query' log for MySQL, which may help you narrow down exactly which queries are slow. Additionally, as asked above, have you checked the PHP error logs? From a cursory investigation of 502 gateway errors using nginx and assuming that your host/server IP is 67.230.173.66 (from your log above), it does seem like something isn't responding. That could be a slow query, a PHP error or something else in the stack that's preventing the page from rendering. Again, I didn't see it yesterday with some quick testing, so:
* Is there a PHP error in the logs?
* Is there anything specific to do to recreate the problem? If so, what steps should we take?
* Does it happen more around a certain time of day (the Apache access logs should be able to help answer this).

Any other details you can provide on how the problem is happening will help. However, please understand that I'm not a server admin and this seems like a much lower-level issue than JFBConnect or even Joomla itself though, which limits my ability to help.

Thanks,
Alex

I was just asking if that would effect jfbconnect, the slow queries?

It really shouldn't. We don't have any timeouts built-in to JFBConnect. During the authentication process, a severe slow query may cause an issue since there's some timing constraints (measured in minutes though) where tokens provided by the social network must be used. On standard page loads though, no, a slow query would just slow the page down and shouldn't cause an issue directly within JFBConnect.

My php errors are above in my previous messages so doesn't look like an error on any php code but remote disconnect.

The error messages from your 2nd or 3rd post aren't from the PHP error log. Those look like the nginx or apache error logs, which are different. Since the server is getting disconnected, it may be that PHP has encountered a fatal error and simply isn't responding anymore for that page load. That's where viewing the PHP error log may narrow down the cause quickly.

Thanks,
Alex

I'm glad to hear it sounds like you found the problem, but I'm not quite clear on your solution or what the ultimate issue was.

First, we are generally regarded very highly for our support. In all of your posts above, we've been responding within a few hours and there doesn't seem to be any attempts to blow you off, as many other extension developers try to do. We certainly tried to help, but the issue didn't sound related directly to JFBConnect.

As to your issue, there are thousands of users with JFBConnect that *aren't* experiencing slowdowns like you mention. I'm not sure what the cause was (or is). From your message above:

so I just remove JFB and then after running a few tests I reinstalled it and so far no issues.

So, after you uninstalled JFBConnect and re-installed it, the performance issue was solved? If so, that sounds like there was an installation error with the original attempt to get JFBConnect running a few months ago. I don't know what that was, and I'm assuming you don't know if there were any install issues at that time.

If things are working correctly now with the same code though, it would seem to indicate the code itself is ok.

Either way, if you can give us more information about how it's performing now vs before and any other differences that may have been made, we'll gladly help. Of course, if you do run into issues with JFBConnect again, let us know and we'll continue to investigate and help however we can.

Thanks,
Alex