2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018

11/22/2009: How to Resolve Heroku's 'not authorized to access newname' Git error.

How to Resolve Heroku's 'not authorized to access newname' Git error. When you see the 'not authorized to access newname' error, it probably. means that your Git configuration is incorrect. For example, my .git/config file had the following:
[core]
 repositoryformatversion = 0
 filemode = true
 bare = false
 logallrefupdates = true
[remote "heroku"]
 url = git@heroku.com:newname.git
 fetch = +refs/heads/*:refs/remotes/heroku/*
Notice the highlighted words. Just change newname to the actual project name and you should be fixed.


subscribe via RSS