Site connection failed. Please try again.

  • Resolved Chris Miller

    (@millertchris)


    3 weeks, 2 days ago

    I’m experiencing exactly the same issue with jetpack connection on our production site (https://govino.com). After installing Jetpack and attempting to connect, we get “Site connection failed. Please try again.” with this console error:

    jetpack-connection.js?minify=false&ver=a50dca3d82c075611fa9:2 
POST https://govino.com/wp-json/jetpack/v4/connection/register 500 (Internal Server Error)

ApiError: Unable to insert blog. Please try again or contact support. (Status 500)
    at jetpack-connection.js?minify=false&ver=a50dca3d82c075611fa9:2:35525

    Our extensive troubleshooting efforts include:

    1. Verified and updated all WordPress plugins to their latest versions—issue still persists
    2. Confirmed WordPress core is up to date
    3. Deactivated all other plugins temporarily to check for conflicts—no change in behavior
    4. Reviewed server logs for any specific errors related to the API call
    5. Verified that all Jetpack-required PHP modules are installed and active
    6. Confirmed proper file permissions on the server

    Most notably, we created an exact replica of the production site by cloning the entire installation—including all files, database content, and server configurations—to a staging environment at https://govino.prolificdigital.io. Without making any changes whatsoever to this clone, we attempted to connect to Jetpack and it worked flawlessly on the first try.

    This is particularly puzzling since:

    • Both environments are managed through SpinupWP with identical server configurations
    • Both use WP Bedrock with the same structure and setup
    • Both have their DNS records hosted on Cloudflare with identical settings and configuration
    • Both have the exact same PHP version, MySQL version, and server configuration
    • Both have “Disable XML-RPC” enabled in SpinupWP
    • The database content is identical between the two environments

    We even tried enabling XML-RPC on the production site temporarily—something that isn’t needed on the staging site for Jetpack to connect—but the connection attempt still fails with the same error.

    The fact that an exact clone works perfectly on https://govino.prolificdigital.io while the production site (https://govino.com) fails consistently suggests there’s something specific about the production domain that’s preventing the Jetpack connection—despite having identical technical configurations. This points to an issue that may be related to how Jetpack’s servers interact with the domain itself rather than with our WordPress installation.

    Has anyone encountered a similar situation or can provide guidance on what might be causing this domain-specific connection failure? Any insights would be greatly appreciated!

    P.S. It appears that @gwalliman was having a similar issue but there was no resolution posted.

    https://wordpress.org/support/topic/site-connection-failed-please-try-again/?view=all#post-18412304

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

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

    (@bruceallen)

    Happiness Engineer

    3 weeks, 2 days ago

    Hi @millertchris

    Thanks so much for your detailed breakdown — it’s incredibly helpful to see all the steps you’ve already taken.

    One thing that stood out is that your production site URL is set to https://govino.com, while your Bedrock-based staging site uses a subdirectory (https://govino.prolificdigital.io/wp). Jetpack expects the WordPress core files to be located where the Site URL points, so mismatched paths like that can sometimes lead to connection issues.

    I’ve gone ahead and adjusted the Jetpack-side configuration to append /wp to your production site’s Site URL. When you have a moment, could you please try connecting Jetpack again on https://govino.com?

    Let me know how it goes — and if the error persists, we can dig deeper from there.

    Thread Starter Chris Miller

    (@millertchris)

    2 weeks, 6 days ago

    Thanks, @bruceallen ! It appears that whatever you did on your end fixed the issue! So there seems to be a settings or value that’s cached on the Jetpack servers that was causing this issue?

    Plugin Support Animesh Gaurav (a11n)

    (@bizanimesh)

    2 weeks, 5 days ago

    Hey @millertchris – thanks for confirmation!

    Yes, that’s correct – the URL configuration for your site was not correct on Jetpack, and making changes for that on our side fixed the issue.

    Also I’m glad we were able to help and the issue is resolved now. If you have a moment, would you like to leave a review of the plugin here? Thank you for using Jetpack! 🙂

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.