tomjn
commented
1 week ago Have you tested this after a reboot? This sounds like a virtualbox or windows networking issue. Unless missingWinAdminPriv is the clue
On Fri, 21 Jun 2024 at 14:15, shanebp @.***> wrote:
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.
c:\vvv-local>vagrant up
\ V\ V\ V / v3.12 Ruby:3.1.4, Path:"c:/vvv-local" //_/ git::stable(aee9a69 https://github.com/Varying-Vagrant-Vagrants/VVV/commit/aee9a695915c1cfb2395b26880ec142952a22f8e )
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 haltto shut it down forcefully, or you can runvagrant suspendto simplysuspend the virtual machine. In either case, to restart it again, simply runvagrant up.Which Operating System are you using?
Microsoft Windows Which provider are you using?
VirtualBox 7
— Reply to this email directly, view it on GitHub https://github.com/Varying-Vagrant-Vagrants/VVV/issues/2717, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAOLZ35HGJJRFPV2LU44FLZIQRQPAVCNFSM6AAAAABJV4ZAHOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM3DMNJSHA2DCMI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
shanebp
Gist
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 upbut 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 provisionor 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 negotiatingHow do we reproduce it?
No response
What is the output of
vagrant statusWhich Operating System are you using?
Microsoft Windows
Which provider are you using?
VirtualBox 7