Error message after successfully pushing to Heroku

Question

remote: Verifying deploy... done.
fatal: protocol error: bad line length character: fata
error: error in sideband demultiplexer

This just randomly started showing up. My changes are being saved in git and pushing successfully to Heroku. I have no idea what this means or what caused it as I have not done anything new at all.

We're seeing the same thing in our Heroku deploys since today. All from build servers where we didn't change any deployment configuration. Think I'm gonna open a Heroku support issue for this one. — NickDK, Mar 21 '16 at 12:46
please let me know if you figure anything out. I am also starting to occasionally get strange errors were my push to heroku fails and then when I push it again it will work. example: `remote: error: cannot lock ref 'refs/heads/master': ref refs/heads/master is at ae943f5f0b6bd283ds486ab6e9676ae973194a70a but expected 69e4ee4446428e4cef84756ff6381ae64e7ea1a24ff5c69` — Timmy Von Heiss, Mar 23 '16 at 01:54
The error messages disappeared today. I did not do anything. — Timmy Von Heiss, Mar 25 '16 at 05:48

score 37 · Answer 1 · answered Jan 16 '20 at 11:04

37

Just had this issue myself. What worked for me was this response directly from Heroku Support

$ Upgrade GIT on your local machine
$ heroku plugins:install heroku-repo
$ heroku repo:reset -a <app-name>
$ git commit --allow-empty -m "Reset repo"
$ git push heroku master

answered Jan 16 '20 at 11:04

IT_puppet_master

702
5
20

1

Just the last 3 steps worked for me (reset and repush) – gwalshington Mar 10 '20 at 21:48
When I try running this I get `Warning: repo:reset is not a heroku command.` – MalcolmOcean Mar 17 '20 at 20:59
I tried upgrading my heroku version and this didn't help. I'm using 7.39 from a couple weeks ago – MalcolmOcean Mar 17 '20 at 21:07
MalcolmOcean - be sure to `heroku plugins:install heroku-repo` first – Mark Swardstrom Mar 27 '20 at 15:57
As an aside - for us it worked to simply reset the repo (`heroku repo:reset`) and then push from our CI tool again. – nicohvi Apr 16 '20 at 08:54
haha took me a year to get back to this but indeed I was missing the `heroku plugins:install heroku-repo` bit – MalcolmOcean Apr 24 '21 at 02:50
The commit history will be gone. Isn't it bad? – Smart Manoj Sep 13 '21 at 13:02
@SmartManoj. No, only resets Heroku repo. Your GitHub/BitBucket/Local Git server will be unaffected, other than 1 empty commit added, needed to trick Heroku into deploy again. – IT_puppet_master Sep 14 '21 at 14:05
What if one use only heroku git? – Smart Manoj Sep 15 '21 at 05:16

score 4 · Accepted Answer · answered Apr 25 '19 at 11:53

Having spoken to Heroku support recently regarding this, you can pass the below environment variables when pushing to your Heroku remote to reveal more about what's going on:

GIT_CURL_VERBOSE=1 GIT_TRACE=1 git push https://heroku:key@git.heroku.com/app-name.git develop:develop

score 0 · Answer 3 · edited May 23 '17 at 10:30

There is a problem on the server.
Your remote git server didn't reply with the expected git response.

First of all check your server .bashrc file. It might print error or there is a syntax problem with it.

Possible related questions:

https://askubuntu.com/questions/210381/git-fatal-protocol-error-bad-line-length-character-ssh

Git push results in fatal: protocol error: bad line length character: This

Strange error in gitlab: fatal: protocol error: bad line length character: Depl

score 0 · Answer 4 · answered Apr 28 '16 at 05:11

0

This was resolved by Heroku and was apparently an error on their end.

answered Apr 28 '16 at 05:11

Timmy Von Heiss

2,160
17
39

2

This is not always the case - I would mark an answer that has some helpful content – adaam Apr 30 '19 at 10:48

score 0 · Answer 5 · answered Jan 09 '20 at 20:57

0

Cleaning the heroku repo and then pushing again from scratch did the trick for me.

https://stackoverflow.com/a/37925714

answered Jan 09 '20 at 20:57

AndresSRG

89
1
3

The commit history will be gone. Isn't it bad? – – Smart Manoj Sep 13 '21 at 13:02

Error message after successfully pushing to Heroku

5 Answers5