1

I'm trying to figure out git daemon.

I have seen many posts and threads including Stack Overflow questions regarding this issue, however none of the solutions helped me.

The repo is 100% not corrupted.

The thing is, I can easily clone the repo via 127.0.0.1, cloning on the same pc where daemon is running with my external IP works around once every 10 attempts, giving "error in sideband demultiplexer"

screenshot

Cloning from another PC in different network using my external IP gives the "read error invalid argument, early EOFs, index-pack failed"

another screenshot

What can be the reason to this behavior?

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
ymdred16
  • 98
  • 3
  • 15

1 Answers1

0

This has been reported before, since 2015: a clone from a Git for Windows daemon is flaky:

See if delaying the daemon execution through text selection in the console helps, as reported here.

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • Selection does not change anything, neither in bash wrapper, nor in console. Still getting same errors. – ymdred16 Sep 22 '19 at 12:02
  • @ymdred16 Is there a reason why you need the ssh daemon, as opposed to, for instance openssh? (which is in Windows 10: https://learn.microsoft.com/en-us/windows-server/administration/openssh/openssh_overview) – VonC Sep 22 '19 at 12:04
  • No particular reason actually. I am a complete newbie in git, so I wanted the most simplest way to share repos with my collaborator, and it seemed pretty easy to set up git daemon. I guess git daemon is not an option for me any more. – ymdred16 Sep 22 '19 at 12:08
  • @ymdred16 no, it is a legacy mechanism, which is not used anymore. Other protocoles exist: https://git-scm.com/book/en/v1/Git-on-the-Server-The-Protocols – VonC Sep 22 '19 at 12:11
  • Okay, seems like I misunderstood it. I am going to check the other options. Thanks :) – ymdred16 Sep 22 '19 at 12:14