> Are you sure it is an error on the remote side (presumably on GitHub)? No, I'm pretty sure it's something on my side, as clones on other PCs still work. >> "$ GIT_TRACE=1 git fetch" gives somewhat different output on local PC >> and server: >> http://pastecode.com/bd3fc1a79f8e9d1eaf30911d9895938051c472f4 > > So you are going over http:// after all. But it does not look like github > to me No, I'm using SSH connection. Did you imply that it's better to paste logs directly in the email? Here they go: ############# Local results ############# $ GIT_TRACE=1 git fetch setup: git_dir: .git setup: worktree: c:/Projects/(local_path) setup: cwd: c:/Projects/(local_path) setup: prefix: (null) trace: built-in: git 'fetch' trace: run_command: 'ssh' 'git@xxxxxxxxxx' 'git-upload-pack '\''(username)/(reponame).git'\''' Enter passphrase for key '(keyname)': trace: run_command: 'rev-list' '--quiet' '--objects' '--stdin' '--not' '--all' ############# AWS results ############# $ GIT_TRACE=1 git fetch trace: built-in: git 'fetch' trace: run_command: 'ssh' 'git@xxxxxxxxxx' 'git-upload-pack '\''(username)/(reponame).git'\''' ERROR: Repository not found. fatal: The remote end hung up unexpectedly I tried re-adding remote: SSH version fails with the same error, but HTTP version works. I'd rather have SSH working, though. And ideas about what could've caused it, or how to diagnose it further? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html