Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic πŸš€

    Jetpack uses your site’s XML-RPC file to communicate with WordPress.com. Unfortunately, you seem to be using a service named blazingfast.io, that blocks all incoming requests to that file.

    I’d recommend getting in touch with them, and asking them if the service can be configured to allow incoming requests to XML-RPC, so you can start using apps and plugins like the mobile apps, or Jetpack.

    Once we can connect to your site’s XML-RPC file, we should be all set!

    Thread Starter Tanuj Singh

    (@tanuj-singh)

    OK, what should I tell them to do?

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic πŸš€

    You could ask them if the service can be configured to allow incoming requests to XML-RPC on WordPress sites. They should be able to take it from there.

    You can also send them this link if they need more information:
    https://gist.github.com/jeherve/e3d7c461d59208b230e8

    Thread Starter Tanuj Singh

    (@tanuj-singh)

    OK, let’s see if it’s solved.

    Thread Starter Tanuj Singh

    (@tanuj-singh)

    OK, let’s see if it’s solved.

    Thread Starter Tanuj Singh

    (@tanuj-singh)

    Hey, so, I contacted my host and they said me to give them the IP(s) that Jetpack uses to communicate with WordPress so that they could whitelist them.

    Thread Starter Tanuj Singh

    (@tanuj-singh)

    Hello, please reply πŸ™

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic πŸš€

    We don’t usually recommend whitelisting IPs, as our IPs will change in the future, and your host will consequently have to keep that list up to date to avoid issues.

    However, if they’re willing to keep the list up to date, they can use these IPs:
    185.64.140.0/22
    2a04:fa80::/29
    As well as all of the IPs listed at http://whois.arin.net/rest/org/AUTOM-93/nets

    Thread Starter Tanuj Singh

    (@tanuj-singh)

    Any other workaround we have over here? Because host is refusing to do so πŸ™

    Maybe, you guys can modify the plugin a bit, I really want to start my website :'(

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic πŸš€

    If they won’t add these IPs to their whitelist, and won’t allow the user of XML-RPC on your site, your only option would be to use Jetpack’s Development mode:
    http://jetpack.me/support/development-mode/

    You won’t have access to all Jetpack features, but at least you’ll be able to use the features that do not require a connection to WordPress.com, and can consequently work even if your host blocks XML-RPC.

    Another alternative would be to switch to a different hosting provider. The most popular hosting providers out there do not block XML-RPC, and you will be able to use all the features Jetpack has to offer, as well as other services and apps using XML-RPC.

    Thread Starter Tanuj Singh

    (@tanuj-singh)

    OK, will you guys update Jetpack in the future so that it could survive with DDoS protected hostings like this one? It’ll be really awesome.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic πŸš€

    Jetpack already includes features to protect you against XML-RPC attacks:
    http://jetpack.me/2015/10/12/jetpack-protection-from-brute-force-xml-rpc-attacks/

    However, it does require the use of XML-RPC, much like the mobile apps and other services like IFTTTT. That won’t change in the immediate future. In this particular case, I believe your host could find other ways to protect themselves against DDoS attacks, without blocking some core WordPress features like XML-RPC.

    Thread Starter Tanuj Singh

    (@tanuj-singh)

    No, it’s being blocked because when Jetpack tries to connect, it lands on that “DDOS PROTECTION BY BLAZINGFAST” instead of just connecting.

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

The topic ‘Jetpack Error: xml_rpc-32700’ is closed to new replies.