Protocol Error Bad Line Length Character Fata
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this fatal: protocol error: bad line length character: logi site About Us Learn more about Stack Overflow the company Business Learn more
Fatal: Protocol Error: Bad Line Length Character: Git@
about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss
Fatal Protocol Error Bad Line Length Character Do
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 takes a minute: Sign up Git Remote: Error:
Fatal Protocol Error Bad Line Length Character Gitlab
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 character: Unab I don't know what's wrong. I don't know what "Unab" is. I tried fatal: protocol error: bad line length character: unab 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 policies of this site About Us Learn more about Stack Overflow the company Business Learn more about heroku fatal protocol error bad line length character erro hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges git protocol error bad line length character git@ Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each fatal: protocol error: bad line length character: inva other. Join them; it only 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 http://stackoverflow.com/questions/8170436/git-remote-error-fatal-protocol-error-bad-line-length-character-unab 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 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 http://stackoverflow.com/questions/28700988/strange-error-in-gitlab-fatal-protocol-error-bad-line-length-character-depl 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: fatal: protocol error: bad line length character: no s can be a truncated answer for "No such project". As in my case, this kind of error can be fixed by adding user (even yourself) to the project in gitlab: https://gitlab.com/username/your_project/project_members also, ensure your public key is set in your user "Profile settings" > SSH Key or in Project > Settings > Deploy Keys share|improve this answer answered Apr 16 '15 at 8:48 Angelo Maragna 913 2 Thanks, this was my problem. It happened because I moved the project to another namespace. Does anyone know why the error messages get truncated? –ihaz
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more http://stackoverflow.com/questions/35509886/git-fails-with-fatal-protocol-error-bad-line-length-character-pass about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack https://github.com/yongjhih/docker-parse-server/issues/10 Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Git fails with “fatal: protocol error: bad line length character: Pass” protocol error up vote 2 down vote favorite All git commands requiring access to the remote repository fail with the error message: fatal: protocol error: bad line length character: Pass They used to work a few days ago. git ssh share|improve this question asked Feb 19 at 16:18 Ignitor 1,4461431 1 Possible duplicate of Git Remote: Error: fatal: protocol error: bad line length character: Unab –Edward Thomson Jul 8 at bad line length 23:36 add a comment| 2 Answers 2 active oldest votes up vote 4 down vote accepted The problem was that my ssh key agent (Pageant) wasn't running. share|improve this answer answered Feb 19 at 16:18 Ignitor 1,4461431 add a comment| up vote 0 down vote Had a similarly issue while setting up aws codecommit, I need to add the .ppk to pageant. share|improve this answer answered Jul 8 at 22:36 Nick Cordova 132 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer you're looking for? Browse other questions tagged git ssh or ask your own question. asked 8 months ago viewed 222 times active 3 months ago Blog Stack Overflow Podcast #92 - The Guerilla Guide to Interviewing Linked 40 Git Remote: Error: fatal: protocol error: bad line length character: Unab Related 1git push returns “fatal: protocol error: bad line length character”40Git Remote: Error: fatal: protocol error: bad line length character: Unab8fatal: protocol error
Sign in Pricing Blog Support Search GitHub This repository Watch 16 Star 201 Fork 79 yongjhih/docker-parse-server Code Issues 19 Pull requests 0 Projects 0 Pulse Graphs New issue clone error, fatal: protocol error: bad line length character: The #10 Open oblank opened this Issue Feb 29, 2016 · 4 comments Projects None yet Labels bug help wanted question Milestone No milestone Assignees No one assigned 2 participants oblank commented Feb 29, 2016 ➜ git clone ssh://git@121.xx.xxx.5/parse-cloud-code Cloning into 'parse-cloud-code'... fatal: protocol error: bad line length character: The ssh -T git@121.xx.xxx.5 -p 2022 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. I change repository URL to git@121.xx.xxx.5:2022/parse-cloud-code , no prefix ssh:// git clone git@121.xx.xxx.5:2022/parse-cloud-code Cloning into 'parse-cloud-code'... FATAL: R any 2022/parse-cloud-code oblank DENIED by fallthru (or you mis-spelled the reponame) fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Owner yongjhih commented Feb 29, 2016 Did you try the following commands? $ docker exec -i parse-server ssh-add-key < ~/.ssh/id_rsa.pub # add ssh-key for auth $ git clone ssh://git@localhost:2022/parse-cloud-code # clone via specific port of ssh yongjhih added the question label Feb 29, 2016 oblank commented Mar 1, 2016 yes, but useless the difference is my docker instance is running on a remote server, and ssh-key is my local Mac's git command be run on my local machine. Owner yongjhih commented Mar 1, 2016 Steps of git deploy on remote: Generate Mac's ssh k