{"thread":{"id":"23680","subject":"Making git work with new remote server","startedAt":"2010-05-03T15:59:34Z","lastAt":"2010-05-03T16:14:47Z","messageCount":2,"participants":["amillican","Michael J Gruber"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"140833","messageId":"28436896.post@talk.nabble.com","threadId":"23680","inReplyTo":null,"subject":"Making git work with new remote server","fromName":"amillican","fromEmail":"amillican@cogentsystems.com","sentAt":"2010-05-03T15:59:34Z","receivedAt":"2010-05-03T15:59:34Z","isPatch":false,"sender":{"key":"amillican@cogentsystems.com","avatar":null},"body":"\n  0  vote down  star\n\t\n\nI am the CM person for a small company that just started using Git. We have\ntwo Git repositories currently hosted on a Windows box that is our\nall-purpose Windows server. But, we just set up a dedicated server for our\nCM software on an Ubuntu Linux server named \"Callisto\".\n\nSo I created a test Git repository on Callisto. I gave its directory all of\nthe proper permissions recursively. I had the sysadmin create a login for me\non Callisto, and I created a key to use for logging in via SSH. I set up my\nkey to use a passphrase; I don't know if that could be contributing to my\nproblems? Anyway, I know my SSH login works because I tested it through\npuTTY.\n\nBut, even after hours of trials and head scratching, I can't get my Windows\nGit bash (mSysGit) to talk to Callisto for the purposes of pushing or\npulling Callisto's git repository files. Obviously, when trying a push, I've\nbeen trying to log into my Callisto account using SSH.\n\nI keep getting \"Fatal error. The remote end hung up unexpectedly.\" And I've\neven gotten the error that Git doesn't recognize the test repository on\nCallisto as a git repository. I read online that the \"Fatal error...hung up\nunexpectedly\" is usually a problem with the server connection or\npermissions. So what am I missing or overlooking here? And why doesn't a\npull using the git:// protocol work, since that only uses read-only access?\nGroup and public permissions for the git repository's directory on Callisto\nare set to read and execute, but not write.\n\nIf anyone could help, I would be so grateful. Thank you.\n-- \nView this message in context: http://old.nabble.com/Making-git-work-with-new-remote-server-tp28436896p28436896.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"140834","messageId":"4BDEF677.5070807@drmicha.warpmail.net","threadId":"23680","inReplyTo":"28436896.post@talk.nabble.com","subject":"Re: Making git work with new remote server","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2010-05-03T16:14:47Z","receivedAt":"2010-05-03T16:14:47Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"amillican venit, vidit, dixit 03.05.2010 17:59:\n> \n>   0  vote down  star\n> \t\n> \n> I am the CM person for a small company that just started using Git. We have\n> two Git repositories currently hosted on a Windows box that is our\n> all-purpose Windows server. But, we just set up a dedicated server for our\n> CM software on an Ubuntu Linux server named \"Callisto\".\n> \n> So I created a test Git repository on Callisto. I gave its directory all of\n> the proper permissions recursively. I had the sysadmin create a login for me\n> on Callisto, and I created a key to use for logging in via SSH. I set up my\n> key to use a passphrase; I don't know if that could be contributing to my\n> problems? Anyway, I know my SSH login works because I tested it through\n> puTTY.\n> \n> But, even after hours of trials and head scratching, I can't get my Windows\n> Git bash (mSysGit) to talk to Callisto for the purposes of pushing or\n> pulling Callisto's git repository files. Obviously, when trying a push, I've\n> been trying to log into my Callisto account using SSH.\n> \n> I keep getting \"Fatal error. The remote end hung up unexpectedly.\" And I've\n> even gotten the error that Git doesn't recognize the test repository on\n> Callisto as a git repository. I read online that the \"Fatal error...hung up\n> unexpectedly\" is usually a problem with the server connection or\n> permissions. So what am I missing or overlooking here? And why doesn't a\n> pull using the git:// protocol work, since that only uses read-only access?\n> Group and public permissions for the git repository's directory on Callisto\n> are set to read and execute, but not write.\n> \n> If anyone could help, I would be so grateful. Thank you.\n\nFor git:// without ssh you need a running git-daemon on the server.\n\nFor helping you more we would need the actual commands you tried and the\nexact output.\n\nCheers,\nMichael\n"}]}