Protocol Error Bad Line Length Character Error
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 git clone fatal: protocol error: bad line length character: of this site About Us Learn more about Stack Overflow the company fatal protocol error bad line length character pass Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges
Fatal: Protocol Error: Bad Line Length Character: Logi
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 takes a
Fatal: Protocol Error: Bad Line Length Character: Git@
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 new projects but pushing fatal protocol error bad line length character do 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 Database is SQLite ... no All migrations up? ...
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings
Fatal Protocol Error Bad Line Length Character Gitlab
and policies of this site About Us Learn more about Stack Overflow fatal: protocol error: bad line length character: unab the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags heroku "fatal: protocol error: bad line length character: erro" 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/22314298/git-push-results-in-fatal-protocol-error-bad-line-length-character-this takes a minute: Sign up Error: protocol error: bad line length character: erro up vote 1 down vote favorite Tried to push to my GitHub URL and it gives me this weird error. I don't see anyone else having this error. I can pull from my git directory but not push. github git-bash share|improve this question edited May 23 '15 http://stackoverflow.com/questions/30375554/error-protocol-error-bad-line-length-character-erro at 9:33 Anthon 12.2k124378 asked May 21 '15 at 13:43 Zachary Adams 123 Did you see stackoverflow.com/questions/22314298/… or stackoverflow.com/questions/8170436/… ? –Luke May 21 '15 at 13:46 Expressing your hope for help should never be part of your question. No distractions, no chit-chat (read help→tour) –Anthon May 23 '15 at 9:33 add a comment| active oldest votes Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook. 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. Browse other questions tagged github git-bash or ask your own question. asked 1 year ago viewed 298 times Blog Stack Overflow Podcast #92 - The Guerilla Guide to Interviewing Linked 40 Git Remote: Error: fatal: protocol error: bad line length character: Unab 25 Git push results in fatal: protocol er
Sign in Pricing Blog Support Search GitHub This repository Watch 1,019 Star 18,587 Fork 5,079 gitlabhq/gitlabhq Code Issues 1 Pull requests 0 Projects https://github.com/gitlabhq/gitlabhq/issues/6537 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 https://answers.atlassian.com/questions/33144840/sourcetree-cant-push-fatal-protocol-error-bad-line-length-character-do 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 protocol error 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 bad line length 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: signatur
push: "fatal: protocol error: bad line length character: