I followed the steps for recovery process of stash -:
<Stash 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:
temporarypassword", but you should use your own value.
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.
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
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot