Viewing 8 replies - 1 through 8 (of 8 total)
  • I am also getting again and again false message. My website is fully up and running but I am getting false message that my website is down. this is a bug?

    Plugin Contributor Stephen Quirk

    (@sdquirk)

    Hi there,

    On the messages we send, please note the following info:

    If the site looks OK in the screenshot, then the string we use to determine if a site is up was missing from the footer of your website.
    <p>A few common causes:</p>

    • Site upgrades are in progess (if this is the case, your site will be back up within a few minutes)
    • Poor site performance on your webserver
    • You may have deactivated or removed the BruteProtect plugin
    • Your WordPress Theme never makes a call to wp_footer()

    We’re also working on a solution for disabling or controlling messages, but I don’t have a solid date for this yet.

    Thanks!

    Hello,

    Thanks for your reply.
    I am using my 5 website. All website is in same server and none of them showing or from those website not coming any message like one website. Also the screenshot, there is nothing. Only a blank white images coming?

    Plugin Contributor Sam Hotchkiss

    (@samhotchkiss)

    We are releasing an update to BruteProtect today which will allow you to opt out of monitoring, which will resolve any issues with receiving too many emails.

    I also got these messages on all my sites after updating to v. 2.3. All my sites were reported to be down while they weren’t.

    3 different hostings.

    All my sites use a cache plugin.

    So I logged in on all sites, cleared all caches and minutes later I got the emails that the sites are running again.

    hth

    I am also getting the same email notifications that sites are down. But they are all up and we are operating at optimum. This started to happen after the latest upgrade.

    Please advise.

    Sorry didn’t realize this was resolved. Opening a new thread.

    Plugin Author Rocco Tripaldi

    (@roccotripaldi)

    Thanks for your reports, folks. We found the issue and we have pushed 2.3.1 to fix it.

    What happened was that sites that weren’t redirected to the bruteprotect-config page after updating to 2.3 ( ie, sites that were autoupdated, or updated through my.bruteprotect ), didn’t get the new configuration data. Our output of the check string depended on the new data, so those sites didn’t get a check string, and thus, appeared to be down.

    Sorry for any inconvenience.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Getting False "Down" message’ is closed to new replies.