git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: "'Abraham Zsombor Nagy'" <abrahamzsombornagy@gmail.com>
Cc: <git@vger.kernel.org>
Subject: RE: Unable to push to git server
Date: Thu, 4 Jul 2024 12:33:26 -0400	[thread overview]
Message-ID: <090401dace2f$e88a1840$b99e48c0$@nexbridge.com> (raw)
In-Reply-To: <CANoqcKasK6UOqa8YNKkqR+ZmizbMwP+Q9j0Yiid-mrUuXHQeew@mail.gmail.com>

Glad to help.
(Adding the original recipients back in for archive purposes).

From: Abraham Zsombor Nagy <abrahamzsombornagy@gmail.com> 
Sent: Thursday, July 4, 2024 12:28 PM
To: rsbecker@nexbridge.com
Subject: Re: Unable to push to git server

Thank you Randall, I will contact GitHub to check the issue.
Sincerely,
Abraham

On Thu, Jul 4, 2024, 6:24 PM <mailto:rsbecker@nexbridge.com> wrote:
On Thursday, July 4, 2024 12:05 PM, Abraham Zsombor Nagy wrote:
>Indeed, I got the error with the classic PAT as well as with OAuth authentication
>within Intellij IDEA.
>
>On Thu, 4 Jul 2024 at 17:20, <mailto:rsbecker@nexbridge.com> wrote:
>>
>> On Thursday, July 4, 2024 11:14 AM, Abraham Zsombor Nagy wrote:
>> >Thank you so much, with SSH, I was able to push my code.
>> >On Thu, 4 Jul 2024 at 16:34, <mailto:rsbecker@nexbridge.com> wrote:
>> >>
>> >> On Thursday, July 4, 2024 9:56 AM, Abraham Zsombor Nagy wrote:
>> >> >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-er
>> >> >ror
>> >> >-bad-line-
>> >> >length-173
>> >>
>> >> As far as I know, GitHub changed to use personal access tokens to
>> >> authentication
>> >for HTTPS push rather than password. Have you tried SSH?
>>
>> That's good but we need to understand what is going on with HTTPS. Try to create
>a PAT and try that.

I would suggest contacting GitHub and Intellij. This may also be a possible firewall/proxy issue in your environment. I may be wrong here (someone else chime in please) but this is not looking like it is caused directly by git. Part of this may be the communication protocol you selected in Intellij or a TLS compatibility issue between your machine and GitHub. There are some articles at StackOverflow discussing this error that may be helpful.


  parent reply	other threads:[~2024-07-04 16:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04 13:56 Unable to push to git server Abraham Zsombor Nagy
2024-07-04 14:33 ` rsbecker
     [not found]   ` <CANoqcKZtOwghKGaUBfS_JnL4mBKsD9+=S1EX8J=rtVW4OUqjOQ@mail.gmail.com>
     [not found]     ` <08ee01dace25$b87cf640$2976e2c0$@nexbridge.com>
     [not found]       ` <CANoqcKZ8ABFQrfakK0MRbrgf-ipm4mPGHkvpFQ_Kg_mmn+F_JQ@mail.gmail.com>
     [not found]         ` <08f101dace2e$adadffd0$0909ff70$@nexbridge.com>
     [not found]           ` <CANoqcKasK6UOqa8YNKkqR+ZmizbMwP+Q9j0Yiid-mrUuXHQeew@mail.gmail.com>
2024-07-04 16:33             ` rsbecker [this message]
2024-07-04 17:02               ` Abraham Zsombor Nagy
2024-07-05  1:50 ` brian m. carlson
2024-07-05  9:07   ` Abraham Zsombor Nagy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='090401dace2f$e88a1840$b99e48c0$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=abrahamzsombornagy@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).