I'll be moving this to the JLinked / Joomla 2.5 support area after I post this. I'm assuming you are working with those versions and just accidentally posted in the JFBConnect forums. If you are using JFBConnect, let us know.
As for your issue, can you let us know when you get that error? Is it when you install the extension, configure something, or simply click the Login with LinkedIn button? Is there a page we can look at?
Finally, that message is obviously very vague. Here are some things you can do to help narrow down the actual cause:
* Disable any JLinked Profile plugins you aren't using. Specifically, if you have the JLinked Profiles - Community Builder plugin enabled, but don't have Community Builder, disable that plugin. Do that for all profile plugins you shouldn't need enabled.
* If that doesn't work, go into the Joomla Global Config area. Turn off GZip compression and set Error Reporting to 'Maximum'. Recreate the problem and see if a better, more descript, error message appears. If so, let us know what it is.
I have followed the instructions you sent through but as I am not a developer there are certain things I have limitations on. One of them is that I don't know where the error log is. Could you also let me know which plug-ins and modules should be installed for only the log in functionality. The ones you mentioned are not activated but I just want to check I just have the minimum on.
Whilst I do have jomsocial installed I have disabled it as I need some developer intervention for it to work with the set up I have.
You shouldn't need to know where your error log is, in most cases. Simply following the steps in the Global Configuration will enable error messages to show on the front-end. So, instead of the generic message you got, you'll (hopefully) see a much more descriptive error which can help us narrow down the problem.
As for the basic login functionality, you should have the following plugins enabled:
* JLinked - Authentication
* JLinked - System
* JLinked - User
The SCLogin module is the easiest way to add a Login with LinkedIn button, but isn't required as there are other ways to display that button.
The Content plugin and Profile plugins are not required for login/registration. The profiles can help with integration with other extensions, but aren't required for creating the basic/standard Joomla user.
Hope that helps. If you get a better error, or no error, definitely let us know!
I can't actually see the Login with LinkedIn button anywhere. Where should I be looking on those pages? Sometimes I go very blind looking at other user's pages.
If you want to (or can) send me admin credentials to the site, we'll gladly look into the issue more thoroughly. You can Private Message them to me by clicking the arrow under my avatar (<
) and hitting the mail icon.
If you can't, we'll gladly test on the front-end and see what we can determine from there.. once we see the login button.
Thanks for updating our credentials. Using extPlorer, we were able to test a few changes and really narrow things down. The issue you're having is one we haven't seen before, but after a lot of research, we think we know the cause.
Basically, JLinked needs to do a lot of communication with LinkedIn.com when a user is logging in. This is all done over an SSL (encrypted) connection for obvious security reasons. From the best we can tell from the error you are receiving, your server has outbound connections to port 443 disabled. Therefore, JLinked can't make the outgoing connection and the server is throwing a hard error for us even trying.
Can you contact your hosting company or technical support to see if they can open up port 443 for outgoing connections? If that doesn't fix the problem, we'll need to get access to the PHP error logs which should state the exact error that's occuring on the server and causing the 500 error. So, when you contact them, you may want to ask them for the log (or for them to look for any fatal errors they see).
Once that's resolved, I think you should be up and running. If not though, we'll gladly help however we can to keep debugging the issue.