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
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
i am experiencing an issue already discussed both here and on stackoverflow, concerning this error:
fatal: protocol error: bad line length character: git_
but most solutions suggest the problem lies in the server.
Thing is, this happens only on my desktop where i've updated to SourceTree 3.4.8; if i try to fetch/push from my laptop to the very same server it works just fine.
On my laptop i delayed the update, and still running SourceTree ver. 3.4.7.
As for the server address, which includes the 4 bytes of the error message reported above, it is in fact:
Pushing to ssh://git_user@myIp:myPort/volume1/git_repos/myRepo.git
Pageant is running on the client, although there is no ssh key, since i am hosting the server in my house and there's just a password auth for the user git_user.
I also tried removing the passwd file, to see if it was failing authentication, but pushing/fetching won't even get to the authentication phase: i reckon the error happens before auth, since i'm not being asked to input the password again.
Aside from testing with both machines, with the same configuration, where one works and the other doesn't, i'm quite stuck with troubleshooting... the only thing i could concieve was the version mismatch.
I should probably try to downgrade and see if it solves the issue.
Can anyone provide additional feedback?
Had a similar issue with the error
"protocol error: bad line length character: | Pa"
Downgraded from 3.4.9 to 3.4.7 and its working again.
Running commands manually on the Terminal also worked. For example, if we pressed the "Push" button we would have that error, but if we executed "git push" in the terminal the push operation would run without errors.
On WIndows 10, this fixed this issue on version 3.4.12 and earlier versions.
Assuming you have an SSH private key setup, under Tools -> Options -> General tab
Change the SSH Client entry to "OpenSSH", and click OK. It will open a command window and ask for your for passcode.
It then works for me.