• Resolved chrissteiner

    (@chrissteiner)


    I’d like to (re-)enable the brute-force protection in Jetpack (free version). It was definitely enabled before. However, I’m getting the following error message: “Error updating settings. protect: The requested Jetpack module could not be activated. (Status 400)” I haven’t been able to get anywhere with my web hosting provider. Does anyone have any idea what might be causing this? Or is brute-force protection simply no longer included in the free plan?

    Many thanks!
    Chris

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Jenny (a11n)

    (@jennywp)

    Hey @chrissteiner – thanks for reaching out.

    It looks like the issue is that your connection to Jetpack itself is broken, so let’s get that sorted first. It’s likely that once you reconnect, you’ll be able to toggle Protect back on. 🙂

    The problem is that access to your site’s xmlrpc.php file is being blocked. You can see the “Forbidden” message here:

    https://www.fmz-imst.at/xmlrpc.php

    This file is used by Jetpack and other plugins and apps to connect to your site, but some hosts and security plugins block access to it. That file should simply return, “XML-RPC server accepts POST requests only.” on a completely white screen, with the text left-justified in the top corner of the screen. You can see a working example here:

    https://jetpack.com/xmlrpc.php

    Please ask your host’s customer support team to check security logs to see if they are blocking or throttling incoming and outgoing connections via XML-RPC. You can tell them to look for the following requests:

    You can also ask them to allowlist the IP addresses listed above. Note that these IP addresses could change (or more could be added) at any time, which could break your connection to Jetpack. For this reason, we actually discourage allowing specific IPs, although with some hosts it may be the only option.

    If your host mentions that they are not blocking access to xmlrpc.php, then please do an audit of any security plugins you’re using, and ensure you’ve adjusted those settings to allow Jetpack to connect. 

    Once your host is allowing connections (or you adjust the settings of your security plugin), you can reconnect Jetpack:

    https://jetpack.com/support/reconnecting-reinstalling-jetpack

    …and then you can activate Protect.

    Let us know how it goes!

    Thread Starter chrissteiner

    (@chrissteiner)

    Unfortunately, the issue could not be fully resolved. At this point, however, we have decided not to invest any further resources in it, as we were able to find another plugin that works well for our purposes.

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

You must be logged in to reply to this topic.