Vagrant VMs are not functional if the laptop lid is closed for sometime.

[nshah-tibco]

Vagrant version - vagrant 2.1.4

Host operating system - Ubuntu 18.04

Guest operating system - Linux

Expected behavior

I did vagrant up. All the VMs were in running state. I was able to access my local env url. Then i closed my laptop lid and came home from office. After coming home, when i opened laptop, all the vm's were still running, but i could not access my local env url.

I did vagrant --provision reload but it did not work either.

I had to destroy vagrant and do vagrant up again but it is a wate of time.

Actual behavior

What actually happened?

Steps to reproduce

References

Are there any other GitHub issues (open or closed) that should be linked here?
For example:

• NAT DNS Proxy Option? #1234
• ...

[briancain]

Hey there @nshahn - When you close your laptop, it might be going to sleep and losing networking and or suspending your virtual machines. This is a setting that you can configure in your operating system, and is not related to Vagrant at all. A reload should bring up the vms properly, but not being able to reach whatever your local env url might have something to do with your app. How are you determining that you can't access your local env url?

[briancain]

Hey there,

I am going to close this due to lack of response. If this is still occurring, please open a new issue and follow the provided issue template that appears when you click the "New Issue" button. This will help us in getting a reproduction and fix. Thanks!

[ghost]

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.