makjsnsakh

Thanks Francesco! I did as you said and the error was solved (enabled nd_mysqli, the mysqli was already disabled).
I was using PHP 7 since months, so I don’t know why the error happened (today) in the first place?

Richard, thank you very much!

Your answer not only helped solving the problem, but it helped me understanding many new important things. The hosting provider kindly solved the problem after forwarding your reply, but they told me the self-signed certificates will stay (all websites in this shared server inherit the certificate information from the first website, i.e. when you did SSSLabs test it was a different website and now another one).

For now, the most important thing is that Jetpack connected with wordpress.com the proper way for the first time: now the debugging page shows “Your Jetpack setup looks a-okay!” (Before that although Jetpack worked fine, the debugging page always showed communication warnings). I hope it will stay functioning like this until I decide what to do with this self-signed certificate.

For people having the same problems, my case demonstrated that when the debugger shows a problem it means there is a problem (I am talking here about the warning mentioned in paragraph 3 in OP that was there since almost a year). Another recent support thread entitled ‘Seems to work fine, but Jetpack Debugger shows a problem’ apparently has the same or similar problem.

p.s. when I wrote this reply I decided to do some digging about this self-signed certificate, because it did not make sense.

I found that the origin of the problem is cPanel forcing these self-signed certificates on users. Now this is not good at all (see this support threat for more information about this problem.

• This reply was modified 7 years, 3 months ago by makjsnsakh.