{"thread":{"id":"61734","subject":"Unable to push to git server","startedAt":"2024-07-04T13:56:30Z","lastAt":"2024-07-05T09:08:01Z","messageCount":6,"participants":["Abraham Zsombor Nagy","rsbecker@nexbridge.com","brian m. carlson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"498083","messageId":"CANoqcKYwgA5sT0fAgSp4atpuPOaUSDALRVcf9XoajOe0g6xibQ@mail.gmail.com","threadId":"61734","inReplyTo":null,"subject":"Unable to push to git server","fromName":"Abraham Zsombor Nagy","fromEmail":"abrahamzsombornagy@gmail.com","sentAt":"2024-07-04T13:56:15Z","receivedAt":"2024-07-04T13:56:30Z","isPatch":false,"sender":{"key":"abrahamzsombornagy@gmail.com","avatar":"https://gravatar.com/avatar/526240cb5e61fa8277467e79a81fede017852c2e654ee28067b37647a97d8c87?d=mp&s=160"},"body":"Hello Git Team,\n\nI hope you can help me.\n\nI'm trying to push my code to GitHub, however I'm unable to do so:\n\nabris@dell:~/Projects/maradandohalo/server$ git push --set-upstream origin main\nUsername for 'https://github.com': nazsombor\nPassword for 'https://nazsombor@github.com':\nfatal: protocol error: bad line length 175\nsend-pack: unexpected disconnect while reading sideband packet\nerror: failed to push some refs to\n'https://github.com/nazsombor/maradandohalo.git'\nEnumerating objects: 31, done.\nCounting objects: 100% (31/31), done.\nDelta compression using up to 16 threads\nCompressing objects: 100% (22/22), done.\n\nI use Debian 12. I tried this with the git installed via apt as well\nwith the git compiled from source code. Git version: 2.45.GIT\n\nI also asked this question first on StackOverflow:\nhttps://stackoverflow.com/questions/78670914/git-fatal-protocol-error-bad-line-length-173\n\nThank you for your help.\n\nSincerely,\nAbraham\n"},{"id":"498085","messageId":"08e701dace1f$388be050$a9a3a0f0$@nexbridge.com","threadId":"61734","inReplyTo":"CANoqcKYwgA5sT0fAgSp4atpuPOaUSDALRVcf9XoajOe0g6xibQ@mail.gmail.com","subject":"RE: Unable to push to git server","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2024-07-04T14:33:59Z","receivedAt":"2024-07-04T14:34:13Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On Thursday, July 4, 2024 9:56 AM, Abraham Zsombor Nagy wrote:\n>I'm trying to push my code to GitHub, however I'm unable to do so:\n>\n>abris@dell:~/Projects/maradandohalo/server$ git push --set-upstream origin main\n>Username for 'https://github.com': nazsombor Password for\n>'https://nazsombor@github.com':\n>fatal: protocol error: bad line length 175\n>send-pack: unexpected disconnect while reading sideband packet\n>error: failed to push some refs to\n>'https://github.com/nazsombor/maradandohalo.git'\n>Enumerating objects: 31, done.\n>Counting objects: 100% (31/31), done.\n>Delta compression using up to 16 threads Compressing objects: 100% (22/22),\n>done.\n>\n>I use Debian 12. I tried this with the git installed via apt as well with the git compiled\n>from source code. Git version: 2.45.GIT\n>\n>I also asked this question first on StackOverflow:\n>https://stackoverflow.com/questions/78670914/git-fatal-protocol-error-bad-line-\n>length-173\n\nAs far as I know, GitHub changed to use personal access tokens to authentication for HTTPS push rather than password. Have you tried SSH?\n--Randall\n\n"},{"id":"498086","messageId":"090401dace2f$e88a1840$b99e48c0$@nexbridge.com","threadId":"61734","inReplyTo":"CANoqcKasK6UOqa8YNKkqR+ZmizbMwP+Q9j0Yiid-mrUuXHQeew@mail.gmail.com","subject":"RE: Unable to push to git server","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2024-07-04T16:33:26Z","receivedAt":"2024-07-04T16:33:34Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"Glad to help.\n(Adding the original recipients back in for archive purposes).\n\nFrom: Abraham Zsombor Nagy \nSent: Thursday, July 4, 2024 12:28 PM\nTo: rsbecker@nexbridge.com\nSubject: Re: Unable to push to git server\n\nThank you Randall, I will contact GitHub to check the issue.\nSincerely,\nAbraham\n\nOn Thu, Jul 4, 2024, 6:24 PM wrote:\nOn Thursday, July 4, 2024 12:05 PM, Abraham Zsombor Nagy wrote:\n>Indeed, I got the error with the classic PAT as well as with OAuth authentication\n>within Intellij IDEA.\n>\n>On Thu, 4 Jul 2024 at 17:20, wrote:\n>>\n>> On Thursday, July 4, 2024 11:14 AM, Abraham Zsombor Nagy wrote:\n>> >Thank you so much, with SSH, I was able to push my code.\n>> >On Thu, 4 Jul 2024 at 16:34, wrote:\n>> >>\n>> >> On Thursday, July 4, 2024 9:56 AM, Abraham Zsombor Nagy wrote:\n>> >> >I'm trying to push my code to GitHub, however I'm unable to do so:\n>> >> >\n>> >> >abris@dell:~/Projects/maradandohalo/server$ git push\n>> >> >--set-upstream origin main Username for 'https://github.com':\n>> >> >nazsombor Password for\n>> >> >'https://nazsombor@github.com':\n>> >> >fatal: protocol error: bad line length 175\n>> >> >send-pack: unexpected disconnect while reading sideband packet\n>> >> >error: failed to push some refs to\n>> >> >'https://github.com/nazsombor/maradandohalo.git'\n>> >> >Enumerating objects: 31, done.\n>> >> >Counting objects: 100% (31/31), done.\n>> >> >Delta compression using up to 16 threads Compressing objects: 100%\n>> >> >(22/22), done.\n>> >> >\n>> >> >I use Debian 12. I tried this with the git installed via apt as\n>> >> >well with the git compiled from source code. Git version: 2.45.GIT\n>> >> >\n>> >> >I also asked this question first on StackOverflow:\n>> >> >https://stackoverflow.com/questions/78670914/git-fatal-protocol-er\n>> >> >ror\n>> >> >-bad-line-\n>> >> >length-173\n>> >>\n>> >> As far as I know, GitHub changed to use personal access tokens to\n>> >> authentication\n>> >for HTTPS push rather than password. Have you tried SSH?\n>>\n>> That's good but we need to understand what is going on with HTTPS. Try to create\n>a PAT and try that.\n\nI 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.\n\n"},{"id":"498090","messageId":"CANoqcKZ_7HX_eLe4gytkB0oV1-kf2wU=W6fNqG2yR70BUfU-pg@mail.gmail.com","threadId":"61734","inReplyTo":"090401dace2f$e88a1840$b99e48c0$@nexbridge.com","subject":"Re: Unable to push to git server","fromName":"Abraham Zsombor Nagy","fromEmail":"abrahamzsombornagy@gmail.com","sentAt":"2024-07-04T17:02:22Z","receivedAt":"2024-07-04T17:02:36Z","isPatch":false,"sender":{"key":"abrahamzsombornagy@gmail.com","avatar":"https://gravatar.com/avatar/526240cb5e61fa8277467e79a81fede017852c2e654ee28067b37647a97d8c87?d=mp&s=160"},"body":"On Thu, 4 Jul 2024 at 18:33, wrote:\n>\n> Glad to help.\n> (Adding the original recipients back in for archive purposes).\n>\n> From: Abraham Zsombor Nagy \n> Sent: Thursday, July 4, 2024 12:28 PM\n> To: rsbecker@nexbridge.com\n> Subject: Re: Unable to push to git server\n>\n> Thank you Randall, I will contact GitHub to check the issue.\n> Sincerely,\n> Abraham\n>\n> On Thu, Jul 4, 2024, 6:24 PM wrote:\n> On Thursday, July 4, 2024 12:05 PM, Abraham Zsombor Nagy wrote:\n> >Indeed, I got the error with the classic PAT as well as with OAuth authentication\n> >within Intellij IDEA.\n> >\n> >On Thu, 4 Jul 2024 at 17:20, wrote:\n> >>\n> >> On Thursday, July 4, 2024 11:14 AM, Abraham Zsombor Nagy wrote:\n> >> >Thank you so much, with SSH, I was able to push my code.\n> >> >On Thu, 4 Jul 2024 at 16:34, wrote:\n> >> >>\n> >> >> On Thursday, July 4, 2024 9:56 AM, Abraham Zsombor Nagy wrote:\n> >> >> >I'm trying to push my code to GitHub, however I'm unable to do so:\n> >> >> >\n> >> >> >abris@dell:~/Projects/maradandohalo/server$ git push\n> >> >> >--set-upstream origin main Username for 'https://github.com':\n> >> >> >nazsombor Password for\n> >> >> >'https://nazsombor@github.com':\n> >> >> >fatal: protocol error: bad line length 175\n> >> >> >send-pack: unexpected disconnect while reading sideband packet\n> >> >> >error: failed to push some refs to\n> >> >> >'https://github.com/nazsombor/maradandohalo.git'\n> >> >> >Enumerating objects: 31, done.\n> >> >> >Counting objects: 100% (31/31), done.\n> >> >> >Delta compression using up to 16 threads Compressing objects: 100%\n> >> >> >(22/22), done.\n> >> >> >\n> >> >> >I use Debian 12. I tried this with the git installed via apt as\n> >> >> >well with the git compiled from source code. Git version: 2.45.GIT\n> >> >> >\n> >> >> >I also asked this question first on StackOverflow:\n> >> >> >https://stackoverflow.com/questions/78670914/git-fatal-protocol-er\n> >> >> >ror\n> >> >> >-bad-line-\n> >> >> >length-173\n> >> >>\n> >> >> As far as I know, GitHub changed to use personal access tokens to\n> >> >> authentication\n> >> >for HTTPS push rather than password. Have you tried SSH?\n> >>\n> >> That's good but we need to understand what is going on with HTTPS. Try to create\n> >a PAT and try that.\n>\n> 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.\n>\n\nThank you for the heads up, I will do so.\n"},{"id":"498102","messageId":"ZodRSw9LEwLa_nOG@tapette.crustytoothpaste.net","threadId":"61734","inReplyTo":"CANoqcKYwgA5sT0fAgSp4atpuPOaUSDALRVcf9XoajOe0g6xibQ@mail.gmail.com","subject":"Re: Unable to push to git server","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2024-07-05T01:50:03Z","receivedAt":"2024-07-05T01:50:05Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2024-07-04 at 13:56:15, Abraham Zsombor Nagy wrote:\n> Hello Git Team,\n> \n> I hope you can help me.\n> \n> I'm trying to push my code to GitHub, however I'm unable to do so:\n> \n> abris@dell:~/Projects/maradandohalo/server$ git push --set-upstream origin main\n> Username for 'https://github.com': nazsombor\n> Password for 'https://nazsombor@github.com':\n> fatal: protocol error: bad line length 175\n> send-pack: unexpected disconnect while reading sideband packet\n> error: failed to push some refs to\n> 'https://github.com/nazsombor/maradandohalo.git'\n> Enumerating objects: 31, done.\n> Counting objects: 100% (31/31), done.\n> Delta compression using up to 16 threads\n> Compressing objects: 100% (22/22), done.\n> \n> I use Debian 12. I tried this with the git installed via apt as well\n> with the git compiled from source code. Git version: 2.45.GIT\n> \n> I also asked this question first on StackOverflow:\n> https://stackoverflow.com/questions/78670914/git-fatal-protocol-error-bad-line-length-173\n\nI know you've got this working with SSH, but I'll just mention that\nusually this message \"protocol error: bad line length\" means that you\nhave some sort of proxy (such as an antivirus or a TLS-intercepting\ndevice) that's tampering with the data. TLS, which is the protocol used\nfor encryption on HTTPS URLs, has built-in mechanisms to detect any sort\nof accidental or intentional modification of the data, so if we assume\nthat both your version of Git and GitHub sent valid protocol data, then\nthis means that if it came out bad on the other side, it was tampered\nwith in the middle by something that can decrypt the data (which would\nhave to be something trusted by your machine).\n\nThat's why SSH works for you: because the types of proxies that\ntypically know how to process HTTPS data don't know how to decrypt or\nintercept SSH connections, so your data doesn't get corrupted.\n-- \nbrian m. carlson (they/them or he/him)\nToronto, Ontario, CA\n"},{"id":"498103","messageId":"CANoqcKaPhAfp1733a3M5P2sMQa8Wr_Ezpje6-ANzE72qUcZ-tA@mail.gmail.com","threadId":"61734","inReplyTo":"ZodRSw9LEwLa_nOG@tapette.crustytoothpaste.net","subject":"Re: Unable to push to git server","fromName":"Abraham Zsombor Nagy","fromEmail":"abrahamzsombornagy@gmail.com","sentAt":"2024-07-05T09:07:47Z","receivedAt":"2024-07-05T09:08:01Z","isPatch":false,"sender":{"key":"abrahamzsombornagy@gmail.com","avatar":"https://gravatar.com/avatar/526240cb5e61fa8277467e79a81fede017852c2e654ee28067b37647a97d8c87?d=mp&s=160"},"body":"On Fri, 5 Jul 2024 at 03:50, brian m. carlson\n wrote:\n>\n> On 2024-07-04 at 13:56:15, Abraham Zsombor Nagy wrote:\n> > Hello Git Team,\n> >\n> > I hope you can help me.\n> >\n> > I'm trying to push my code to GitHub, however I'm unable to do so:\n> >\n> > abris@dell:~/Projects/maradandohalo/server$ git push --set-upstream origin main\n> > Username for 'https://github.com': nazsombor\n> > Password for 'https://nazsombor@github.com':\n> > fatal: protocol error: bad line length 175\n> > send-pack: unexpected disconnect while reading sideband packet\n> > error: failed to push some refs to\n> > 'https://github.com/nazsombor/maradandohalo.git'\n> > Enumerating objects: 31, done.\n> > Counting objects: 100% (31/31), done.\n> > Delta compression using up to 16 threads\n> > Compressing objects: 100% (22/22), done.\n> >\n> > I use Debian 12. I tried this with the git installed via apt as well\n> > with the git compiled from source code. Git version: 2.45.GIT\n> >\n> > I also asked this question first on StackOverflow:\n> > https://stackoverflow.com/questions/78670914/git-fatal-protocol-error-bad-line-length-173\n>\n> I know you've got this working with SSH, but I'll just mention that\n> usually this message \"protocol error: bad line length\" means that you\n> have some sort of proxy (such as an antivirus or a TLS-intercepting\n> device) that's tampering with the data. TLS, which is the protocol used\n> for encryption on HTTPS URLs, has built-in mechanisms to detect any sort\n> of accidental or intentional modification of the data, so if we assume\n> that both your version of Git and GitHub sent valid protocol data, then\n> this means that if it came out bad on the other side, it was tampered\n> with in the middle by something that can decrypt the data (which would\n> have to be something trusted by your machine).\n>\n> That's why SSH works for you: because the types of proxies that\n> typically know how to process HTTPS data don't know how to decrypt or\n> intercept SSH connections, so your data doesn't get corrupted.\n> --\n> brian m. carlson (they/them or he/him)\n> Toronto, Ontario, CA\n\nThank you Brian,\n\nI cannot think of anything, I'm just behind my home network, I don't\nhave a dedicated firewall or proxy. Pushing via https works on Windows\non the same laptop. So I guess it's something in my Linux env. I don't\nknow if it matters, but cloning worked out of the box on Linux.\n\nSincerely,\nAbraham\n"}]}