Lockout recovery process
Administering Bitbucket Server
- Users and groups
- External user directories
- Global permissions
- Setting up your mail server
- Integrating Bitbucket Server with Atlassian applications
- Connecting Bitbucket Server to an external database
- Migrating Bitbucket Server to another server
- Specifying the base URL for Bitbucket Server
- Configuring the application navigator
- Managing add-ons
- Audit logging in Bitbucket Server
- Running Bitbucket Server as a Windows service
- Updating your Bitbucket Server license details
- Bitbucket Server config properties
- Moving Bitbucket Server to a different context path
- Data recovery and backups
- Disabling HTTP(S) access to Git repositories in Bitbucket Server
- Smart Mirroring
- Git Large File Storage
- Enabling SSH access to Git repositories in Bitbucket Server
- Using diff transcoding in Bitbucket Server
- Changing the port that Bitbucket Server listens on
- Lockout recovery process
- Proxying and securing Bitbucket Server
- High availability for Bitbucket Server
- Enabling JMX counters for performance monitoring
- Bitbucket Server debug logging
- Scaling Bitbucket Server
- Getting started with Bitbucket Server and AWS
- Add shortcut links to a Bitbucket Server repository
- Data Center Migration
- Git Virtual File System (GVFS)
- Diagnostics for third-party apps
- Administer code search
On this page
- No related content found
Still need help?
The Atlassian Community is here for you.
This page describes how to recover administrator access for Stash 2.11, now known as Bitbucket Server 4.X+, and later. For releases prior to that, refer to Restoring the Bitbucket Server Administrator's Password.
As an administrator, you may find yourself locked out of Bitbucket Server and unable to log in. This situation can arise when all users are managed externally from Bitbucket Server, and Bitbucket Server 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 within a JIRA application and the Application Link from Bitbucket Server to a JIRA application 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 application that is connected to Bitbucket Server but which is unavailable.
The lockout recovery process for Bitbucket Server is:
- Edit the
<Bitbucket Server installation directory>
setenv.baton Windows) and add the "
-Datlassian.recovery.password=temporarypassword" argument to the
JVM_SUPPORT_RECOMMENDED_ARGSproperty. 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.
- Start Bitbucket Server manually by running
<Bitbucket Server installation directory>\bin\start-bitbucket.sh(or
- Log in to Bitbucket Server using the 'recovery_admin' username and the temporary password specified in Step 1.
- Repair your Bitbucket Server configuration. We strongly recommend that you do not perform other actions while Bitbucket Server is in recovery mode.
- Confirm your ability to log in with your usual admin profile.
- Shut down Bitbucket Server, remove the
setenv.sh, and restart Bitbucket Server as usual.
- No related content found