Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
After upgrading Stash to 2.0.1 (from 1.3) I get this error when cloning, and pushing.
Login to to the Stash WebApp is working as expected.
It seems to be a problem with urls that contains the username, ie: http://username@stash:7990/scm/REPO/repo.git
When cloning the same repo wihtout specifying the username it seems to be OK - but I need some solution to this since Stash itself is providing the link with username and all the cloned respositories have this as their remote...
Adding the username to the URL is only a hint for an HTTP client (Git in this case) to use basic authentication. This results in a request that is attempting to authenticate with a blank password, before prompting for your actual password and trying again. However your user directory (JIRA) is throwing an exception on the first attempt, which shouldn't happen. There may be something wrong with the directory configuration.
To diagnose this further it would be handy to see the full stacktrace from the logs which should contain the underlying exception. You could either post that here and/or raise a support ticket at http://support.atlassian.com and attach your logs so we can help diagnose this further.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs