This message appears because your site is not yet connected to your WordPress.com account. You should be able to connect your site to WordPress.com by clicking on the Connect button you’ll find in the Jetpack > Dashboard menu in your dashboard.
Could you let me know where you found the link to this page, or walk me through the steps you followed to get this error?
Thanks!
Thread Starter
bahus
(@bahus)
This message appears after clicking on the connect button. Link to /wp-admin/admin.php?page=jetpack&action=register&_wpnonce=c04eac724a&from=banner-44-slide-1 connect button to redirect to a page /wp-admin/admin.php?page=jetpack_modules with the message to the specified message.
Previously, when you press the connect button on the login form was wordpress.com. Now this is not happening. Reinstalling the plugin does not solve the problem.
This problem appeared after the transfer of the site from http to https protocol.
-
This reply was modified 7 years, 3 months ago by
bahus.
That’s interesting, thanks for the extra details! It sounds like you found a bug.
I can’t reproduce the problem right now, but it may be limited to your site. Would you mind contacting us through this form and mention this thread, so we can run some more tests with you on your site?
Thanks!
I am having a similar issue. When I go to the Jetpack page in my admin panel there is a red message which says:
Error Details: The Jetpack server was unable to communicate with your site https://boxtoninc.com [IXR -32300: transport error: http_request_failed cURL error 60: SSL certificate problem: unable to get local issuer certificate]
If I try and hit connect, it redirects me to: /wp-admin/&from=landing-page-top
which is a 404 error.
I recently installed SSL on my site as well and went from http to https
@jpcaprara You seem to be using a self-signed SSL certificate on your site, making it impossible for your site to communicate with WordPress.com. It’s actually also an issue in most modern browsers; here is what I see when I try to access your site, for example:
http://i.wpne.ws/infI
Could you try to install a signed SSL certificate for your domain? That should solve the issue. If you need some help with this, your hosting provider should be able to help.
Thread Starter
bahus
(@bahus)
The plugin uses xmlrpc.php file?
@bahus Yes, Jetpack relies on the XML-RPC file to communicate with WordPress.com. You’ll only be able to use the plugin if your site’s XML-RPC file is publicly accessible.
Thread Starter
bahus
(@bahus)
Everything was easy to banality. On the default hosting xmlrpc.php file is locked, as through this file often hack wordpress. 🙂 At least strange decision.
I’m getting this too. I have a VPS running Let’s Encrypt but, for some reason, I get the https version of the site when viewing front end validating OK. When I’m in the dashboard, the https is crossed out in the browser address bar (invalid). So the certificate seems fine when you are viewing the site from the front end, but not the dashboard (backend). This only started happening this week.
I’m out of knowledge on this one unfortunately. I don’t think my problem is XMLRPC related – Let’s Encrypt seems to be securing the public part of the website correctly, but not the wp-admin side!!
http://www.scentperfique.com
Let’s Encrypt seems to be securing the public part of the website correctly, but not the wp-admin side!!
@zincweb This issue seems to be quite different from the one reported in this thread. I would recommend getting in touch with your hosting provider if you still experience issues.
Actually, I don’t have this quite right. Upon further investigation, it seems that Let’s Encrypt is working fine. I get the valid padlock when logged into the back end of WordPress.
However, when going through the connection process to Jetpack, authorization, etc, Jetpack then passes me back to the dashboard. From then on, the padlock is broken (the https is crossed out in the url).
It’s very strange. I administer the vps myself and the server is fine and the certificate for Let’s Encrypt is up to date.
It’s the process of being passed back to the dashboard from Jetpack which throws the SSL error.
When you get back to your dashboard, are you on the correct domain?
Could you contact us via this form, so we can run some more tests with you?
Thanks!
