我昨天使用PuPHPet设置了Vagrant,一切似乎都运行正常。我使用Querious连接到mysql数据库。但是,我没有保存用于连接的配置,并且在今天早上做完流浪之后,无论我做什么,我都无法连接。
我正在尝试:
如果我尝试这些设置,我会
> SSH failed to connect to the server 192.168.56.101 on port 2222
>
> SSH connection failed for an unknown reason. SSH shutdown.
>
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: Connecting to 192.168.56.101 [192.168.56.101] port 2222.
debug1: connect to address 192.168.56.101 port 2222: Operation timed out
ssh: connect to host 192.168.56.101 port 2222: Operation timed out
如果我将SSH主机更改为127.0.0.1,则会出现其他错误。远程主机的SSH密钥验证失败。
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: Connecting to 127.0.0.1 [127.0.0.1] port 2222.
debug1: fd 3 clearing O_NONBLOCK
debug1: Connection established.
debug1: identity file /Users/db/Dev/c2t-vagrant/puphpet/files/dot/ssh/id_rsa type 1
debug1: identity file /Users/db/Dev/c2t-vagrant/puphpet/files/dot/ssh/id_rsa-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 OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 pat OpenSSH*
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5-etm@openssh.com none
debug1: kex: client->server aes128-ctr hmac-md5-etm@openssh.com none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA 9c:3a:9a:d0:22:8c:19:05:f2:26:54:d9:62:9e:ba:e4
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
9c:3a:9a:d0:22:8c:19:05:f2:26:54:d9:62:9e:ba:e4.
Please contact your system administrator.
Add correct host key in /Users/db/.ssh/known_hosts to get rid of this message.
Offending RSA key in /Users/db/.ssh/known_hosts:2
RSA host key for [127.0.0.1]:2222 has changed and you have requested strict checking.
Host key verification failed.
我做了“vagrant ssh”并转到〜/ .ssh并且有三个文件,授权密钥,id_rsa和id_rsa.pub。 id_rsa与我选择的密钥匹配,但我没有立即识别authorized_keys文件中的内容。
我也尝试在php.ini中更改绑定地址la Connect to MySQL on Vagrant instance with Sequel Pro,但我没有运气/不明白它在做什么。
我显然是盲目地飞行,对Vagrant不熟悉并且对SSH的掌握非常不完整。我应该尝试哪种类型的东西才能让它发挥作用?
谢谢。
答案 0 :(得分:2)
答案 1 :(得分:1)
PuPHPet默认使用ssh端口22。确保你的config.yaml说的是什么。
如果您已更改它,请确保将该端口添加到防火墙。