Git Protocol Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings git protocol error bad line length character git@ 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 Questions Jobs Documentation
Fatal Protocol Error Bad Line Length Character Do
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 each other. Join them; it
Fatal Protocol Error Bad Line Length Character Gitlab
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 I just can't get it working. I am able to access the web interface, create fatal: protocol error: bad line length character: unab 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 Number of Sidekiq processes ... 1 Checking Sidekiq ... Finished Checking LDAP ... LDAP is disabled in config/gitlab.yml Checking LDAP ... Finished Checking GitLab ... Database config exists? ... yes Datab
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 heroku fatal: protocol error: bad line length character: erro company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions fatal: protocol error: bad line length character: inva 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: usin" programmers, just like you, helping each other. Join them; it only takes a minute: Sign up fatal: protocol error: bad line length character: You up vote 0 down vote favorite I'm on Ubuntu. I didn't have any http://stackoverflow.com/questions/22314298/git-push-results-in-fatal-protocol-error-bad-line-length-character-this issues with git but out of the blue I start seeing this error for any remote git operations like git pull, push etc. Searched the other posts on this and when I ran ssh git@hostname git-upload-pack '/path_to_your_repo' I got-" You don't have access." Any pointers? git share|improve this question asked Mar 19 '15 at 5:55 Raj 6927 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote The error http://stackoverflow.com/questions/29138069/fatal-protocol-error-bad-line-length-character-you you get is pretty common, namely: fatal: protocol error: bad line length character: This This is due to of problems with the Shell access (is the access allowed?) on the server.. Perhaps this link would be of any help: Git Remote: Error: fatal: protocol error: bad line length character: Unab. It seems related. I hope it helps! share|improve this answer answered Mar 19 '15 at 5:59 Joey Dorrani 25711 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 or ask your own question. asked 1 year ago viewed 2355 times active 1 year ago Linked 40 Git Remote: Error: fatal: protocol error: bad line length character: Unab Related 855Git for beginners: The definitive practical guide2002How do you create a remote Git branch?1git push returns “fatal: protocol error: bad line length character”870Push a tag to a remote repository using Git?849How can I reconcile detached HEAD with master/origin?909Git fetch remote branch0fatal: protocol error: bad line length character: Plea3git on Windows: fatal: protocol e
Merge Requests 2 Network Create a new issue Commits Issue Boards Closed Open Issue #35 opened 2015-03-06 17:41:25 UTC by https://gitlab.com/gitlab-org/gitlab-development-kit/issues/35 svenglar@svenglar Can't push or pull from my private repository When issuing https://github.com/gitlabhq/gitlabhq/issues/6537 a git pull or git push, I see: fatal: protocol error: bad line length character: No s My remotes are setup just as they were a few days ago when I wasn't seeing this issue: origin git@gitlab.com:svenglar/home.git (fetch) origin git@gitlab.com:svenglar/home.git (push) A run of ssh git@gitlab.com protocol error git-receive-pack svenglar/home.git shows: no such project When issuing a `git pull` or `git push`, I see: ``` fatal: protocol error: bad line length character: No s ``` My remotes are setup just as they were a few days ago when I wasn't seeing this issue: ``` origin git@gitlab.com:svenglar/home.git (fetch) origin git@gitlab.com:svenglar/home.git (push) ``` A bad line length run of `ssh git@gitlab.com git-receive-pack svenglar/home.git` shows: ``` no such project ``` Edited 2015-03-12 16:50:22 UTC 0 0 William Huart @quantumotter commented 2015-03-12 16:47:56 UTC For what it's worth: I could pull the project but got this very same error when pushing. After pushing rights have been granted to my account I finally could push svenglar @svenglar commented 2015-03-12 16:50:22 UTC Turns out I just had an issue with choosing the correct SSH key when using git. I needed to 'ssh-add' my gitlab specific private key. This was a non-issue... just user error. svenglar @svenglar 2015-03-12 16:50:22 UTC Status changed to closed Tobias Munk @schmunk commented 2015-04-02 16:07:48 UTC I got the same error fatal: protocol error: bad line length character: No s when misspelling a repo name. Please sign up or sign in to post a comment Assignee No assignee Select assigneeAssign to None Milestone None MilestoneAssign milestone None Due date No
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 0 Pulse Graphs New issue git pull/push/clone error "fatal: protocol error: bad line length character: Welc" #6537 Closed renanvaz opened this Issue Mar 15, 2014 · 24 comments Projects None 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, 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 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 corre