• Resolved jfambrini

    (@jfambrini)


    Great plugin guys. Here is the problem I’m having:

    • I deactivated Jetpack now when I try to re-activate it I get the following error: Error Details: The Jetpack server could not communicate with your site’s XML-RPC URL. If you have the W3 Total Cache plugin installed, deactivate W3 Total Cache, try to Connect to WordPress.com again, reactivate W3 Total Cache, then clear W3 Total Cache’s cache.
    • The caching plugin I use is LiteSpeed Cache and I deactivated it and still having this problem

    The reason I deactivated Jetpack is because one of the forum greats helped me with a problem where my posts were not displaying images. He asked me to disable “Enable Site Accelerator” so this is what I did:

    • I tried disabling this accelerator and I got the following error: “Giving me “Error updating settings. Cookie nonce is invalid (Status 403)” Error.”
    • I deactivated Jetpack and the new posts started loading images
    • I now re-activated Jetpack and am receiving the error when I click on “Set up Jetpack

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support supernovia

    (@supernovia)

    Hi @jfambrini, are you using any other caching plugins (like the accelerator) that you could temporarily disable, then reactivate and clear the same way we suggest for W3 Total Cache?

    Also, when did this issue start?

    Thread Starter jfambrini

    (@jfambrini)

    Thanks @supernovia. As I mentioned I use LiteSpeed Cache and it has been disabled and I’m still having the problem. The problem started when I created new posts after enabling of image accelerator.

    Thread Starter jfambrini

    (@jfambrini)

    Now getting “cURL error 7: Failed to connect to jetpack.wordpress.com port 443: Connection timed out”

    Thread Starter jfambrini

    (@jfambrini)

    And this is the detail of the error:

    Outbound HTTPS not working
    Your site could not connect to WordPress.com via HTTPS. This could be due to any number of reasons, including faulty SSL certificates, misconfigured or missing SSL libraries, or network issues.

    Jetpack will re-test for HTTPS support once a day, but you can click here to try again immediately”

    When I try https://toyota-dealer.org/wp1 I’m able to log in fine so know that https is working.

    Plugin Contributor James Huff

    (@macmanx)

    Volunteer Moderator

    Yep, inbound HTTPS is working, but outbound may be broken, and that’s something your hosting provider needs to correct.

    Does the Health Check plugin report similar? https://wordpress.org/plugins/health-check/

    Thread Starter jfambrini

    (@jfambrini)

    Thanks @macmanx. My host whitelisted their IPs as shown at https://jetpack.com/support/hosting-faq/ and now not getting https access error but this error:

    Error Details: The Jetpack server could not communicate with your site’s XML-RPC URL. If you have the W3 Total Cache plugin installed, deactivate W3 Total Cache, try to Connect to WordPress.com again, reactivate W3 Total Cache, then clear W3 Total Cache’s cache.

    As mentioned earlier, I have disabled the Litespeed Cache, I don’t have any other caching plugin.

    Plugin Contributor James Huff

    (@macmanx)

    Volunteer Moderator

    It’s possible that we’re being blocked by Cloudflare: https://toyota-dealer.org/wp1/xmlrpc.php?for=jetpack

    Please set your Cloudflare security to either Low or Off to see if that makes any difference.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Jetpack’ is closed to new replies.