Good day team,
I realise with the latest release of Sourcetree, i assume it is Version 2.7.1, it always triggers this alert
Cloning into '-'...
warning: templates not found /usr/local/git/share/git-core/templates
remote: Too many invalid password attempts. Try logging in through the website with your password.
fatal: unable to access 'https://-@bitbucket.org/-/-/': The requested URL returned error: 403
"-" just indicates redacted, it is valid data. But thats besides the point. It just seems so broken to me, because every time i want to work from Sourcetree, this error comes up, which has never happened on previous versions of Source.
I tried a workaround found in the web, which is to reauthenticate in id.atlassian.com; it just fixes the symptom, but it not the problem.
I hope this can be fixed, something is wrong with your authentication.
First thing, please update to the latest version of Sourcetree 2.7.2 (167) that is available as OSX_Latest.zip from https://bitbucket.org/atlassianlabs/sourcetree-betas/downloads/
From the details you've mentioned above, I understand that you are using https remote repo URL. Can you also confirm if the bitbucket account you have in Sourcetree is using https too?
If in case, its ssh, you might want to either fix the account to use https or change your remote url to ssh.
To change the account to use ssh, just edit the account in the preference window > Accounts tab and select ssh as the protocol.
If you want to use ssh for remote URLs, in the repository browser window, right click on the repo bookmark and select "Convert to SSH"
If your problem isn't solved with these steps, please let us know here with the details of what you've tried and the error messages you see.
Sourcetree Mac Developer
Tried the beta build. However the same issue still ensues. The repositories are in https, so my approach is fine. I do not think the issue is with how the repository authenticates with sourcetree, it is how sessions are managed for oauth between Google and Atlassian.
It seems like it times out and everytime it is fixed, it is because i logged out and logged back into the service, which should be the case. The timeout should be 30 days, if the box has been ticked, no?
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