git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Unable to push to git server

From
Abraham Zsombor Nagy <abrahamzsombornagy@gmail.com>
Date
Jul 5, 2024, 09:07 UTC
Message-ID
<CANoqcKaPhAfp1733a3M5P2sMQa8Wr_Ezpje6-ANzE72qUcZ-tA@mail.gmail.com>
In-Reply-To
<ZodRSw9LEwLa_nOG@tapette.crustytoothpaste.net>

On Fri, 5 Jul 2024 at 03:50, brian m. carlson <sandals@crustytoothpaste.net> wrote:

Show 43 quoted lines
>
> On 2024-07-04 at 13:56:15, Abraham Zsombor Nagy wrote:
> > Hello Git Team,
> >
> > I hope you can help me.
> >
> > I'm trying to push my code to GitHub, however I'm unable to do so:
> >
> > abris@dell:~/Projects/maradandohalo/server$ git push --set-upstream origin main
> > Username for 'https://github.com': nazsombor
> > Password for 'https://nazsombor@github.com':
> > fatal: protocol error: bad line length 175
> > send-pack: unexpected disconnect while reading sideband packet
> > error: failed to push some refs to
> > 'https://github.com/nazsombor/maradandohalo.git'
> > Enumerating objects: 31, done.
> > Counting objects: 100% (31/31), done.
> > Delta compression using up to 16 threads
> > Compressing objects: 100% (22/22), done.
> >
> > I use Debian 12. I tried this with the git installed via apt as well
> > with the git compiled from source code. Git version: 2.45.GIT
> >
> > I also asked this question first on StackOverflow:
> > https://stackoverflow.com/questions/78670914/git-fatal-protocol-error-bad-line-length-173
>
> I know you've got this working with SSH, but I'll just mention that
> usually this message "protocol error: bad line length" means that you
> have some sort of proxy (such as an antivirus or a TLS-intercepting
> device) that's tampering with the data.  TLS, which is the protocol used
> for encryption on HTTPS URLs, has built-in mechanisms to detect any sort
> of accidental or intentional modification of the data, so if we assume
> that both your version of Git and GitHub sent valid protocol data, then
> this means that if it came out bad on the other side, it was tampered
> with in the middle by something that can decrypt the data (which would
> have to be something trusted by your machine).
>
> That's why SSH works for you: because the types of proxies that
> typically know how to process HTTPS data don't know how to decrypt or
> intercept SSH connections, so your data doesn't get corrupted.
> --
> brian m. carlson (they/them or he/him)
> Toronto, Ontario, CA
Thank you Brian,

I cannot think of anything, I'm just behind my home network, I don't have a dedicated firewall or proxy. Pushing via https works on Windows on the same laptop. So I guess it's something in my Linux env. I don't know if it matters, but cloning worked out of the box on Linux.

Sincerely, Abraham

Previous: brian m. carlsonNext: rsbecker@nexbridge.com
Message 4 of 6 in “Unable to push to git server”
  1. Abraham Zsombor NagyJul 4, 2024
  2. rsbecker@nexbridge.comJul 4, 2024
  3. brian m. carlsonJul 5, 2024
  4. Abraham Zsombor NagyJul 5, 2024
  5. rsbecker@nexbridge.comJul 4, 2024
  6. Abraham Zsombor NagyJul 4, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.