• Resolved muckaveli

    (@muckaveli)


    This is my setup
    WordPress v. 6.2
    Jetpack v. 12.5

    The problem 1
    WordPress settings (via https://wordpress.com/settings/general/mydomain.com) is alerting me: “Jetpack cannot communicate with your website because your website is not connected.”
    Simultaneously, Jetpack itself (via https://mydomain.com/wp-admin/admin.php?page=my-jetpack) says

    • ? Site connected
    • ? Connected as username (Owner)

    The problem 2 (whenever disconnecting Jetpack)

    Whenever I follow tutorials on how to disconnect and re-connect jetpack from WordPress, it will get very complicated for me.

    • Trying to re-connect Jetpack in My Jetpack, it states?“An error occured. Please try again.”
    • Checking the connection (via https://mydomain.com/wp-admin/admin.php?page=connection-test-admin-page) > Test Authenticated WCS request results in “Connected with another user account”. With a GET response “{“statusCode”:401,”error”:”Unauthorized”,”message”:”Invalid credentials”,”attributes”:{“error”:”Invalid credentials”}}”.
    • My Jetpack then states “site connected, user account NOT connected”. Clicking “connect” resulted in?“Unfortunately, an unexpected error has occurred”.

    The only way I can (somewhat successfully) re-connect Jetpack to my WordPress installation is via https://wordpress.com/jetpack/connect. However, this is when problem 1 occurs again.

    The problem 3

    Using https://jptools.wordpress.com/debug/ to analyze my website, the result is “Communication error

    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. If the error persists, try disconnecting and connecting Jetpack again.”

    I have the strong feeling that my connection with Jetpack has issues and I’ll need to get rid of them in order to make everything else work smoothly. How can I fix this mess?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Hi @muckaveli

    It sounds like that while your site is publicly accessible, we cannot access your site’s XML-RPC file:

    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:

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

    • Can you see the /xmlrpc.php file at the root of your WordPress installation when accessing your site via FTP? If you don’t, then please try re-installing WordPress. You can do this by going to the Dashboard -> Upgrades page, then click the “Reinstall” button.
    • 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, please try to reconnect your site:

    If you want to learn more details about XML-RPC and how it interacts with Jetpack, you can check out our detailed guide here: https://jetpack.com/support/jetpack-and-xml-rpc

    Looking forward to your reply on how it went and then we will check for the Jetpack connection for your site again to check if things started working properly after the above steps. ??

    Plugin Support Tamirat B. (a11n)

    (@tamirat22)

    Hello @muckaveli

    Do you have updates about that? We usually close inactive threads after one week of no activity, but we want to make sure we’re all set before marking it as solved. Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Heavy connection issues with wordpress.com’ is closed to new replies.