2016-10-11 81 views
0

我想ssh到的Heroku(進入命令行)...... 我跟着instuctions在https://devcenter.heroku.com/articles/keys,但我不斷收到此錯誤:SSH Heroku的錯誤「PTY分配請求失敗的通道0」

PTY allocation request failed on channel 0 
shell request failed on channel 0 

整個日誌:

debug1: Reading configuration data /home/gilad/.ssh/config 
debug1: /home/gilad/.ssh/config line 1: Applying options for heroku.com 
debug1: Reading configuration data /etc/ssh/ssh_config 
debug1: /etc/ssh/ssh_config line 19: Applying options for * 
debug1: Connecting to heroku.com [50.19.85.132] port 22. 
debug1: Connection established. 
debug1: identity file /home/gilad/.ssh/ssh-dss type -1 
debug1: identity file /home/gilad/.ssh/ssh-dss-cert type -1 
debug1: identity file /home/gilad/.ssh/id_rsa type 1 
debug1: identity file /home/gilad/.ssh/id_rsa-cert type -1 
debug1: Enabling compatibility mode for protocol 2.0 
debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8 
debug1: Remote protocol version 2.0, remote software version endosome 
debug1: no match: endosome 
debug1: SSH2_MSG_KEXINIT sent 
debug1: SSH2_MSG_KEXINIT received 
debug1: kex: server->client aes128-ctr hmac-sha1 none 
debug1: kex: client->server aes128-ctr hmac-sha1 none 
debug1: sending SSH2_MSG_KEX_ECDH_INIT 
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY 
debug1: Server host key: RSA 8b:48:5e:67:0e:c9:16:47:32:f2:87:0c:1f:c8:60:ad 
debug1: Host 'heroku.com' is known and matches the RSA host key. 
debug1: Found key in /home/gilad/.ssh/known_hosts:2 
debug1: ssh_rsa_verify: signature correct 
debug1: SSH2_MSG_NEWKEYS sent 
debug1: expecting SSH2_MSG_NEWKEYS 
debug1: SSH2_MSG_NEWKEYS received 
debug1: SSH2_MSG_SERVICE_REQUEST sent 
debug1: SSH2_MSG_SERVICE_ACCEPT received 
debug1: Authentications that can continue: publickey 
debug1: Next authentication method: publickey 
debug1: Offering RSA public key: /home/gilad/.ssh/id_rsa 
debug1: Server accepts key: pkalg ssh-rsa blen 279 
debug1: Authentication succeeded (publickey). 
Authenticated to heroku.com ([50.19.85.132]:22). 
debug1: channel 0: new [client-session] 
debug1: Entering interactive session. 
debug1: Sending environment. 
debug1: Sending env LC_PAPER = he_IL.UTF-8 
debug1: Sending env LC_ADDRESS = he_IL.UTF-8 
debug1: Sending env LC_MONETARY = he_IL.UTF-8 
debug1: Sending env LC_NUMERIC = he_IL.UTF-8 
debug1: Sending env LC_TELEPHONE = he_IL.UTF-8 
debug1: Sending env LC_IDENTIFICATION = he_IL.UTF-8 
debug1: Sending env LANG = en_US.UTF-8 
debug1: Sending env LC_MEASUREMENT = he_IL.UTF-8 
debug1: Sending env LC_TIME = he_IL.UTF-8 
debug1: Sending env LC_NAME = he_IL.UTF-8 
PTY allocation request failed on channel 0 
shell request failed on channel 0 

ssh_config中:

Host heroku.com 
    HostName heroku.com 
    IdentityFile ~/.ssh/id_rsa 
    IdentitiesOnly yes 

我雷爾你知道這意味着什麼 - 幫助嗎?

+0

嘗試改變事情,看看會發生什麼。嘗試再次瀏覽指南,看看是否有幫助。然後,如果你仍然無法得到它,告訴我們你試過什麼,什麼不起作用。如果你表現出努力,人們更可能提供幫助。另外,如果你仍然可以問一個完整的問題,一般應避免使用「整個日誌:」。瀏覽本文,它將幫助您改進您的問題:http://stackoverflow.com/help/mcve – 3ocene

+0

PTY和shell請求消息意味着服務器不願意爲您啓動交互式會話。 Heroku可能是正常的。鏈接到的Heroku頁面正在討論使用ssh作爲git訪問,它不需要PTY或shell。什麼讓你認爲shell訪問應該起作用? – Kenster

回答

2

可以通過先安裝heroku toolbelt並登錄工具區後,可以運行heroku run bash --app your_app_name

關於它的Heroku文檔見here ssh到一個Heroku的賽道。注意他們的警告,儘管說通過使用ssh幾乎沒有什麼收穫

相關問題