git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git send-pack: protocol error: bad band #50

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Apr 11, 2013, 18:37 UTC
Message-ID
<20130411183758.GL27070@google.com>
In-Reply-To
<51665D08.3030307@netcabo.pt>
Hello,
João Joyce wrote:
> I am not sure this is the right place to ask this.
You're in the right place.
[...]
Show 7 quoted lines
> I am trying to push some files to a server with git push. I have
> configured the server to push the files:
>     git remote set-url test ssh://user@location.com:2200/fullpath/
>
> but I am getting the following error:
>     git send-pack: protocol error: bad band #50
>     fatal: The remote end hung up unexpectedly

That means that where git expected to read a binary sideband number, it instead received the byte \x32 (ASCII '2').

Without more details, it's hard to debug this further. Can you get a trace of the communication by setting the envvar GIT_TRACE_PACKET=/tmp/log on the client?

Thanks and hope that helps, Jonathan

Previous: Konstantin KhomoutovNext: João Joyce
Message 3 of 6 in “git send-pack: protocol error: bad band #50”
  1. João JoyceApr 11, 2013
  2. Konstantin KhomoutovApr 11, 2013
  3. Jonathan NiederApr 11, 2013
  4. João JoyceApr 11, 2013
  5. Fwd: Re: git send-pack: protocol error: bad band #50João Joyce, Apr 13, 2013
  6. Jeff KingApr 15, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.