Sean bit of advice, remove your cPanel username. People use it to hack your cPanel account.

And it looks like a Curl error. Post the error to your host and ask them to

Execute this:

/bin/chmod 755 /etc/pki/tls/certs

Sean, this issue is related to cURLS. We are currently checking the issue.

Most likely the issue was caused by server settings, since Oxwall doesn't interact with those certificates- everything is done via Facebook SDK.

Dragging up an old topic. I am confronted with the same issue. Is there a fix or workaround ? See debug from e500.php

Error details:Type:ExceptionMessage:error setting certificate verify locations: CAfile: /etc/ssl/certs/ca-certificates.crt CApath: noneFile:/data/www/fiat/htdocs/wall/ow_libraries/facebook/base_facebook.phpLine:977

Line is longer and i left out the trace info. 

Already tried Bambi's suggestion, no fix...

What is your software and FB plugin versions?
When did you get this error?

Oxwall 1.7.2. (8520)

Plugin 8320

Servers setup is based on Eisfair with most recent Apache 2 and php versions

ross, any ideas ?

Arno, what are the permissions of this folder: etc/ssl/certs/ ? make sure it is 755

Sorry for the slow reply,

For the regular ftp user, used to install the oxwall site, permissions are 755 and not changable

For the Root user permissions are 755 and changable

I tried 775, no luck so reverted back to 755

Viewed certs configuration, some there but service disabled... ? Enabled certs service, no luck...

Must be doing something terrably wrong...

When i check my certificates, location given is : /usr/local/ssl/certs so should not this be the directory pointed at...?

Arno, we use facebook SDK which on its part uses CURL under SSL which tries to use the certificates, which are on your server and cannot find it. I mean this one: /etc/ssl/certs/ca-certificates.crt

Also the latest FB version is 8520, please update your plugin and try again. If the issue persists, you need to contact your hosting provider to resolve the issue with the certificates on your server. 

Thanks for the reply, i found one ca.cert in the other location and its container is in the disired location. I host my own so i'll have to fix it as well...

If i understand correct i need to have a trusted certificate for the communication in the desired location. It can't be self signed because that would not be trusted...right ?

I'll try to update first and then dive into this certificate jungle..

Thanks sofar, your answers are guiding me through google ;-)

Yes, you need a verified certificate. you can search in google. There are must be the website which sell them. 

Almost there, i found a CA that provides free and truted basic certificates, this should be enough because Facebook has hardly got a policy regardig certificate security level. 

The problem i ran into now is that my domain contains a car brand name. The CA won't give out a certificate because of that... looking for a workaround with an alternative domainname.

As long as the handshake is verified the connect plugin should work.

Yes, i'm going to get a certificate... the certmaster with the CA is going to make an exception because he remembers the specific type of car the site is about... more to follow. If i can spare the time i'll make a howto for the self hosters among us, of course after i get connect up and running...

Ross, thanks for the support, it's going to be ok now !