VVV: timeout during server version negotiating
Are you using the latest stable or develop branch version of VVV?
Yes (stable)
Is it a new VVV, or an existing VVV that used to work?
Existing, worked but now broken
Did you use a CustomFile?
No (default)
Whats the problem?
Using Windows 10.
Everything was working properly until today. Tried to vagrant up but get this error: timeout during server version negotiating. The vagrant machine is running.
I can open the vvv dashboard in a browser, but none of the sites will connect.
Output: c:\vvv-local>vagrant up
\ V\ V\ V / v3.12 Ruby:3.1.4, Path:“c:/vvv-local” _/_/_/ git::stable(aee9a695)
Platform: mingw32 windows missingWinAdminPriv vagrant-goodhosts monochrome-terminal shared_db_folder_disabled Vagrant: v2.4.1, virtualbox: v7.0.18
Docs: https://varyingvagrantvagrants.org/ Contribute: https://github.com/varying-vagrant-vagrants/vvv Dashboard: http://vvv.test
Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 vvv.test
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 wordpress.test
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 buddyboss.test
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 vvv.test
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 wordpress.test
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 buddyboss.test
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 vvv.test
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 wordpress.test
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 buddyboss.test
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 vvv.test
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 wordpress.test
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 buddyboss.test
==> default: [vagrant-goodhosts] Checking for host entries
==> default: [vagrant-goodhosts] Finished processing
==> default: Machine already provisioned. Run vagrant provision or use the --provision
==> default: flag to force provisioning. Provisioners marked to run always will still run.
==> default: Running action triggers after up …
==> default: Running trigger: VVV Post-Up…
==> default: Trigger run failed
==> default: An error occurred in the underlying SSH library that Vagrant uses.
==> default: The error message is shown below. In many cases, errors from this
==> default: library are caused by ssh-agent issues. Try disabling your SSH
==> default: agent or removing some keys and try again.
==> default:
==> default: If the problem persists, please report a bug to the net-ssh project.
==> default:
==> default: timeout during server version negotiating
How do we reproduce it?
No response
What is the output of vagrant status
c:\vvv-local>vagrant status
__ __ __ __
\ V\ V\ V / v3.12 Ruby:3.1.4, Path:"c:/vvv-local"
\_/\_/\_/ git::stable(aee9a695)
Platform: mingw32 windows missingWinAdminPriv vagrant-goodhosts monochrome-terminal shared_db_folder_disabled
Vagrant: v2.4.1, virtualbox: v7.0.18
Docs: https://varyingvagrantvagrants.org/
Contribute: https://github.com/varying-vagrant-vagrants/vvv
Dashboard: http://vvv.test
Current machine states:
default running (virtualbox)
The VM is running. To stop this VM, you can run `vagrant halt` to
shut it down forcefully, or you can run `vagrant suspend` to simply
suspend the virtual machine. In either case, to restart it again,
simply run `vagrant up`.
Which Operating System are you using?
Microsoft Windows
Which provider are you using?
VirtualBox 7
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 35 (22 by maintainers)
3.14.0