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

    (@tamirat22)

    Thanks for reaching out @f1yejunrui,

    To help us better understand the issue, could you let us know where you’re seeing the 429 error? For example, is it appearing in your browser, your site’s logs, or elsewhere?

    In some cases, 429 errors can be triggered when using Jetpack’s Image CDN, especially if your site or server is requesting the same images very frequently and our system may temporarily rate limit requests to prevent overload.

    These protections apply to all sites using Jetpack, but free plans have lower request thresholds. Paid plans include higher limits, which can help reduce the chances of running into this kind of error.

    Once we know more about where the error is showing up, we can help confirm whether the image CDN or something else is at play.

    Looking forward to your reply!

    Thread Starter f1yejunrui

    (@f1yejunrui)

    I can access the Jetpack “stats”, but this will pop up when I try to enter the “setting” sector.

    Outbound HTTPS not working

    Your site could not connect to WordPress.com via HTTPS. This could be due to any number of reasons, including faulty SSL certificates, misconfigured or missing SSL libraries, or network issues.

    Jetpack will re-test for HTTPS support once a day, but you can click here to try again immediately: Try again Response was not OK: <!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Transitional//EN” “http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd”&gt; <html xmlns=”http://www.w3.org/1999/xhtml”><head profile=”http://gmpg.org/xfn/11″&gt; <meta http-equiv=”Content-Type” content=”text/html; charset=UTF-8″ /> <title>WordPress.com 429 Error</title> <style type=”text/css”> h1 { font-weight: normal; font-size: 40px; } body { line-height: 1.6em; font-family: Georgia, serif; width: 390px; margin: auto; text-align: center; } .message { font-size: 22px; width: 350px; margin: 10px auto; } </style> <script type=”text/javascript” src=”//stats.wp.com/wpcom.js?5″></script> <script type=”text/javascript”> _error = ‘429-lb’; fzd(); </script> </head> <body> <h1>Whoops!</h1> <p class=”message”>There was a small systems error. Please try refreshing the page and if the error is still there <a href=”https://wordpress.com/contact-support/”>drop us a note</a> and let us know.</p> </body> </html>

    For more help, try our connection debugger or troubleshooting tips.

    • This reply was modified 5 months, 1 week ago by f1yejunrui.
    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there, @f1yejunrui,

    Thanks for continuing to troubleshoot this. We ran more tests on your site, and we suspect that the reason you still see that error when accessing the Jetpack settings is still likely related to some connection issues happening at your server’s end.

    While the XML-RPC and the REST API seem well-connected, allowing you to access some Jetpack features, there still might be something else that is interfering with the connection. Could you please check the following with your host for us?

    • ensure our IP range is fully in the allow list for your servers: https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/
    • check for any security/caching plugins you may have enabled, and try temporarily disabling them to see if it fixes the problem. 
    • search for any firewall on your server-side that might be blocking the communication with Jetpack.

    Let me know how you get on, and we’ll take it from there if necessary. thanks for sorting this out with us!

    Thread Starter f1yejunrui

    (@f1yejunrui)

    curl -I https://jetpack.wordpress.com
    curl -I https://public-api.wordpress.com
    HTTP/2 302
    server: nginx
    date: Thu, 23 Oct 2025 06:43:08 GMT
    content-type: text/html; charset=utf-8
    location: https://jetpack.com/
    x-hacker: Want root? Visit join.a8c.com/hacker and mention this header.
    host-header: WordPress.com
    vary: accept, content-type, cookie
    x-redirect-by: WordPress
    x-ac: 19.sin _bur MISS
    alt-svc: h3=":443"; ma=86400
    strict-transport-security: max-age=31536000
    server-timing: a8c-cdn, dc;desc=sin, cache;desc=MISS;dur=201.0

    HTTP/2 429
    server: nginx
    date: Thu, 23 Oct 2025 06:43:08 GMT
    content-type: text/html
    content-length: 960
    etag: "67f88038-3c0"
    x-ac: 18.sin _bur BYPASS
    alt-svc: h3=":443"; ma=86400
    strict-transport-security: max-age=31536000
    server-timing: a8c-cdn, dc;desc=sin, cache;desc=BYPASS;dur=0.0

    I think the issue is that our server IP might still be rate-limited on Jetpack API layer.

    The reason for being rate-limited was probably because I move my website from “blog.junruiye.com” to “www.junruiye.com” last week

    Plugin Support Chatoxz (a11n)

    (@chatoxz)

    Hi there,

    Thanks for following up. If you moved your site recently, it may be worth checking with your hosting provider if the change affected the IP addresses allocated. Please ask them to add them again if they are not available anymore, as listed here:

    https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/

    If the issue persists, try temporarily disabling any security or caching plugins to see if they are causing the problem. Also, check for any server-side firewalls that might be blocking communication with Jetpack.

    Please let us know how it goes by replying to this thread.

    Thank you!

    Plugin Support Tamirat B. (a11n)

    (@tamirat22)

    Hello @f1yejunrui,

    Do you have updates about the above? 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 6 replies - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.