Based on the Trac link you sent, it does appear that the iOS developers do have it filed in Trac and it will probably be addressed at a later date. It’s hard to say when that might happen though. If it’s an issue that’s an edge case, it’s a possibility that it could wait longer than other priorities.
I’m not sure about the Jetpack servers, but I will try to see what I can find out about that.
I can speak for Jetpack.
It was a design decision to not allow self-signed certificates. We have since reevaluated that decision. Now it’s a bug.
Unfortunately, I don’t have an ETA on when that bug will be fixed for Jetpack.
Ahh, many thanks for clearing that up!
It’s coming 🙂 http://ios.trac.wordpress.org/changeset/3700
Now, it’s not possible (or I haven’t found out how) to permanently trust a ssl certificate from the app, so it’ll prompt about it every time it relaunches. But at least the site can be used
I have a site running on a virtualmin server with a valid ssl certificate (no browser errors at all) and Jetpack is still throwing Error Details: The Jetpack server was unable to communicate with your site [IXR -32300: transport error: http_request_failed SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed]
The certificate is fine – GoDaddy cert correctly installed and verifiable.
I have similar configurations on other cPanel based servers which run on SSL and connect to jetpack without problem. Is anyone else experiencing this certificate issue with Jetpack running on a virtualmin based system?
Joe,
Without a URL, I can’t say for certain, but it’s probably because your server is sending only your certificate, not the intermediary ones between yours and the root of the certificate chain.
GoDaddy does not sign the certificates with their root certifcate; they sign them with an intermediate certificate which you must configure your webserver to send alongside your certificate.
Your site is accessible in your browser without SSL warnings because your browser has the GoDaddy intermediate certificate installed by default. Your site is not accessible by our Jetpack servers because OpenSSL (the SSL library we and many others use) does not include these sorts of intermediate certificates.
If you compare the certificate information you send to what we send on https://wordpress.com/, you can see we send the intermediate certificates as well (we are both using GoDaddy).
It’s not just a Jetpack problem. Not sending the intermediate certificates almost certainly breaks other things besides OpenSSL (older browsers, some mobile devices, etc.).
Assuming my guess about the problem is correct, if you configure your webserver to send the intermediate certificates as well, everything should start working.
If you’re using Apache as your webserver, here’s a FAQ about SSL verification and intermediate certificates: http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#gid
i, too, have this issue. running on a VPS with parrallels plesk panel. the domain actually has a proper ssl certificate (signed by alpha ssl) but there’s one that parallels have signed for the raw IP.
my error is as follows
Your website needs to be publicly accessible to use Jetpack: site_inaccessible
and then
Error Details: The Jetpack server was unable to communicate with your site [IXR -32300: transport error: http_request_failed SSL certificate problem: unable to get local issuer certificate]
I have started to receive this error as well, after successfully connecting over 120 sites on the same network, with the same account.
Your website needs to be publicly accessible to use Jetpack: site_inaccessible
Error Details: The Jetpack server was unable to communicate with your site [IXR -32300: transport error: http_request_failed SSL certificate problem: unable to get local issuer certificate]
The certificate is issued by InCommon CA (the certificate authority for Internet2 members) for *.princeton.edu. You can see the details of the cert at https://blogs.princeton.edu
@berkayozcan Can you please try installing the Jetpack Compatibility Plugin so we can see some additional information from your site?
1) Download the plugin from http://plugins.svn.wordpress.org/jetpack/branches/jetpack-compatibility-test.zip
2) Upload the plugin to your site via Dashboard -> Plugins -> Add New.
3) Activate the plugin and go to Plugins -> Jetpack Compatibility Test.
4) Click the “Select All” button.
5) Send us the test results via this contact form:
http://en.support.wordpress.com/contact/?jetpack=needs-service
Thanks!
Thank you for your interes Jeremy.
I have sent the test result via contact form.
Thanks Berkayozcan, I replied by email!
Richard, lots of thanks for your help.
After receiving your email, i understood the problem :). I did not make your advises since I have just simply upgrade the PHP version of my server from 5.2 to 5.3.
There is not any problem for now.
