• Resolved ramyibrahim200

    (@ramyibrahim200)


    Since the site has been moved from one host to another, there is a problem with Jetpack
    This message appears when connecting between the site and WordPress

    500 status code for “POST /sites/192763987/publicize-connections/new”

    The Jetpack site is inaccessible or returned an error: Jetpack: [http_request_failed] cURL error 52: Empty reply from server [-10520]

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Animesh Gaurav (a11n)

    (@bizanimesh)

    Hi there,

    From the page source, it looks like your WordPress URL is the same as the site URL that you mentioned above.

    While your site is publicly accessible, we cannot access your site’s XML-RPC file: https://YOURSITENAME.com/xmlrpc.php

    This file is used by Jetpack and other plugins and apps to connect to your site. It must return the following message: XML-RPC?server accepts POST requests only.

    You can see a working example here: https://jetpack.com/xmlrpc.php

    Since your site returns an?error?for this page, I would recommend that you check the following:

    • Do you use any security plugins that may block access to this file? If so, could you try to disable them? You might also want to check your site’s .htaccess file for any rules that might be blocking access to the?xmlrpc.php file.
    • Does your hosting provider block access to this file? If you don’t find any plugin that may block access to the file on your site, I would recommend that you get in touch with your host.

    Once we are able to access your site’s?xmlrpc.php file, you should be able to connect Jetpack to?https://wordpress.com.

    Let me know how it goes!

    Thread Starter ramyibrahim200

    (@ramyibrahim200)

    But he was working on the old hosting before moving the site
    When I transferred, I transferred all the files as they are and did not make any modifications

    Hello @ramyibrahim200

    Would you please disconnect and then reconnect Jetpack? You can follow these instructions to do that:

    1. Go to the **Jetpack** menu in your WP-Admin dashboard
    2. Scroll down to find the *Connections* area.
    3. Click *Manage site connection*.
    4. Click **Disconnect** and follow the prompts to complete the disconnection process.
    5. Click **Set Up Jetpack** button to connect your site to WordPress.com again.

    This handy guide explains the full process in more detail:

    * https://jetpack.com/support/reconnecting-reinstalling-jetpack/#disconnecting-jetpack

    Let me know if you have any questions.

    My best regards,

    Michelle C.

    Thread Starter ramyibrahim200

    (@ramyibrahim200)

    There was an error disconnecting Jetpack. Error: ApiError: Cookie check failed (Status 403)

    There was an error reconnecting Jetpack. Error: Cookie check failed

    Cookie check failed

    Plugin Support MadHatter (a11n)

    (@madhattersez)

    I’m afraid the xmlrpc.php file is still not working, as you can see here:https://aflamhd5.com/xmlrpc.php?for=jetpack

    It shows “ERR_HTTP2_PROTOCOL_ERROR.”

    This file is used by Jetpack and other plugins and apps to connect to your site. It -must- return the following exact message:

    
    XML-RPC server accepts POST requests only.
    

    As Animsesh said, I would suggest reaching out to your host to ask if they can remove that block so we can try a new connection.

    For the absolute best results, you could also have them whitelist the following to avoid future issues:

    1. All connections to and from *.wordpress.com
    2. The Jetpack IP ranges noted on this page: https://jetpack.com/support/hosting-faq

    Once your xmlrpc.php is loading normally and we’ve been whitelisted, please try connecting and letting us know how it goes. Thanks!

    Plugin Contributor Dan (a11n)

    (@drawmyface)

    Your site’s connection is working as expected now, so I’ll mark this thread as resolved. Let us know if you still have trouble.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘connection error’ is closed to new replies.