Protocol Error Bad Line Length Character Prag
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the git clone fatal: protocol error: bad line length character: no s workings and policies of this site About Us Learn more about Stack fatal protocol error bad line length character do Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs fatal protocol error bad line length character gitlab Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join
Heroku Fatal Protocol Error Bad Line Length Character Erro
them; it only takes a minute: Sign up Git Remote: Error: fatal: protocol error: bad line length character: Unab up vote 40 down vote favorite 5 I set up a git server and want now to push initially my repo from the client. I used git push origin master and get this error message: fatal: protocol error: bad line length fatal: protocol error: bad line length character: unab character: Unab I don't know what's wrong. I don't know what "Unab" is. I tried tu resize the shell but it is still "Unab". I cannot find a solution for this error message. I setup the server with "authorized_keys" and SSH. (I can connect to it, using SSH.) It seems to be a git problem? BTW: The server is set up in a Windows 7 VM git ssh authorized-keys share|improve this question edited Jan 19 '15 at 13:34 mstrap 7,11152754 asked Nov 17 '11 at 16:11 user437899 2,55883463 add a comment| 15 Answers 15 active oldest votes up vote 52 down vote accepted The complaint is actually that the remote didn't reply with a proper git response - ie, there's a problem on the server running . (The first four bytes should be the line length - instead, they were the characters Unab... probably an error message of some kind.) What happens when you run ssh
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and git protocol error bad line length character git@ policies of this site About Us Learn more about Stack Overflow the
Fatal: Protocol Error: Bad Line Length Character: Inva
company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags
"fatal: Protocol Error: Bad Line Length Character: Usin"
Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only http://stackoverflow.com/questions/8170436/git-remote-error-fatal-protocol-error-bad-line-length-character-unab takes a minute: Sign up Strange error in gitlab: fatal: protocol error: bad line length character: Depl up vote 7 down vote favorite 2 On one of my servers, when I'm try to pull/ls-remote fresh-created repo on gitlab, I'm getting these error: git ls-remote git@gitlab.com:mas-vem/dinnerdelivery.git fatal: protocol error: bad line length character: Depl If I'm trying to ls-remote one of earliest http://stackoverflow.com/questions/28700988/strange-error-in-gitlab-fatal-protocol-error-bad-line-length-character-depl created repositories, all is fine. When I'm run this command: ssh git@gitlab.com git-receive-pack mas-vem/dinnerdelivery.git I'm getting this error: Deploy key not allowed to push But I doesn't want to push =/ What it could be? Does it is gitlab issue or error on my side? git gitlab share|improve this question edited Jun 8 '15 at 0:38 asked Feb 24 '15 at 16:23 Drakmail 3881417 possible duplicate of Git Remote: Error: fatal: protocol error: bad line length character: Unab –Edward Thomson Feb 24 '15 at 16:25 add a comment| 5 Answers 5 active oldest votes up vote 10 down vote accepted Found what is was problem: I just forgot to add deploy key to repo =/ After that issue was solved. share|improve this answer answered Feb 24 '15 at 16:25 Drakmail 3881417 1 Yes, same here. I wish this error was a bit more descriptive. –Kurt Mueller Apr 9 '15 at 14:33 1 Yes, same here. Weird error. –Klodoma Jun 1 '15 at 12:57 add a comment| up vote 9 down vote Just for other users reference:
Berners-LeeW3C/MITY. Lafon, EditorW3CJ. F. Reschke, EditorgreenbytesJune 2007Hypertext Transfer Protocol -- HTTP/1.1draft-lafon-rfc2616bis-03Status of this MemoBy submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, https://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html and any of which he or she becomes aware will be disclosed, http://pvoutput.org/help.html in accordance with Section 6 of BCP 79.Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, protocol error or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress".The list of current Internet-Drafts can be accessed at
remote host or network may be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 24 Oct 2016 18:07:07 GMT by s_wx1196 (squid/3.5.20)