Ok I'm having trouble cloning a project on my Bitbucket.
I have SourceTree installed and when I clone a project using Bitbucket site I get a authentication log in.
I used my username and password (i'm pretty sure i used the correct one since i tried it on the bitbucket site and it worked) but sadly it doesn't accept and just sends me a Authentication failed error.
Here's the image
http://www.2shared.com/photo/FmKqnu0c/dsadasdsadsa.html
Please see https://jira.atlassian.com/browse/SRCTREEWIN-3944 for updates and a work around. A new release will be coming tomorrow morning San Francisco time.
I'm having the same problem. Sourcetree 2.1 on OSX. Login credentials are correct.
Try using the terminal option. The terminal never crashes, and it will allow you to enter the correct user name or to update password when needed.
image2016-10-19 11:34:8.png
Still having this issue with Version 2.4 (93)
Regularly prevents me from pulling changes due to 'incorrect password' error even though the password is absolutely correct.
'Use the terminal' is not a solution - the whole reason I choose to use sourcetree is so that I don't have to user the terminal. If that's the solution it might as well be suggesting to uninstall sourcetree altogether.
Same problem here.
OS version: macOS Sierra Version 10.12.4
SourceTree version: 2.5 (104)
I can't log in to my Bitbucket account, receive this error message:
"Could not authorize request with the available token. Please re-authenticate."
Hi,
yesterday I solved my issue: the reason I couldn´t connect was a special character (german umlaut) in my password that was not supported. This could be caused by a different codepage in Atlassian.
How to fix it fast and easy: change your password -> use only supported characters for it.
Following a new install of Sourcetree 2.7 on a Mac the initial login succeeded but on the first access to remote repositories required another login which repeatedly failed using correct credentials. This was solved as follows:
In sourcetree navigate to preferrences -> accounts.
Select the account listed and change the login type to OAuth - login form presented and credentials were accepted.
Remote repositories listed correctly.
Explanation (?)
On the initial login the licence file was downloaded from Atlassian completing the account details that had existed in a previous version - this used the username / password - authentication now uses email not password - by changing it to OAuth I was able to enter the new style email / password and reset the app.
I tried this and for a brief second i see my avatar when the edit screen is open, as soon as i confirm it it goes blanc again
i see this error
'Could not authorize request with the available token. Please re-authenticate.'
Im new to this forum, tried adding a second note here and keeps beeing deleted some how???
Found a stack exchange post. using this worked for me using ssh, using the beta version
ssh://git@github.com/USERNAME/REPONAME.git
Seems like the input is wrong when the app is used and account is setup?
It looks like you're new here. Sign in or register to get started.