Jetpack 'protect' keeps getting re-enabled

  • Resolved mech422

    (@mech422)


    9 years ago

    The jetpack ‘protect’ feature keeps locking people out…
    It was a major pain in the butt, so I disabled it thru the control panel. However, about once a day the stupid thing re-enables itself.

    I’d like to know if there’s a way to prevent this from happening, and why it happens to begin with? I know jetpack is tied to wordpress.com now – is Automatic updating database settings on wordpress.com or something ?

    Thanks!

    https://wordpress.org/plugins/jetpack/

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter mech422

    (@mech422)

    9 years ago

    Updated last night to newest jetpack…
    ‘Protect’ still re-enables itself

    This is getting silly – it re-enables itself sometimes multiple times a day!!

    Plugin Author Brandon Kraft

    (@kraftbj)

    Code Wrangler

    9 years ago

    Do you have BruteProtect installed? Assuming no, could you disable the Jetpack plugin, reactivate, and reconnect your site to WordPress.com, then de-select Protect once more?

    It should only activate once upon activation. I haven’t heard of other reports like this to confirm there isn’t anything on our end tripping it back on.

    Cheers!

    Thread Starter mech422

    (@mech422)

    9 years ago

    BruteProtect is not installed. I disabled jetpack, downloaded it from the jetpack.me/install link, and now jetpack refuses to work at all.

    “There seems to be a problem with your site’s ability to communicate with Jetpack!”

    Thread Starter mech422

    (@mech422)

    9 years ago

    stopped/started php-fpm and nginx – deactivated & re-activated Jetpack
    Now it saying ‘client error: verification took too long’

    I disabled W3TotalCache, but still no joy
    the debug page claims there’s a problem contacting Jetpack.
    the xmlrpc file seems fine, and I’m not using any of the conflicting plugins. I was using betterWPSecurity, but I removed it awhile (months?year ?) ago

    Plugin Author Brandon Kraft

    (@kraftbj)

    Code Wrangler

    9 years ago

    Could you post your site URL here, so I can have a look?

    If you want it to remain private, you can also contact us via this contact form:
    http://jetpack.me/contact-support/

    Thread Starter mech422

    (@mech422)

    9 years ago

    http://www.digitalmusicnews.com

    Plugin Author Brandon Kraft

    (@kraftbj)

    Code Wrangler

    9 years ago

    There appears there may be some conflict between your production and staging sites. Your record with us has your staging URL, suggesting that the db was cloned between the two and something triggered the sync on the staging server, etc.

    Using JP’s Development mode on the staging server or not copying over Jetpack’s private options db row would prevent the contamination.

    I’m not certain if this is related or causing the Protect issue, but it could be.

    On the staging server, I’d suggest disconnected Jetpack, then on Production, disconnecting and reconnecting to reset the site record on our with your production environment.

    Cheers!

    Thread Starter mech422

    (@mech422)

    9 years ago

    That appears to have fixed it…
    Will let you know after its run for a while

    Thanks for the help!

    Thread Starter mech422

    (@mech422)

    9 years ago

    I’m gonna stick a fork in this and call it done 😉

    So far, no changes to activation state of the ‘protect me’ plugin.

    Thanks for all the help!

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Jetpack 'protect' keeps getting re-enabled’ is closed to new replies.