Your site could not connect to WordPress.com via HTTPS. | ww.wp.xz.cn

Resolved mp0001
(@mp0001)

1 year, 6 months ago

cURL error 60: Peer’s Certificate issuer is not recognized.

JetPack has been working for the last 2 years with no problems, even yesterday it was working. As of today I’m getting the above error. I’ve done the usual Google searches and tried seveal things and still no luck.

Tried a different WordPress site, on a differnet server and getting same results.

Have a Certbot SSL on the server, and traffic via Cloudfare with SSL.

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

ksseroka
(@ksseroka)

1 year, 6 months ago

I have the same (or just very similar issue) – Jetpack stats stopped working even though I didn’t do any changes and automated updates are turned off. I contacted hosting provider to check the certificate, but it’s ok.

That’s what I see in Jetpack debugger:

HTTPS: cURL error 60: SSL certificate problem: unable to get local issuer certificate

Advanced debugger (fragment):

TEST RESULTS:
HTTP: PASS
HTTPS: FAIL
IDENTITY_CRISIS: PASS
SELF: FAIL

Plugin Support lastsplash (a11n)
(@lastsplash)

1 year, 6 months ago

Hi @mp0001 –

Could you please post your site URL here so that we can have a look?

If you want it to remain private, you can also contact us via this contact form:

https://jetpack.com/contact-support/?rel=support&hpi=1

If you choose to reach out directly, please include a link to this thread.

Thanks!

Plugin Support lastsplash (a11n)
(@lastsplash)

1 year, 6 months ago

Hi @ksseroka

Could you please start your own thread, as per the Forum Welcome guidelines

https://ww.wp.xz.cn/support/plugin/jetpack#new-post

Please include your site’s URL to help us investigate.

Thank you!

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

The topic ‘Your site could not connect to WordPress.com via HTTPS.’ is closed to new replies.

3 replies
3 participants
Last reply from: lastsplash (a11n)
Last activity: 1 year, 6 months ago
Status: resolved