title: Git fetch/pull have stopped working
body: <p>Git fetch and pull both stopped working yesterday on the server (AWS instance).</p>
  
  <pre><code>$ git fetch
  ERROR: Repository not found.
  fatal: The remote end hung up unexpectedly
  </code></pre>
  
  <p>There are two repository clones on that instance, both giving the same error. git still works well from local PCs.</p>
  
  <p><code>git remote -v</code> gives the same results on local PC and on the server; <code>ssh git@github.com</code> works as it should ("Hi (name)! You've successfully authenticated, but GitHub does not provide shell access.")</p>
  
  <p>There's one difference in behaviour: <code>git pull origin st</code>+[Tab] used to expand to a branch name; now it expands to a name of the file in current directory (filename is not the same as branch name).</p>
  
  <p><strong>UPDATE</strong>: I tried re-creating remote: SSH version still fails, but HTTP worked.</p>
  
  <p>According to <a href="http://thread.gmane.org/gmane.comp.version-control.git/197323/">this</a> discussion in git mailing list, this is actually a problem on GitHub site.</p>
  
  <p><strong>UPDATE</strong></p>
  
  <p>output with <code>GIT_TRACE=1</code></p>
  
  <pre><code>############# 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@github.com' '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@github.com' 'git-upload-pack '\''(username)/(reponame).git'\'''
  ERROR: Repository not found.
  fatal: The remote end hung up unexpectedly
  </code></pre>