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

[Jay Heath]

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@bitbucket.org "git-upload-pack ...".  But didn't seem to show anything helpful to this error.  Anyone have any ideas?

[Mike Corsaro]

Hello!

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?

[Jay Heath]

Thanks Mike for the link.  Using git bash I can run: ssh git@bitbucket.org "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 git@bitbucket.org "******"
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
0000

[cgoodwin]

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

[Rick Runowski]

It appears (https://community.atlassian.com/t5/Sourcetree-questions/Bad-line-length-character-after-updating-to-Sourcetree-3-4-8/qaq-p/1967945) 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.)