CONNECTION JETPACK DENIED TO WP SITE

  • Resolved Walup

    (@walletup)


    1 month, 3 weeks ago

    Hi,

    Currently the website is unable to take woopayments because of this error. We are main self-hosted, and have investigated this without success.
    We’re encountering a critical issue with Jetpack on our WordPress site (satellapower.com/market). Jetpack is unable to communicate with our site, consistently receiving an HTTP 403 error.

    Specific Error Message: “The Jetpack server was unable to communicate with your site https://satellapower.com/market [HTTP 403]. Ask your web host if they allow connections from WordPress.com. If you need further assistance, contact Jetpack Support: https://jetpack.com/support/”

    Steps Already Taken without success:

    1. Verified SSL certificate is valid and properly installed.
    2. Disconnected and reconnected Jetpack to WordPress.com (in vain).
    3. Ensured WordPress version is up-to-date (currently running version X.X).
    4. Disabled all other plugins to rule out conflicts except jetpack and woo.
    5. Added recommended WordPress constants in wp-config.php:
      • define( ‘WP_HTTP_BLOCK_EXTERNAL’, false );
      • define( ‘JETPACK_DEV_DEBUG’, true );
    6. Verified host firewall is not blocking WordPress.com IP ranges.
    7. Disabled Temporally CSF, switched from LSWB to apache

    We request your assistance in:

    1. Providing specific Jetpack debug steps to identify the root cause of the 403 error.
    2. Advising on any known conflicts between Jetpack and server configurations (we’re using CloudLinux 8.10 with LiteSpeed enterprise 6).
    3. Guiding us through any advanced troubleshooting specific to Jetpack connectivity issues (WE CONSULTED YOUR ONLINE RESOURCES EXTENSIVELY WITHOUT SUCCESS).

    Your expertise in resolving this Jetpack connection issue is crucial for restoring full functionality to our site.

    PS: The same server runs another store that connects to woocommerce directly without issues since 2019

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

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

  • Hi @walletup, thanks for getting in touch.

    This sounds like something we will want to escalate to the development team to take a look at, given the extensive troubleshooting you’ve already completed with no success.

    First, could you verify that the JSON API module is enabled on your site? You can do this from the Jetpack Modules page. I’m seeing a notification on our side that JSON API calls to your blog have been disabled. This is sometimes the root cause of a 403 error.

    If this doesn’t work, then please contact us via this contact form and mention this thread. To escalate this to the development team we’ll need to be able track the issue internally and this will allow us to do that.

    Talk to you soon.

    Thread Starter Walup

    (@walletup)

    Thank you .
    We are unable to proceed with the steps within jetpack. Since the Jetpack is disconnected, it does not show us these options. However we curl and Connections to?wordpress.com?and to?api.www.ads-software.com??(https://developer.www.ads-software.com/rest-api/) are successful. 

    [satellapow@kingdom market]$ curl -LI https://api.www.ads-software.com
    HTTP/1.1 302 Found
    Server: nginx
    Date: Tue, 01 Oct 2024 23:40:47 GMT
    Content-Type: text/html; charset=utf-8
    Connection: close
    Location: https://developer.www.ads-software.com/rest-api/
    X-Frame-Options: SAMEORIGIN
    Alt-Svc: h3=":443"; ma=86400
    X-nc: ord 1

    HTTP/2 200
    server: nginx
    date: Tue, 01 Oct 2024 23:40:48 GMT
    content-type: text/html; charset=UTF-8
    vary: Accept-Encoding
    x-olaf: ?
    link: https://developer.www.ads-software.com/wp-json/; rel="https://api.w.org/"
    link: https://developer.www.ads-software.com/wp-json/wp/v2/rest-api-handbook/22832; rel="alternate"; title="JSON"; type="application/json"
    link: https://developer.www.ads-software.com/?p=22832; rel=shortlink
    x-frame-options: SAMEORIGIN
    alt-svc: h3=":443"; ma=86400
    x-nc: EXPIRED ord 1

    [satellapow@kingdom market]$ curl -IL https://WordPress.com
    HTTP/2 200
    server: nginx
    date: Tue, 01 Oct 2024 23:40:57 GMT
    content-type: text/html; charset=utf-8
    vary: Accept-Encoding
    x-frame-options: SAMEORIGIN
    x-content-type-options: nosniff
    x-xss-protection: 1; mode=block
    x-hacker: Want root? Visit join.a8c.com/hacker and mention this header.
    host-header: WordPress.com
    vary: Cookie
    set-cookie: tk_ai=2m45G6xLgbCw9Zb5PcnvPMqn; expires=Sun, 30-Sep-2029 23:40:57 GMT; Max-Age=157680000; path=/; domain=.wordpress.com; secure; SameSite=None
    set-cookie: tk_ai_explat=2m45G6xLgbCw9Zb5PcnvPMqn; expires=Sun, 30-Sep-2029 23:40:57 GMT; Max-Age=157680000; path=/; domain=.wordpress.com; secure; SameSite=None
    set-cookie: tk_qs=_en%3Dwpcom_experiment_variation_assigned%26_ut%3Danon%26_ui%3D2m45G6xLgbCw9Zb5PcnvPMqn%26_ts%3D1727826057205%26experiment_id%3D22017%26experiment_variation_id%3D4620%26reason%3Dset_by_anon_id; path=/; domain=.wordpress.com; secure; SameSite=Strict
    set-cookie: explat_test_aa_weekly_lohp_2024_week_40=control; expires=Mon, 21-Oct-2024 00:00:00 GMT; Max-Age=1642743; path=/; domain=.wordpress.com; secure; SameSite=None
    x-ac: 1.sjc _bur BYPASS
    strict-transport-security: max-age=31536000; preload
    alt-svc: h3=":443"; ma=86400

    [satellapow@kingdom market]$ curl -LI https://developer.www.ads-software.com/rest-api/
    HTTP/2 200
    server: nginx
    date: Tue, 01 Oct 2024 23:41:54 GMT
    content-type: text/html; charset=UTF-8
    vary: Accept-Encoding
    x-olaf: ?
    link: https://developer.www.ads-software.com/wp-json/; rel="https://api.w.org/"
    link: https://developer.www.ads-software.com/wp-json/wp/v2/rest-api-handbook/22832; rel="alternate"; title="JSON"; type="application/json"
    link: https://developer.www.ads-software.com/?p=22832; rel=shortlink
    x-frame-options: SAMEORIGIN
    alt-svc: h3=":443"; ma=86400
    x-nc: EXPIRED ord 1
    Plugin Support Alin (a11n)

    (@alinclamba)

    Hi @walletup,

    I found your message via email and replied so let’s continue there.

    Thank you!

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