突然无法推送到heroku:“无法协商密钥交换方法" [英] Suddenly can't push to heroku: "unable to negotiate key exchange method"

查看:158
本文介绍了突然无法推送到heroku:“无法协商密钥交换方法"的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

"git push heroku"突然失败. (我安装了Node.js,我认为它可能已经升级了一些东西,并以某种方式破坏了它.)

"git push heroku" is suddenly failing. (I installed Node.js and I think it may have upgraded some things and broke this somehow.)

我已经阅读了所有类似的帖子;它不是在告诉我哪个交换已提供",并且看起来一切都匹配,但是通话失败,我很茫然.
我成功完成了heroku auth:login.

I've read all the similar posts; it's not telling me which exchange was 'offered', and everything looks like it matches, but the call fails and I'm at a loss.
I did heroku auth:login successfully.

ssh git@heroku.com -v给了我以下内容:

OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/jeff/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for * <This line is 'Host *'>
debug1: Connecting to heroku.com [50.19.85.156] port 22.
debug1: Connection established.
debug1: identity file /Users/jeff/.ssh/id_rsa type 1
debug1: identity file /Users/jeff/.ssh/id_rsa-cert type -1
debug1: identity file /Users/jeff/.ssh/id_dsa type -1
debug1: identity file /Users/jeff/.ssh/id_dsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
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-sha2-256-etm@openssh.com none
debug1: kex: client->server aes128-ctr hmac-sha2-256-etm@openssh.com none
Unable to negotiate a key exchange method

推荐答案

今天早上我遇到了同样的问题.

I encountered same problem this morning.

我可以通过更改git remote url来避免此问题.

I can avoid this problem, with change git remote url as below.

来自: git@heroku.com:app-name.git

from: git@heroku.com:app-name.git

至: https://git.heroku.com/app-name.git

您可以在下面使用命令

git remote rm heroku git remote add heroku https://git.heroku.com/app-name.git

git remote rm heroku git remote add heroku https://git.heroku.com/app-name.git

这篇关于突然无法推送到heroku:“无法协商密钥交换方法"的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆