Git Clone Protocol Error Bad Line Length Character
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 site About Us Learn more about Stack Overflow fatal: protocol error: bad line length character: logi the company Business Learn more about hiring developers or posting ads with us Stack Overflow
Fatal: Protocol Error: Bad Line Length Character:
Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7
Fatal Protocol Error Bad Line Length Character Gitlab
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: Unab up vote 40 down vote favorite 5 I
Fatal: Protocol Error: Bad Line Length Character: Unab
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 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" git protocol error bad line length character git@ 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,06652754 asked Nov 17 '11 at 16:11 user437899 2,54383462 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
Sign in Pricing Blog Support Search GitHub This repository Watch 1,016 Star 18,565 Fork 5,077 gitlabhq/gitlabhq Code Issues 0 Pull requests 0 Projects heroku fatal: protocol error: bad line length character: erro 0 Pulse Graphs New issue git pull/push/clone error "fatal: protocol error: bad fatal: protocol error: bad line length character: inva line length character: Welc" #6537 Closed renanvaz opened this Issue Mar 15, 2014 · 24 comments Projects None "fatal: protocol error: bad line length character: usin" yet Labels None yet Milestone No milestone Assignees No one assigned 6 participants renanvaz commented Mar 15, 2014 Dear, I have a error in my gitlab instalation, http://stackoverflow.com/questions/8170436/git-remote-error-fatal-protocol-error-bad-line-length-character-unab can you help me? I think the error is that the welcome message to the user git on ssh should not be this "Welcome to Ubuntu 13.10 (GNU / Linux 3.11.0-12-generic x86_64) ..." but I can not say what should be. Info: My SSH keys are added. In my repository: $ git remote add origin ssh://git@gitlab.XXXXX.XX:2222/root/luver-bootstrap.git $ git push https://github.com/gitlabhq/gitlabhq/issues/6537 origin master fatal: protocol error: bad line length character: Welc Debug: $ ssh -vT git@gitlab.XXXXX.XX -p 2222 OpenSSH_6.2p2 Ubuntu-6ubuntu0.1, OpenSSL 1.0.1e 11 Feb 2013 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to gitlab.XXXXX.XXX [162.XXX.XXX.XX] port 2222. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/id_rsa type 1 debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048 debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048 debug1: identity file /root/.ssh/id_rsa-cert type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: identity file /root/.ssh/id_dsa-cert type -1 debug1: identity file /root/.ssh/id_ecdsa type -1 debug1: identity file /root/.ssh/id_ecdsa-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.2p2 Ubuntu-6ubuntu0.1 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.2p2 Ubuntu-6ubuntu0.1 debug1: match: OpenSSH_6.2p2 Ubuntu-6ubuntu0.1 pat OpenSSH* debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5-etm@openssh.com none debug1: kex: client->server aes128-ctr hmac-md5-etm@openssh.com none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ECDSA 77:cf:16:00:2e:39:3d:ef:c8:f5:e7:6c:80:ef:3a:e7 debug1: Host '[gitlab.XXXXX.XX]:2222' is known and matches the ECDSA host key. debug1: Found key in /root/.ssh/known_hosts:1 debug1: ssh_ecdsa_verify: signature correct debug1: SSH2_MSG_NEW
s Does anyone https://forum.gitlab.com/t/fatal-protocol-error-bad-line-length-character-no-s/347 have some suggestions on how to troubleshoot this? axil 2015-03-10 06:29:26 UTC #2 Is this a private repo? Can you post the https://wincent.com/wiki/fatal%3A_protocol_error%3A_bad_line_length_character link to reproduce maybe? etc 2015-03-10 12:59:50 UTC #3 Yes, it was a private repo on gitlab.com. I believe we moved protocol error it to another group, and it seemed to work fine, so I'm not sure if it was just a fluke or what. bhagwatchouhan 2015-05-06 05:45:17 UTC #4 We face this error when we have access lower than Developer. We must have access level bad line length set to at least Dev. axil 2015-05-06 07:25:39 UTC #5 bhagwatchouhan: We face this error when we have access lower than Developer. We must have access level set to at least Dev. Is this on gitlab.com or on your hosted instance? hectorlee369 2015-05-07 15:41:10 UTC #6 I got the same error "Fatal: protocol error: bad line length character: No s" when I tried to push to other user created project on our hosted instance. The project is an internal repo and I can pull it to my client.Then I add member in the project and set project access as Master, everything is fine. Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled What is GitLab? Try it! Download It! Blog Docs