401: Jetpack: [unknown_token]

  • Resolved Jason Houge

    (@jasonhouge)


    1 year, 5 months ago

    I reinstalled my site from a backup (moved to a new host machine).
    Now I am having an issue trying to get Jetpack working again.

    “401: Jetpack: [unknown_token] It looks like your Jetpack connection is broken. Try disconnecting from WordPress.com then reconnecting.”

    • I have uninstalled, and reinstalled the plugin to no avail.
    • I’ve logged into my WordPress.com profile and my site isn’t listed any longer.
      (Oddly, one website is listed twice and another that hasn’t been online in a while is also listed. Is there a way to purge duplicates and defunct websites?)

    Thank you

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Tamirat B. (a11n)

    (@tamirat22)

    1 year, 5 months ago

    Hi there,

    Regarding your site’s Jetpack connection, please note Jetpack relies on the xmlrpc.php file to connect with our systems. Right now, it looks like something is blocking that connection, causing Jetpack to disconnect.

    I see that your site is behind Cloudflare (a CDN and DDoS protection service), which may be contributing to this issue. Can you please try pausing Cloudflare as described here?

    After you’ve paused it, try again to see if the issue persists.

    I’d also suggest checking if you have any other security plugins activated that might be blocking our requests.

    If not, try contacting your hosting provider and asking them to check their security logs to see if they are blocking or otherwise limiting incoming and outgoing connections over XML-RPC.

    Our requests look like the following:

    Please ask them to allowlist the IP addresses listed above.

    Regarding the duplicate and defunct websites in your WordPress.com profile, you can disconnect/purge defunct sites by visiting: https://wordpress.com/settings/manage-connection/. From there choose the site you want to disconnect and click Disconnect from WordPress.com at the bottom.

    Best regards,

    Thread Starter Jason Houge

    (@jasonhouge)

    1 year, 5 months ago

    Hi Tamirat,

    I appreciate your time looking into this for me. I didn’t want to overwhelm you with the many other things I’ve tried.

    This installation is years old, possibly a decade? It’s worked fine up until a very recent event which involved a host migration. I manage 5 other sites, all with the same setup, running without issues.

    I believe the issue is in the database. I believe there’s a corrupted something in there that prevents jetpack from re-initiating. I’ve looked at the database and I do not see any lines that jump out as Jetpack specific, so I am not sure how to fully remove jetpack from the database to start it fresh.

    best,

    …

    • This reply was modified 1 year, 5 months ago by Jason Houge.
    • This reply was modified 1 year, 5 months ago by Jason Houge.
    Plugin Support Tamirat B. (a11n)

    (@tamirat22)

    1 year, 5 months ago

    Hello @jasonhouge,

    Thanks for getting back.

    If you suspect stale Jetpack data is getting in the way, please try installing the plugin here: https://github.com/automattic/jetpack-addons/archive/add/jp-rm-options.zip.

    Once activated, it will remove any stale Jetpack data from installation. Deactivate the plugin, then try to connect again: https://jetpack.com/support/reconnecting-reinstalling-jetpack/.

    Let us know how it goes. We’ll escalate this to our development team depending on the outcome.

    Best,

    Thread Starter Jason Houge

    (@jasonhouge)

    1 year, 5 months ago

    Tamirat!
    You solved it, Thanks so much!

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘401: Jetpack: [unknown_token]’ is closed to new replies.