Lockout recovery process

Redirection notice

This page will redirect to /display/BitbucketServer/Lockout+recovery+process .

This page describes how to recover administrator access for Stash 2.11 and later. For releases prior to that, refer to Restoring the Stash Administrator's Password

As an administrator, you may find yourself locked out of Stash and unable to log in. This situation can arise when all users are managed externally from Stash, and Stash becomes unable to access those user directories for some reason, including:

  • The external user directory server is not accessible (because the network is down, or the directory is down, or the directory has been moved to another IP address).
  • Users are managed in JIRA and the Application Link from Stash to JIRA has been accidentally deleted.
  • The admin password has been forgotten or lost.
  • The admin account is shaded by a remote account in an LDAP or JIRA instance that is connected to Stash but which is unavailable.

The lockout recovery process for Stash is:

  1. Edit the <Stash installation directory>\bin\setenv.sh file (or setenv.bat on Windows) and add the "-Datlassian.recovery.password=temporarypassword" argument to the JVM_SUPPORT_RECOMMENDED_ARGS property. The property value must be non-blank, and should look like this when you've done that:



    Here we are using "temporarypassword", but you should use your own value.

    If you are starting Stash as a Windows Service ...

    If you are running Stash as a Windows service, please follow the steps outlined on Change atlassian.recovery.password when installed as a Windows service instead. The setenv.bat file is not used by the Windows service and changes there will, therefore, have no effect.

  2. Start Stash.
  3. Log in to Stash using the 'recovery_admin' username and the temporary password specified in Step 1.
  4. Repair your Stash configuration. We strongly recommend that you do not perform other actions while Stash is in recovery mode.
  5. Confirm your ability to log in with your usual admin profile.
  6. Shut down Stash, remove the atlassian.recovery.password argument from setenv.sh, and restart Stash as usual.


Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport