Git Ssh Fatal Protocol Error Bad Line Length Character
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might
Fatal: Protocol Error: Bad Line Length Character: Git@
have Meta Discuss the workings and policies of this site About fatal: protocol error: bad line length character: logi Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads
"fatal: Protocol Error: Bad Line Length Character:
with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million fatal protocol error bad line length character gitlab programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Git push results in fatal: protocol error: bad line length character: This up vote 25 down vote favorite 4 I am trying to get GitLab working on my server (running CentOS 6.5). I followed the gitlab-receipe to the line, but fatal: protocol error: bad line length character: unab I just can't get it working. I am able to access the web interface, create new projects but pushing to the master branch returns the following error : fatal: protocol error: bad line length character: This I have done checks on the production environment, here are the results : Checking Environment ... Git configured for git user? ... yes Checking Environment ... Finished Checking GitLab Shell ... GitLab Shell version >= 1.7.9 ? ... OK (1.8.0) Repo base directory exists? ... yes Repo base directory is a symlink? ... no Repo base owned by git:git? ... yes Repo base access is drwxrws---? ... yes update hook up-to-date? ... yes update hooks in repos are links: ... ASC / Wiki ... repository is empty Running /home/git/gitlab-shell/bin/check Check GitLab API access: OK Check directories and files: /home/git/repositories: OK /home/git/.ssh/authorized_keys: OK Test redis-cli executable: redis-cli 2.4.10 Send ping to redis server: PONG gitlab-shell self-check successful Checking GitLab Shell ... Finished Checking Sidekiq ... Running? ... yes Nu
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta
Heroku Fatal: Protocol Error: Bad Line Length Character: Erro
Discuss the workings and policies of this site About Us Learn more git protocol error bad line length character git@ about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack
Fatal: Protocol Error: Bad Line Length Character: Inva
Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping http://stackoverflow.com/questions/22314298/git-push-results-in-fatal-protocol-error-bad-line-length-character-this each other. Join them; it only takes a minute: Sign up Git fails with “fatal: protocol error: bad line length character: Pass” 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 http://stackoverflow.com/questions/35509886/git-fails-with-fatal-protocol-error-bad-line-length-character-pass 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 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| Did you find this question interesting? Try our newsletter Sign up for our newsletter and get our top new questions delivered to your inbox (see an example). Subscribed! Success! Please click the link in the confirmation email to activate your subscription. 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 Faceboo
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 http://stackoverflow.com/questions/28700988/strange-error-in-gitlab-fatal-protocol-error-bad-line-length-character-depl About Us Learn more 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 https://answers.atlassian.com/questions/33144840/sourcetree-cant-push-fatal-protocol-error-bad-line-length-character-do the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Strange error in gitlab: protocol error 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 created repositories, all is fine. When I'm run this command: ssh git@gitlab.com git-receive-pack bad line length 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: 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 ca
push: "fatal: protocol error: bad line length character: