I'm able to log in to the console and cd to chef-server-vagrant, but not able to run vagrant ssh, which it will fail with "ssh_exchange_identification: read: connection reset by peer message. I'm running on a virtualbox. I have tried to use vagrant up --debug, but nothing available.
On Friday, October 25, 2019 at 3:56:13 PM UTC-5, TB wrote: > > Hello, > > I need help. Recently, my chef server vagrant was working one day and the > next it stopped working. Everytime I run 'vagrant ssh' it said > "ssh_exchange_identification: read: Connection reset by peer.' message. > I've looked for this error message online, from other users suggesting to > run vagrant halt, then vagrant up to bring it back, but it stills won't > work. Some suggested to check for enabling hyper-v and enabling vt-x, and > it stills won't work. I am thinking about to run vagrant destroy and bring > back up again to its normal state with vagrant up, but afraid I might loose > everything or how long it will take to get vagrant back to its normal > working condition. > > Any suggestions/ideas to what caused this and how to resolve this? > > > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/fbf427f7-b42d-4e71-bc64-a458e216abab%40googlegroups.com.
