SSH library issue on 2.2.1 version

[dingo-d]

I tried re-provisioning after switching to a new branch. I removed triggers and updated vagrant, virtualbox, and when I try vagrant up --provision I get

An error occurred in the underlying SSH library that Vagrant uses. The error message is shown below. In many cases, errors from this library are caused by ssh-agent issues. Try disabling your SSH agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating

Am I missing anything?

Your Environment

• VVV version: 2.2.1
• VVV Git Branch: 2-2-release
• Vagrant version: 2.1.1.
• VM Provider name: Virtualbox
• VM Provider version: Version 5.2.12 r122591 (Qt5.6.3)
• Operating System and version: MacOS High Sierra v10.13.4 (17E202)

[dingo-d]

Ok, seems like I had to do vagrant halt first and then vagrant up --provision. Seems to be provisioning with few issues:

[default] GuestAdditions versions on your host (5.2.12) and guest (5.2.8) do not match. An error occurred during installation of VirtualBox Guest Additions 5.2.12. Some functionality may not work as intended. In most cases it is OK that the "Window System drivers" installation failed.

[dingo-d]

And I got another error (well, errors)

default: fatal: destination path '/srv/www/default/dashboard' already exists and is not an empty directory. default: fatal: Not a git repository (or any parent up to mount point /srv) default: Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

Then it couldn't access my utilities and VVV utilities

default: fatal: unable to access 'https://github.com/dingo-d/browscap-vvv-utility/': Couldn't connect to server
default: fatal: unable to access 'https://github.com/dingo-d/apigee-vvv-utility/': Couldn't connect to server
default: fatal: unable to access 'https://github.com/Varying-Vagrant-Vagrants/vvv-utilities.git/': Couldn't connect to server

default: fatal: unable to access 'https://github.com/rlerdorf/opcache-status.git/': Couldn't connect to server The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong.

[dingo-d]

Ok, seems like what I needed was a computer restart and that solved it.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.