Cloud
Data Center 4.8
Versions
- 9.5
- 9.4
- 9.3
- 9.2
- 9.1
- 9.0
- 8.19
- 8.18
- 8.17
- 8.16
- 8.15
- 8.14
- 8.13
- 8.12
- 8.11
- 8.10
- 8.9
- 8.8
- 8.7
- 8.6
- 8.5
- 8.4
- 8.3
- 8.2
- 8.1
- 8.0
- 7.21
- 7.20
- 7.18
- 7.19
- 7.17
- 7.16
- 7.15
- 7.14
- 7.13
- 7.12
- 7.11
- 7.10
- 7.9
- 7.8
- 7.7
- 7.6
- 7.5
- 7.4
- 7.3
- 7.2
- 7.1
- 7.0
- 6.10
- 6.9
- 6.8
- 6.7
- 6.6
- 6.5
- 6.4
- 6.3
- 6.2
- 6.1
- 6.0
- 5.16
- 5.15
- 5.14
- 5.13
- 5.12
- 5.11
- 5.10
- 5.9
- 5.8
- 5.7
- 5.6
- 5.5
- 5.4
- 5.3
- 5.2
- 5.1
- 5.0
- 4.14
- 4.13
- 4.12
- 4.11
- 4.10
- 4.9
- 4.8
- See all
Lockout recovery process
Advanced actions
- Running the Bitbucket Server installer
- Automated setup for Bitbucket Server
- Starting and stopping Bitbucket Server
- Install Bitbucket Server from an archive file
- Install and configure a remote Elasticsearch instance
- Running Bitbucket Server as a Linux service
- Running Bitbucket Server as a Windows service
- Bitbucket Server config properties
- Proxying and securing Bitbucket Server
- Enabling SSH access to Git repositories in Bitbucket Server
- Using diff transcoding in Bitbucket Server
- Changing the port that Bitbucket Server listens on
- Moving Bitbucket Server to a different context path
- Running Bitbucket Server with a dedicated user
- Bitbucket Server debug logging
- Data recovery and backups
- Lockout recovery process
- Scaling Bitbucket Server
- High availability for Bitbucket Server
- Clustering with Bitbucket Data Center
- Enabling JMX counters for performance monitoring
- Getting started with Bitbucket Server and AWS
- Disabling HTTP(S) access to Git repositories in Bitbucket Server
- Smart Mirroring
- Git Large File Storage
On this page
Related content
- Using Bitbucket Server in the enterprise
- Getting started with Git and Bitbucket Server
- Bitbucket Server documentation home
- Installing Bitbucket Data Center
- Bitbucket rebrand FAQ
- Bitbucket Server FAQ
- Using Bitbucket Server
- Why should I choose Bitbucket Server over some other repository management tool?
- Getting started with Bitbucket Server and AWS
- Running the Bitbucket Server installer
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>\bin\setenv.shfile (orsetenv.baton Windows) and add the "-Datlassian.recovery.password=temporarypassword" argument to theJVM_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(orstart-bitbucket.baton Windows). - 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
atlassian.recovery.passwordargument fromsetenv.sh, and restart Bitbucket Server as usual.
Last modified on Jun 15, 2016
Related content
- Using Bitbucket Server in the enterprise
- Getting started with Git and Bitbucket Server
- Bitbucket Server documentation home
- Installing Bitbucket Data Center
- Bitbucket rebrand FAQ
- Bitbucket Server FAQ
- Using Bitbucket Server
- Why should I choose Bitbucket Server over some other repository management tool?
- Getting started with Bitbucket Server and AWS
- Running the Bitbucket Server installer
Powered by Confluence and Scroll Viewport.