Jetpack locking me from logging in, says ‘recovery token is not valid’ when I follow steps.

  • Unknown's avatar

    PLEASE contact me with explicit procedures for (1) getting past being locked out of logging in to my site so I can (2) get rid of Jetpack so it won’t ever again lock me out of logging in to my site. I find this behavior totally unacceptable.

    The blog I need help with is: (visible only to logged in users)

  • Hi there,

    You can find Jetpack’s instructions on how to whitelist your IP address here:

    Jetpack

    For more help with this, please contact Jetpack support directly at the following link:

    Contact Support

  • Unknown's avatar

    After reading your support page [https://jetpack.com/support/security-features/#unblock] again this morning, and thinking through WHICH IP number I needed to include in the “define” statement added to wp-config.php, I restored logging in. I have a THEORY as to why the IP number “flagged for potential security violations” is different from the IP number returned by whatismyip.com – not being certain is bothersome.
    My THEORY: the plugin WPS Hide Login is using the flagged IP number when re-routing the login page to other than /wp-login or /wp-admin.
    One of the effects, if my theory is correct, is that it breaks your send-you-an-email to get logged in process. It uses a login URL that includes /wp-login. I changed that to the alternate name set with the above plugin, and got a login prompt. When I then tried logging in, though, I got an error:
    “The recovery token is not valid for this user.”
    End-of-day tiredness, uncertainty about proper fix, and frustration at not being able to get to the site (another admin living in another state had precisely the same issue) led to some ranting language. Apologies for that.

  • No worries. I’m glad you were able to get back in to the site :) We understand that it can be a frustrating experience when something unexpected like that occurs.

  • The topic ‘Jetpack locking me from logging in, says ‘recovery token is not valid’ when I follow steps.’ is closed to new replies.