Thread Starter
Lock
(@locksoft)
Update:
If I disable and re-enable JP, it sends me to a page where to approve the connection and it immediately gives this error:
“cURL error 60: SSL: no alternative certificate subject name matches target host name ‘www.lemonskin.net'”
If I click “retry” it sends me back to my website and says everything is ready.
But, still, I keep getting that critical erro in WP Site Health.
Hi there,
It seems that our server cannot verify your server’s SSL certificate, as its chain is incomplete.
Here’s a report that gives some more details:
https://www.ssllabs.com/ssltest/analyze.html?d=io.lemonskin.net&hideResults=on
The problem is that OpenSSL doesn’t recognize your certificate’s Certificate Authority’s (CA) certificate. The URL works in most browsers because they allow for certificate discovery by reading the “Authority Information Access” metadata from the certificate, which contains a URL from which the browser can download the CA’s certificate. OpenSSL does not do this though.
The best solution is if you can configure your webserver to supply the entire SSL certificate chain, rather than just your own certificate. That’s what we do on WordPress.com. Sending the entire chain will also make your sites more compatible with older (and I believe some mobile) browsers.
Thread Starter
Lock
(@locksoft)
Thanks Fresatomica but I still can’t understand the problem.
On my website I’ve two subdomains connected to two WP sites:
io.lemonskin.net
sventrax.lemonskin.net
Both are connected to jetpack for site statistics but only “io” gives me this critical error.
I tried disabling and reenabling the plugin and it takes me to the “authorize plugin” on your website. but it gives me this error:
cURL error 60: SSL: no alternative certificate subject name matches target host name ‘www.lemonskin.net’
If I press “retry” it takes me to my WP dashboard and says everything is configured. But that critical error is still there. 🙁
“sventrax” subdomain, instead, doesn’t report any issue.
I fear there’s something wrong in jetpack and/or Jetpack configuration as the error reports “www.lemonskin.net” and not “io.lemonskin.net”, and the fact the jetpack.com website keeps saying I’m not logged in with my WP.com account, but I am.
-
This reply was modified 5 years, 10 months ago by
Lock.
-
This reply was modified 5 years, 10 months ago by Lock.
You’ll see the problem listed at https://www.ssllabs.com/ssltest/analyze.html?d=io.lemonskin.net&hideResults=on&latest
This is not something we can fix, it will need to be fixed by your hosting provider. You can pass that link along to them for details.
Thread Starter
Lock
(@locksoft)
They made me remove “www” from WP settings (both fields) and everything now seems to work (no more that critical error).
I don’t understand much about it (not my knowledge field) but does a so simple solution makes sense? 🤔
Removing the www cname indeed can make a difference. I’m glad that everything now works for you!
