You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Beginning with the SourceTree 3.4.8 (Windows) update, I can no longer push or pull. Everything else seems to work, but I'm having to use the git command line for push/pull. The error message is (personal info replaced with asterisks):
git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks push -v origin develop:develop
Pushing to ssh://***
fatal: protocol error: bad line length character: ***
Completed with errors, see above.
Is there a workaround for this until the bug gets fixed?
Thank you.
It seems that the problem is the new Putty version 0.76.
I replaced the integrated putty (just the putty folder - version 0.76) by the one from the previous version 3.4.7 (0.70.2-Sourcetree) and it works as before.
The putty folder is in (C:\Users\<user>\AppData\Local\SourceTree\app-3.4.8\tools\putty - or your user folder).
Is it possible that the official putty version is missing some fixes done by Atlassian ?
Thx. That solved my problem as well.
To be honest I was running on version 3.4.6 and from one to another day I wasn't able to work with my gitserver via ssh.
Then - as the last hope - I did an update to 3.4.8 - nothing changed.
I was already despaired I searched on the net again and found this entry.
I copied putty from 3.4.6 into 3.4.8 - I didn't expected that it helps - but it did.
From my perspektiv this issue must caused by another reason. My gues was to check the windows updates - but there weren't any updates done in the relevant time frame.
Amasing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I finally tried this, and it worked for me as well. Also, the Putty problem persists in SourceTree 3.4.9. Sigh.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The problem component is plink.exe (part of Putty), bundled with Sourcetree.
Sourcetree 3.4.7 has plink.exe version "0.70.2-sourcetree" compiled specially for the Sourcetree project, but more recent versions have common plink.exe from https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html.
The workaround is the following:
I hope the Sourcetree team will fix this bug in future releases.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm using SourceTree 3.4.11 and had the exact same issue. I resolved it as stated above by replacing the putty folder by the one included with 3.4.7!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Goug,
Please try this method, it worked for me. https://community.atlassian.com/t5/Sourcetree-questions/Cannot-connect-to-bitbucket-account-since-app-passwords/qaq-p/1971112
Cheers,
Gopi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.