Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Lockout recovery process for Stash

I followed the steps for recovery process of stash -:

  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.
  2. Start Stash.
  3. Log in to Stash using the 'recovery_admin' username and the temporary password specified in Step 1.

But now I don't know how should I repair the stash configuration.

    4) Repair your Stash configuration. We strongly recommend that you do not perform other actions while Stash is in recovery mode.


Please help me in setting up the user name and password of stash.

2 answers

Hi Uttam, Could you please provide further details about the issue you were facing, that led you to use the Lockout Recovery process? Obviously it's something related to login, but I'd like to know further details on this, as: * What do you see when trying to login with any user? Is there any apparent error? * Is Stash connected to any external user directory? If so you may need to go to Administration > User Directories and confirm it is properly connecting to the external directory. * You may also enable debug and attempt to login with some user to check if the logs show you anything. You can enable debug at Administration > Support > Logging and Profiling, selecting Enable debug logging and saving it. You can then try to login and, having the login failing, you can check at your atlassian-stash.log which is located at your $STASH_HOME/log directory. Regards, Gustavo Refosco

Does this apply to stash 3.51?  I'm trying to upgrade to bitbucket server and going through the dregs of legacy software to do it.  Just managed to lock myself out and need a way to get back in or reinstall the dummy stash server I'm using for the migration/upgrade.

 

I followed the directions, but recover_admin and my temporary password don't seem to have any affect when applied as shown.  Is there an additional step besides restarting stash?

Hi Joshua

Yes, the approach is the same from Stash 2.11 to Bitbucket Server 7.10.

https://confluence.atlassian.com/display/STASH035/Lockout+recovery+process

I believe there is a typo in your example as the username should be "recovery_admin".

 

Regards, Anton

The typo was just in my issue, I've been using recovery_admin

 

Any other ideas?

image.png

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Powering DevOps with Bitbucket Server & Data Center

Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster   ! While we’re all excited about the new improvements to Bitbucket ...

2,581 views 1 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you