Attempts to reconnect Jetpack after site migration to new host failed

  • Resolved llilly0

    (@llilly0)


    7 months, 1 week ago

    I migrated to a new host. There my site is in ‘preview’ mode, (a type of staging) until I connect the domain to the new host.

    In reconnecting Jetpack after the migration I got this: “There was an error reconnecting Jetpack. Error: ApiError: 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. (Status 500)”

    After deactivating W3 Total Cache, I then tried to connect to WordPress.com, got “connect to user account to fix this” and when I pressed button, ‘an error occurred please try again’

    In addition, I scrolled down to the bottom of “My Jetpack” to where it says “Your Plans and Connection” and tried again and it failed again.

    How do I get Jetpack fully functional again on my newly migrated site?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter llilly0

    (@llilly0)

    Note: I understand that a possible reason for the failed reconnect is because the migrated ‘preview’ site is not live therefore a connection cannot be made with Jetpack and my WordPress.com account.

    So a further question is this:

    If I reactivate the W3 Total Cache plugin (a reversal of the suggested process as described above), will it put the Jetpack in its original migrated form ready to be reconnected once it is live (after the dns redirect to my new host is complete?)

    Mehdi Benchalal

    (@muffinpeace)

    Hi @llilly0,

    I can see you mentioned migrating your website to another hosting provider, and there the site was on a staging-like, maintenance/coming soon mode.

    That would definitely affect the Jetpack connection, so it was better to wait for the DNS propagation to finish (which should be the case a few days ago already now).

    Have you been able to fully connect Jetpack at this point? If not, we’d appreciate if you can share your website, so we can advise precisely depending at which stage it is.

    Looking forward to your reply.

    Thread Starter llilly0

    (@llilly0)

    All’s well, now. Thank you.

    Great, thanks for letting us know! Please post again if you run into other issues.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Attempts to reconnect Jetpack after site migration to new host failed’ is closed to new replies.