Varying-Vagrant-Vagrants / VVV

An open source Vagrant configuration for developing with WordPress
https://varyingvagrantvagrants.org
MIT License
4.54k stars 848 forks source link

VirtualBox v6.1.28 issues, All sites timing out #2549

Closed ollybowman closed 2 years ago

ollybowman commented 2 years ago

All sites are timing out when I try to view them in the browser.

I've just updated vagrant, vvv and virtualbox and it was all working fine beforehand.

I've checked the hosts file and the dns entries are there.

There doesn't appear to be any issues when provisioning.

The VM is definitely running because I can SSH into it.

I've destroyed the box, updated it and re-provisioned.

Not really sure why this isn't working, does anyone know what's going on?

Here's the log file provisioner-main.log

welcome[bot] commented 2 years ago

Thanks for opening your first issue here! Be sure to follow the issue template and include your OS/Vagrant/VVV versions! Don't forget you can get support in the VVV slack at https://varyingvagrantvagrants.org/docs/en-US/slack/

VVV
VVV Slack Workspace
Join the VVV Slack Workspace
tomjn commented 2 years ago

Hey!

Which branch are you on and can you share your splash screen from a vagrant status? Versions of things would be good! Just walking home so it’ll take me a bit to get to your log

On Thu, 28 Oct 2021 at 20:58, welcome[bot] @.***> wrote:

Thanks for opening your first issue here! Be sure to follow the issue template and include your OS/Vagrant/VVV versions! Don't forget you can get support in the VVV slack at https://varyingvagrantvagrants.org/docs/en-US/slack/

https://camo.githubusercontent.com/3e970fd174a8f4e54062348f83e134cf11c6b25afa60b92657e2a52794f87a2d/68747470733a2f2f76617279696e6776616772616e7476616772616e74732e6f72672f696d616765732f7676762e706e67 http:///images/vvv.png VVV VVV Slack Workspace https://varyingvagrantvagrants.org/docs/en-US/slack/ Join the VVV Slack Workspace

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Varying-Vagrant-Vagrants/VVV/issues/2549#issuecomment-954156540, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAOLZY3UFKG5A7VNE3J2DLUJGTP5ANCNFSM5G5WSCMA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

ollybowman commented 2 years ago

Thanks, actually I just tried rolling back VirtualBox to 6.1.24 after looking at another comment and that seems to have fixed the issue.

tomjn commented 2 years ago

@ollybowman which version of virtualbox?

ollybowman commented 2 years ago

I was using 6.1.28

chrisjimallen commented 2 years ago

I am on 6.1.29 on Arch. Oddly I have also tried it on Manjaro with the same version as @ollybowman (6.1.28) and it works fine. I guess this is more a vagrant/vb compatibility issue than an actual VVV issue?

tomjn commented 2 years ago

Closing this as it's not a VVV issue, it's a VirtualBox issue.

If you have this issue: