Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


can't pull, getting error "fatal: protocol error: bad line length character: logg

Have been using source tree on windows for several years but a week ago started getting the above error whenever I try to do a pull or fetch.  Using ssh, getting same error through gitbash.  Tried to see actual error with 

ssh "git-upload-pack ...".  But didn't seem to show anything helpful to this error.  Anyone have any ideas?

1 answer

0 votes
Mike Corsaro
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 14, 2019


This might be an issue with your remote server, but it also might be an issue with your SSH agent -- could you try some of steps in this answer and see if it works for you?

Thanks Mike for the link.  Using git bash I can run: ssh "git-upload-pack *****" but then at the end I get the below.  Since I'm getting output from that, I'm assuming this means my ssh key and openSSH are working properly?  any ideas what the last 4 digits of my error "logg" are referring to?  In the link you provided, I couldn't find anyone else getting those last 4 digits of "logg".

$ ssh "******"
00caad7297471a4b7caa250c475fdb7188f82e4fdefb HEADmulti_ack thin-pack side-band s ide-band-64k ofs-delta shallow no-progress include-tag multi_ack_detailed symref =HEAD:refs/heads/master agent=git/2.10.5
0040d54bd821d79a4672dfa880f242c2c8a295086d99 refs/heads/DWH-393
0040e0886a966a65f676f5c7eae4e1131352522e7299 refs/heads/DWH-411
003ff2a14f613d2d21d1a829135e2ecf7674d339a9d0 refs/heads/Mashup
00409d59e733c6a6d07aeb39c1175a58665d1ff38bf1 refs/heads/RPT-573
004fdc0bb53d38c23fd4e770a12ecf56a7dccbdde5af refs/heads/RPT-588-
003fad7297471a4b7caa250c475fdb7188f82e4fdefb refs/heads/master

Curious if you ever solved this... struggling against this exact same thing right now.

Like CreativeWarlock likes this

It appears ( downgrading to 3.4.7 is the preferred solution.  I had hoped Atlassian would have resolved this by now.  Just testing 3.4.12 and still getting the issue if I use their GUI.  (command line works fine for me.)

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events