Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

problems with connecting to server after vagrant up #9120

Closed
OtezVikentiy opened this issue Oct 28, 2017 · 3 comments
Closed

problems with connecting to server after vagrant up #9120

OtezVikentiy opened this issue Oct 28, 2017 · 3 comments

Comments

@OtezVikentiy
Copy link

Vagrant version 2.0.0

Host operating system Windows 10

Guest operating system ubuntu/trusty64

Vagrantfile

# -*- mode: ruby -*-
# vi: set ft=ruby :

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "ubuntu/trusty64"

  config.vm.provider "virtualbox" do |v|
      v.name = "local_vm_100500"
      v.memory = 2048
  end

  # Create a private network, which allows host-only access to the machine using a specific IP.
  config.vm.network "private_network", ip: "192.168.128.56"

  # Share an additional folder to the guest VM. The first argument is the path on the host to the actual folder.
  # The second argument is the path on the guest to mount the folder.
  config.vm.synced_folder ".", "/var/www/project", owner: "vagrant", group: "vagrant"

end

Debug output

$ vagrant ssh -- -v
OpenSSH_7.5p1, OpenSSL 1.0.2k  26 Jan 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to 127.0.0.1 [127.0.0.1] port 2222.
debug1: Connection established.
Could not create directory '/home/admin/.ssh'.
debug1: key_load_public: No such file or directory
debug1: identity file C:/Users/admin/.vagrant.d/insecure_private_key type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:/Users/admin/.vagrant.d/insecure_private_key-cert type -
1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.5
ssh_exchange_identification: read: Connection reset by peer

Expected behavior

It should have connected to virtual machine via ssh

Actual behavior

in Debug

@briancain
Copy link
Member

Could you provide a link to a gist of the debug output when you just run vagrant ssh --debug? Thank you!

@OtezVikentiy
Copy link
Author

Hello, i solved this problem globally. I installed Ubuntu and now everything works fine. I don't know why, after last update in Windows nothing worked fine. So in my case i solved the problem reinstalling OS. =D

@ghost
Copy link

ghost commented Mar 31, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Mar 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants