Open talumbau opened 10 years ago
Hmmm
Could there be something else trying to use the same ssh port ?
thanks, wade
On Jun 16, 2014, at 1:05 PM, "T.J. Alumbaugh" notifications@github.com wrote:
This VM has been great to get going on XData stuff. However, I've noticed twice now that exiting out and reloading the VM can occasionally cause some problem where I can no longer connect to the VM. When this problem occurs, typing vagrant ssh results in this error:
ssh_exchange_identification: read: Connection reset by peer I've tried using config.ssh options to use a password, or just straight ssh to 127.0.0.1:2222 to try to get in to the box. Even just booting the VM in VirtualBox ends up with just a black screen. I can't imagine what is causing this. I have added DHCP to the Vagrant file:
config.vm.network "private_network", type: "dhcp" but taking it out doesn't fix the problem, and I need that to get an IP from the XData network. I'm using Mac OS 10.9.3, Vagrant 1.6.2, and VirtualBox 4.3.12. Let me know if you have any ideas on what could be causing this.
— Reply to this email directly or view it on GitHub.
This VM has been great to get going on XData stuff. However, I've noticed twice now that exiting out and reloading the VM can occasionally cause some problem where I can no longer connect to the VM. When this problem occurs, typing
vagrant ssh
results in this error:I've tried using
config.ssh
options to use a password, or just straightssh
to 127.0.0.1:2222 to try to get in to the box. Even just booting the VM in VirtualBox ends up with just a black screen. I can't imagine what is causing this. I have added DHCP to the Vagrant file:but taking it out doesn't fix the problem, and I need that to get an IP from the XData network. I'm using Mac OS 10.9.3, Vagrant 1.6.2, and VirtualBox 4.3.12. Let me know if you have any ideas on what could be causing this.