When i type heroku login i get this in the console
Sumant Bagade#Specter MINGW32 ~/Desktop
$ heroku login
heroku-cli: Adding dependencies...
! Get https://cli-assets.heroku.com/node/v5.7.0/win-x86/node.exe: dial tcp: lookup cli-assets.heroku.com: getaddrinfow: No such host is known.
done
heroku-cli: Installing core plugins...
!
! exec: "C:\\Users\\Sumant Bagade\\AppData\\Local\\heroku\\node-v5.7.0-windows-x86\\bin\\node.exe": file does not exist
heroku-cli: Installing core plugins (retrying)...
! Error installing package.
!
! Try running again with GODE_DEBUG=info to see more output.
heroku-cli: Adding dependencies...
! Get https://cli-assets.heroku.com/node/v5.7.0/win-x86/node.exe: dial tcp: lookup cli-assets.heroku.com: getaddrinfow: No such host is known.
done
heroku-cli: Installing core plugins...
!
! exec: "C:\\Users\\Sumant Bagade\\AppData\\Local\\heroku\\node-v5.7.0-windows-x86\\bin\\node.exe": file does not exist
heroku-cli: Installing core plugins (retrying)...
! Error installing package.
!
! Try running again with GODE_DEBUG=info to see more output.
heroku-cli: Adding dependencies...
! Get https://cli-assets.heroku.com/node/v5.7.0/win-x86/node.exe: dial tcp: lookup cli-assets.heroku.com: getaddrinfow: No such host is known.
done
System is Window 8.1 64 bit.
Tried npm cache clean but didnt work. I am trying to deploy Node.js app on heroku
Related
when i tried to run composer install on ubuntu 18.04 i got this:
The "https://packagist.org/packages.json" file could not be downloaded: SSL
operation failed with code 1. OpenSSL Error messages:
error:1408F10B:SSL routines:ssl3_get_record:wrong version number
Failed to enable crypto
failed to open stream: operation failed
I got the rigth proxy configuration on my /etc/apt/apt.conf and /etc/profile, but the error goes on and on, no mather what i do.
The proxy configuration needed for using composer is located in /etc/enviroment file.
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
http_proxy="http://username:password#10.4.1.20:3128"
https_proxy="http://username:password#10.4.1.20:3128"
I'm trying to install heroku-accounts using this command:
$ heroku plugins:install heroku-accounts
but instead I got this:
heroku-cli: Updating plugins... !
/Users/hit/Library/Caches/heroku/update.lock is locked with a reader active: 17964
I try rm the update.lock but it still get same result
I solve the problem by updating Heroku (I use homebrew install heroku)
heroku update
brew upgrade heroku
None of the above answers seem to work for me. The issue happened when I updated my heroku-cli via brew to version heroku-cli/6.13.8 (darwin-x64) node-v8.2.1 .
Although Error was very explicit that one more process is running, ps | grep showed no such process.
The only solution was to Restart System Once.
There is another copy of the heroku CLI running with the PID 17964
You can find it by doing something like this:
ps | grep 17964
Once you stop that process try your install again.
My heroku toolbelt had been working fine until last week that it's giving me this error on all heroku commands.
$ heroku run console -a abc
/Users/songserm/.local/share/heroku/client/bin/heroku: line 21: /Users/songserm/.local/share/heroku/client/bin/node: No such file or directory
/Users/songserm/.local/share/heroku/client/bin/heroku: line 21: /Users/songserm/.local/share/heroku/client/bin/node: No such file or directory
I didn't know that my heroku has been auto upgraded, but what has changed is I installed heroku-vi addon around the time. Not sure if it's the case.
Has anyone seen this issue before?
Noted that I installed heroku on my Mac using homebrew.
Cause:
This also happened to me, the client auto-updated but didn't do so properly:
heroku run console
heroku-cli: Updating to 6.11.14-c5f9179... 12.9 MB/12.9 MB
/Users/steves/.local/share/heroku/client/bin/heroku: line 21: /Users/steves/.local/share/heroku/client/bin/node: No such file or directory
/Users/steves/.local/share/heroku/client/bin/heroku: line 21: /Users/steves/.local/share/heroku/client/bin/node: No such file or directory
Solution:
The resolution was to re-install the client using the following (as found here https://github.com/heroku/cli/issues/485):
rm -rf ~/.local/share/heroku/client
I then checked using the status command and it re-installed correctly:
heroku status
heroku-cli: Updating to 6.11.14-c5f9179... 12.9 MB/12.9 MB
Migrating Heroku CLI v5 plugins... done
Apps: No known issues at this time.
Data: No known issues at this time.
Tools: No known issues at this time.
Heroku-error-Not a directory
Not a directory Error when executing Heroku commands
heroku
▸ stat /User/xxx/.local/share/heroku/client/bin/heroku: not a directory
▸ fork/exec /User/xxx/.local/share/heroku/client/bin/heroku: not a directory
Solution is to remove previous directory
rm -rf ~/.local/share/heroku/client
A quick workaround for me was to remove this file.
rm -rf ~/.local/share/heroku
And I was able to acces heroku console easily.
As everyone said the solution is:
deleting the heroku client with the following console command:
rm -rf ~/.local/share/heroku/plugins
But if you continue having problems you have to delete the heroku plugins folder:
rm -rf ~/.local/share/heroku/plugins
Then you can excecute the command
heroku status
To reinstall correctly
$ heroku status
heroku-cli: Updating to 6.99.0-ec9edad... 12.8 MB/12.8 MB
Apps: No known issues at this time.
Data: No known issues at this time.
Tools: No known issues at this time.
Today when I went to deploy to parse I got the error message below. It was working up until today, and it happens in any directory where I try to use parse. I reinstalled the command line tool but this didn't help. Any ideas as to what is going on and how I can get it to work again?
dial tcp: lookup api.parse.com: no such host
/home/travis/gopath/src/github.com/ParsePlatform/parse-cli/main.go:143 checkIfSupported
/home/travis/gopath/src/github.com/ParsePlatform/parse-cli/main.go:101 main
/home/travis/.gimme/versions/go1.4.2.linux.amd64/src/runtime/proc.go:72 main
/home/travis/.gimme/versions/go1.4.2.linux.amd64/src/runtime/asm_amd64.s:2233 goexit
GOT THIS TO WORK!
go version 1.4.2 is the problem. Use homebrew to "brew install go" to get go version 1.5.3. then install parse-cli with:
'go get -t github.com/ParsePlatform/parse-cli'
now use 'parse-cli deploy' instead of 'parse deploy'
EDIT: In case you haven't set them:
export GOPATH=$HOME/golang
export GOROOT=/usr/local/opt/go/libexec
I was able to solve this same issue just by running the install:
curl -s https://www.parse.com/downloads/cloud_code/installer.sh | sudo /bin/bash
I am using OS X Yosemite
I ran the following command in Composer because Laravel fails to download and install properly all the time:
composer diagnose
result:
Checking platform settings: OK
Checking git settings: OK
Checking http connectivity to packagist: OK
Checking https connectivity to packagist: FAIL
[Composer\Downloader\TransportException] The "https://packagist.org/packages.json" file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Failed to enable crypto
failed to open stream: operation failed
Checking github.com rate limit: FAIL
[Composer\Downloader\TransportException] The "https://api.github.com/rate_limit" file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Failed to enable crypto
failed to open stream: operation failed
Checking disk free space: OK
Checking composer version:
[Composer\Downloader\TransportException]
The "https://getcomposer.org/version" file could not be downloaded: SSL ope
ration failed with code 1. OpenSSL Error messages:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify
failed
Failed to enable crypto
failed to open stream: operation failed
The main line I want to focus on is:
SSL operation failed with code 1. OpenSSL Error messages:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Failed to enable crypto
How can I fix this. I have tried several solutions on the web and none have worked. I am totally new to the use of the command line.
When downloading and installing Laravel with the following command: composer create-project laravel/laravel --prefer-dist can't I just manually download the stuff myself and place it in the correct folder to avoid this SSL problem?
Note: I am running OS X Yosemite. I believe this works with Mavericks too.
After looking a several answers and combining them mixing and matching etc. Here is a rough explanation on what I did.
Open the command line and run:
locate cacert.pem
This will list all the locations where your certificates are.
My result:
/Applications/Adobe Dreamweaver CS6/Configuration/Certs/cacert.pem
/Applications/MAMP/Library/lib/python2.7/test/pycacert.pem
/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/pip/_vendor/requests/cacert.pem
/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/test/pycacert.pem
/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/test/test_asyncio/pycacert.pem
/Users/robert/.composer/cacert.pem
/opt/vagrant/embedded/cacert.pem
/usr/ssl/certs/cacert.pem
I downloaded the most recent one from curl
http://curl.haxx.se/docs/caextract.html
I made a directory in /usr/ssl/certs/
and put the downloaded cert there /usr/ssl/certs/cacert.pem
I opened up my php.ini file and placed this line at the top of the file:
openssl.cafile=/usr/ssl/certs/cacert.pem
Restart apache (stop apache and start it again)
Everything worked out for me.
Now one thing that I do believe needs to be done is you need to tell the command line which PHP you are referring to. I am running PHP under XAMPP and not natively on my OS X. So the command line will think that you are referring to the native PHP on OS X and not the one running on XAMPP. This needs to be changed I believe for this to work. If not then it should be good.
As mentioned this solution worked for me.
I faced this issue while executing composer install in Magento 2 , on MAMP , Mac m1 the issue was fixed after I replaced the file in path : /Applications/MAMP/Library/OpenSSL/cert.pem
with the pem file downloaded from the :
http://curl.haxx.se/docs/caextract.html
hope this helps someone on .
The easiest way without the need to change the php.ini file:
DEBIAN/UBUNTU:
# apt-get install ca-certificates
FEDORA:
# dnf install ca-certificates.noarch
CENTOS/REDHAT
# yum install ca-certificates.noarch
Source:
https://linuxconfig.org/routines-ssl3-get-server-certificate-certificate-verify-failed
Another possible reason is that the server's SSL cert has expired. If it is your server, check the /etc/apache2/ssl (for ubuntu). The certs usually last for 365 days. See 'https://www.digitalocean.com/community/tutorials/how-to-create-a-ssl-certificate-on-apache-for-ubuntu-14-04' on how to create one.