Problem solved. Turns out that was a miscommunication on out side: the guy who setup the keys on that box left, and his access to GH repo has been revoked. And GitHub returns "repo not found" rather than "you have no access rights for this repository". On Wed, May 9, 2012 at 1:28 AM, Egor Ryabkov <egor.ryabkov@xxxxxxxxx> wrote: > > > Agreed. It's hard to tell if there's a real problem or not. If the > > redacted bits are the same, > > Yes, I checked this a few times and tried re-creating remote with the > address copied from GH site. > HTTP worked, SSH didn't. > > > > then it is probably a github issue. In that > > case, Egor, you should email support@xxxxxxxxxx about it and mention the > > name of the problematic repo. > > Yes, I actually contacted them last Friday, working with Simon Rozet now. > I updated him on what we've found and sent him the link to this thread. > > > Thanks for your help guys :) -- 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