search

heroku / legacy-cli

Heroku CLI
https://cli.heroku.com
MIT License
1.37k stars 381 forks source link

Unable to install CLI -- Error: Permission denied #1990

Open alexauritt opened 8 years ago

alexauritt commented 8 years ago

I've been having trouble with the Heroku CLI for several days now. I've tried uninstalling and reinstalling several times. Have tried installing through homebrew, as well as installing the Heroku Toolbelt. And I've made sure to fully uninstall before trying again, following uninstall directions posted at: https://devcenter.heroku.com/articles/heroku-command#uninstalling-the-heroku-cli

When I download the toolbelt, and then run heroku --version, I'm getting the following error:

➝ heroku --version heroku-cli: Installing CLI... 20.39MB/20.39MB ! Heroku client internal error. ! Search for help at: https://help.heroku.com ! Or report a bug at: https://github.com/heroku/heroku/issues/new

Error:       Permission denied - /Users/[xxx]]xx]/.local/share/heroku (Errno::EACCES)
Command:     heroku --version
Version:     heroku-toolbelt/3.43.6 (x86_64-darwin10.8.0) ruby/1.9.3
Error ID:    8316c18765d74ea9ac1b7f677ab6bb70

More information in /Users/alexauritt/.heroku/error.log

When I installed through Homebrew a few days ago, and I was able to get the cli to install after changing permission on a file somewhere (can't recal which one). However today autoupdate failed, also due to a permissions issue.

Can you advise. To the best of my knowledge, I am not running any antivirus software, and haven't restricted any permissions settings on my machine.

Please advise. Work has come to a standstill and I'm quite frustrated.

Thanks in advance

jdx commented 8 years ago

You need write access to that directory that is in the error message. Make sure you are the owner of it and/or the parent directory and you've given it user write permission.

code4cake commented 8 years ago

If you are installing heroku with homebrew rather than downloading the CLI from the heroku website. Just chmod 600 to the folder specified when you got the error. That solved the problem for me