It seems there is a problem with your SSL certificate configuration. I cannot even access your site at the moment; I receive the following error:
http://i.wpne.ws/SksI
I would suggest that you contact your hosting provider and ask them to help you fix the issues you’re having with your SSL certificate.
Thanks!
I’m facing the same issue as well, so let me add a few more details.
I believe both Evan and I have a free OpenShift plan, which provides a shared SSL certificate for *.rhcloud.com. They do allow custom DNS CNAME records so that you can map your own domain to your OpenShift site, which is of the form appname-namespacename.rhcloud.com. I think both of us have mapped our own domains to our OpenShift websites, and hence the SSL certificate error.
Is there any possible workaround for this? OpenShift is amazing for small to midsize-blog owners like us.
You could disable the HTTPS check by adding the following line to your site’s wp-config.php file, right before /* That's all, stop editing! Happy blogging. */:
define( 'JETPACK_CLIENT__HTTPS', 'NEVER' );
Jetpack will then stop to try to use HTTPS when connecting to WordPress.com.
I’ve added this now, but I still get the same error. Can I help with more data?
Can you add the line to your site again, and then use Jetpack’s Debugger module to send us some more information about your site?
1) Go to the Jetpack page in your dashboard.
2) Click on the Debug link appearing at the bottom of the page.
3) Click the link that says “click here to contact Jetpack support.”
4) Fill in the description box and your name and email address.
5) Click the “Contact Support” button.
Thanks!
I am facing the same problem. And even after adding the HTTPS check, the problem persists.
I have sent the debug information.
I noticed the following in the debug message – [body] => {“error”:”Communication error”,”error_description”:”We were unable to make an XML-RPC request to your website. Please make sure that XML-RPC is turned on and that Jetpack is installed, activated and connected with your WordPress.com account.”}
But I was able to access the XML-RPC PHP file on my blog (with both HTTP and HTTPS).
@ssriram75 If you’ve sent us the debug information, we’ll get back to you very soon!
Sye
(@psychosherry)
Okay, I was able to fix the problem. I logged into my Openshift WordPress app using SSH, and then modified my wp-config.php.
By default, Openshift forces SSL on wp-admin. So just comment out this line in your wp-config.php:
define('FORCE_SSL_ADMIN', true);
BTW your WP app is located at:
/var/lib/openshift/<app-id>/app-root/repo/php
Interesting. Would that change cause the admin section to run under HTTP then?
Ah, in my case though, I’m afraid I cannot run the admin section without HTTPS just for a plugin. Congratulations on getting yours fixed!
