git on Windows: fatal: protocol error: bad line character: @-

Question

I was using SourceTree + Git on Windows without any problem. I was able to use git commands from command (terminal/BASH). I prefer to use terminal for git push/pull etc. Unfortunately, after reinstallation of my machine (server/git are the same), I'm getting this painful error.

On a new machine, I installed Git 1.9.5 (Git-1.9.5-preview20141217.exe) and configured to use BASH only and plink with proper SSH key file.

I can do git log on my repository, but git pull or git push gives this error:

me@NEW-MACHINE /c/Workspace/project (master)
$ git pull
fatal: protocol error: bad line length character:
@-

ERROR: Problem parsing the command line arguments.

Of course, I searched many articles related to "fatal: protocol error: bad line length character". But, couldn't find any clue.

Interestingly, on SourceTree, I can do git pull or push successfully. I'm only getting this error in BASH terminal. Note that SourceTree doesn't use embedded git.

Here are my investigations so far:

I installed an older version of git (1.8.x), still getting error.
Moved .bashrc, but no good.
Obviously, not a problem of SourceTree as SourceTree doesn't use embedded Git.
The server is in Github (enterprise, private).
I have no problem using any git commands on my Linux with the same git repository/server.

My clue is <newline>@-<newline> from the error message. It is more like a problem of Windows/BASH-specific problem. I can't figure it out what causes "@-".

Edit: I tried suggestions in this thread, but didn't solve my problem. The git server is github.mycompany.com, which doesn't allow any ssh connection.

possible duplicate of [Git Remote: Error: fatal: protocol error: bad line length character: Unab](http://stackoverflow.com/questions/8170436/git-remote-error-fatal-protocol-error-bad-line-length-character-unab) — Etan Reisner, Feb 03 '15 at 02:59
I tried the answers in that thread, but didn't work. Edited question. — Nullptr, Feb 03 '15 at 03:08
What connection method are you using to that server? http(s)? — Etan Reisner, Feb 03 '15 at 03:17
Probably https. It is an enterprise Github. The interface is pretty much the same with public Github. — Nullptr, Feb 03 '15 at 05:31
Don't "probably" your answer. Check your git configuration for that remote. What does it say? — Etan Reisner, Feb 03 '15 at 13:19
What (exactly) is the [complete] command you are using for `git pull`? What is the result of `git remote -v`?` I **strongly** suspect the `@` is in [one of] your git remotes. — Thom Parkin, Feb 10 '15 at 13:56

score 1 · Answer 1 · answered Feb 13 '15 at 21:50

You can circumvent the bash-ssh issue entirely by:

launching a DOS shell with git-cmd.bat (packaged within your Git for Windows msysgit distribution)
using git clone to make a new clone using the proper https url of your remote repo.

That is:

git clone https://<yourAccount>@github.mycompany.com/<yourAccount>/<yourRepo>

Since you will be using in this case the https protocol, there won't be any shell session during a git pull (as opposed to the ssh protocol: see The Smart Protocols), and you shouldn't see any extra message like fatal: protocol error: bad line length character.

score 0 · Answer 2 · answered Jun 21 '16 at 20:38

0

I had same issue for git in windows. Load your public/private key by Pageant App (Putty Authentication Agent). add private/public key.

answered Jun 21 '16 at 20:38

dityagow

69
12

git on Windows: fatal: protocol error: bad line character: @-

2 Answers2