jb_static and XML-RPC (errors 400 after the activation)

  • Resolved testingthetest

    (@testingthetest)


    7 months, 4 weeks ago

    Hello Jetpack support,

    I need your assistance to identify the cause of a list of errors 400 on a website that I manage.

    All the problematic URLs have the following path (with different hashes after the first /)

    _jb_static/?%3F-eJyNjbEOwjAMRP+GidSNGMpS8S0hcYurxIkcp8DfE7ZOiPF0793BsxhiH1vACluFQFVhRw5ZoFclx%2FdCMXYGRYdEPGz1DD8kwRU76zSLkcZKCf%2FRDl9H3GdWZIUS20pc4ZudV7NkSWaClEOLfUzQu6L+4YA44KvbtzTbydrxeplGe%2FL32X4AeA1V2Q=%3D

    I cannot turn off your plugin because it allows me to pass the mobile CWV.

    Any suggustion?

    The active features are:

    Optimize critical CSS loading;
    Delayed loading of non-essential JavaScript;
    Concatenate JS;
    Concatenate CSS;

    ——————-
    Other errors 400 refers to

    xmlrpc.php?rsd

    Any suggestion about this?

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

  • Hi @testingthetest,

    To better assist you with the errors 400 related to URLs with the _jb_static path and xmlrpc.php?rsd, could you please post your site URL here so that we can have a look?

    If you want it to remain private, you can contact us via this contact form. If you choose to reach out directly, please don’t forget to include a link to this thread.

    For the issue with _jb_static paths, this seems to be related to Jetpack’s Site Accelerator feature that serves static assets from Jetpack’s servers. If you’re experiencing 400 errors, it could be due to caching issues or misconfiguration disallowing Jetpack from accessing the original resource.

    Regarding the xmlrpc.php?rsd issue, this is often associated with Jetpack’s connection to your site. XML-RPC is used by Jetpack and other applications to communicate with WordPress. However, if the XML-RPC file is returning a 400 error, it may be due to security measures or hosting configurations blocking access to that file.

    Looking forward to your reply with the website URL so we can investigate further.

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi?@testingthetest,

    Do you have updates about that? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘jb_static and XML-RPC (errors 400 after the activation)’ is closed to new replies.

Tags