Jetpack Not Connecting

I have the same problem, now on 2 websites using JetPack. Both websites use the same website host server.

The “xmlrpc” file is working properly according to the browser test.

Logging into the WordPress account to manage the site from that end, it fails to show the websites and asks to create a WordPress site.

I deactivated the security on both sites and that made no difference.

Once I deactivate or uninstall JetPack, then reactivate/install again, I cannot access the Custom CSS, it is not listed in the WordPress Admin side menu.

Also a quirk, the Custom CSS is not working if I change anything in the Custom CSS window, yet the site still uses the Custom CSS to show the changes. This says I cannot use Custom CSS to make any new changes, it won’t work and won’t show changes in the Customizer.

Test in Another Site
I tested the JetPack connection on a different website, different website host and all is working fine, especially at when in the WordPress account for that site.

• This reply was modified 7 years, 5 months ago by mwarbinek. Reason: more info
• This reply was modified 7 years, 5 months ago by mwarbinek. Reason: More Info
• This reply was modified 7 years, 5 months ago by mwarbinek.
• This reply was modified 7 years, 5 months ago by mwarbinek.

realspear – need to ask, who is your website hosting service for your website?

Mine is “Shaw Hosting” who leases the servers of Hostopia.

—-
and an update on my tests so far,

I deactivated all theme plugins, except Jetpack. That made no difference. I changed themes to the WordPress default theme and that made no difference, JetPack fails to connect.

I did a JetPack debug, but I am not versed that well in PHP so this did not help me understand what is causing this. Basically it said that Jetpack cannot communicate with the site.

• This reply was modified 7 years, 5 months ago by mwarbinek. Reason: updated info

@realspear – What is the error message that you are receiving?

Could you post your site URL here, so I can have a look?

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

@mwarbinek Could you please send us the debug logs via Contact Support and mention this thread URL in your message.

It seems to have been a GoDaddy issue although they claimed it was Jetpack. I accelerated a move to another host (InMotion) and it works fine there. I’m going to take it live there today so it won’t be an issue.

Thanks for taking a look, hopefully it was tied to the host and not JetPack.

Ah, the GoDaddy Dilemma, know it well.

I will send the Deb logs to Support. I will send the logs from both sites.

Thanks

I have been advised, for my issue of JetPack not connecting, was a problem with cURL.

According to JetPack, the plugin uses cURL to make these HTTP requests for a connection and functions for some of its features. Without cURL support, JetPack will fail.

To my dismay, my the website host “Hostopia” disallows cURL commands/calls. I am still dealing with them about this issue because the website is WordPress, of course and WordPress also uses cURL.

WooCommerce plugin uses cURL and likely WordPress themes will use it as well.

So, I may never get this JetPack issue resolved because of the website host, which I have no choice but to stick with because my client’s websites are built there. Unless Jetpack does something with the plugin to bypass cURL and instead, maybe, use HTTP API instead.

Thanks for getting back to us. Sorry to hear that! Unfortunately there’s no plans to move away from using the cURL method for Jetpack at this time, as you’ve mentioned it’s a very popular method used by many WordPress plugins so it’s definitely very restrictive for your host to block this. Hopefully they will be able to make some allowances.