Error: SSL certificate problem

Resolved crxed
(@crxed)

7 months, 1 week ago

Since today I get the follow error

2025-08-24 13:53:16: The social post ID: 6242 failed to post. Error: SSL certificate problem: unable to get local issuer certificate

Tried to remove the Facebook service and add it again, but now adding is not possible anymore either, throwing the same SSL error.

Any help?

It was working fine until last week and I have not changed anything on my site.

Viewing 11 replies - 1 through 11 (of 11 total)

petecarr
(@petecarr)

7 months, 1 week ago
I’m also getting the same message in my logs. I can’t refresh anything via Facebook. It was also fine last week.
```
2025-08-27 10:21:26: The social post ID: 229804 failed to post. Error: SSL certificate problem: unable to get local issuer certificate
2025-08-27 10:21:26: TRANSITION 229804 (  social_post  ): future => publish
```
Plugin Support Val Meow
(@valwa)

7 months ago

Hey @crxed! 👋

Unfortunately, this isn’t something caused by the plugin, so I won’t be able to help directly. An SSL error is almost always the result of the server not providing an intermediate certificate during the TLS handshake. Running the SSL Labs test against the server will confirm if that’s the case.

This can happen either because of an issue with your server or with the API server you’re trying to use.

🔗 SSL Labs Test

Thread Starter crxed
(@crxed)

7 months ago

My server is returning Grade A in the SSL report

Thread Starter crxed
(@crxed)

6 months, 3 weeks ago

@valwa I got a request question from my host:

Which User Agent is used to use the Social App?
They want to know, in case they might be blocking it.

theaaronp
(@theaaronp)

6 months, 2 weeks ago

So my replies have been deleted. I just solved the problem. And now they’re being deleted. Take some accountability ffs.

Thread Starter crxed
(@crxed)

6 months, 2 weeks ago

What happened to the solution that was posted here?

Why was it deleted???

theaaronp
(@theaaronp)

6 months, 2 weeks ago

Seems like they don’t like the fact I just pointed out to them that this is a them issue. They haven’t kept up with the latest Facebook SDK. I solved it by changing a couple of lines of code after weeks of them telling me I was wrong and it was my server.

Thread Starter crxed
(@crxed)

6 months, 2 weeks ago

I got your info. Is this correct?

Go here:

/wp-content/plugins/social-engine-pro/vendor/facebook/graph-sdk/src/Facebook/HttpClients/FacebookCurlHttpClient.php

Open:

FacebookCurlHttpClient.php

Change:

CURLOPT_SSL_VERIFYHOST => 2,CURLOPT_SSL_VERIFYPEER => true,CURLOPT_CAINFO => *DIR* . ‘/certs/DigiCertHighAssuranceEVRootCA.pem’,

To:

CURLOPT_SSL_VERIFYHOST => 2,CURLOPT_SSL_VERIFYPEER => true,

That means to remove the /certs DIR part?

theaaronp
(@theaaronp)

6 months, 2 weeks ago

CURLOPT_SSL_VERIFYHOST => 2, CURLOPT_SSL_VERIFYPEER => true, CURLOPT_CAINFO => DIR . '/certs/DigiCertHighAssuranceEVRootCA.pem',

CHANGE TO

CURLOPT_SSL_VERIFYHOST => 2, CURLOPT_SSL_VERIFYPEER => true,

Thread Starter crxed
(@crxed)

6 months, 2 weeks ago

@theaaronp It immediately started working after that change, thanks a lot!!

@valwa time to update the plugin

theaaronp
(@theaaronp)

6 months, 2 weeks ago

@crxed glad it worked for you, we’ve been testing all day and it seems to be working well. This is a fix in the short term, there might be other changes in the latest SDK that need to be reflected in the plugin but nothing that will stop you from scheduling.

@valwa credit for the fix please 🙂