Take a look for the network of virtualbox. What says ifconfig at the host machine?

Sure - here's what it says for vboxnet0 (I ran ifconfig on the host machine):

vboxnet0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
    ether 0a:00:27:00:00:00 
    inet 192.168.10.1 netmask 0xffffff00 broadcast 192.168.10.255

Thanks!

I now know what the problem is. Somehow, the box listens to 127.0.0.1:8000from the host machine instead of 192.168.10.10:80.

So I can test my projects now, with the hassle of having to append :8000 to the URLs. That's weird, the homestead.yaml specifically says to be available at 192.168.10.10 ...

This is a little trick, but not the solution. Try ping to 192.168.10.1. Perhaps there is a mismatch with the network options in virtualbox?

I tried pinging 192.168.10.1, but still no luck. It times out as well.

Even tried matching the IP in the Homestead.yaml to 192.168.10.1 and reprovisioning+rebooting the box, but that didn't help either.

How can I find out if there's a mismatch within the network options? I just checked the virtualbox GUI, but it doesn't provide too much information under the network settings...

Have you tried restarting the host machine? if the host updated the kernel it could cause virtualbox to fail in wierd ways. A restart should re load all kernel modules including the virtualbox one and that could fix it.

Well, so that was exactly it. Somehow it didn't come to my mind to reboot the host as well. Thanks to both of you!

What I found out is that you need to edit the Vagrantfile in the homeasted directory on line 29 to create private network. This allowed me to ping the 192.168.10.10 IP successfully and connect to database from HeidiSql.

Create a private network, which allows host-only access to the machine using a specific IP.

config.vm.network "private_network", ip: "192.168.10.10"

Hope this help some people.

Sorry for necro-ing an old thread, but I also often ran into this issue, and as suggested by one of the reply, rebooting the machine fixes the issue.

Though I'm not sure what is the exact root cause, in my case it happens often enough that rebooting the machine isn't really an option (it seems to happen when I connect to some of my VPN).

So if anyone is also running into similar issue, rebooting the vbox network interface seems to also achieve the same thing without rebooting.

sudo ifconfig vboxnet0 down && sudo ifconfig vboxnet up on macos. You can see the interface the vm is using on the Virtualbox app.

@HENDRA - This works beautifully. I was searching for a way to accomplish this without having to restart my host machine. I was able to verify vboxnet0 in the Virtualbox GUI, and made one tweak to your suggestion:

sudo ifconfig vboxnet0 down && sudo ifconfig vboxnet0 up worked for me - making sure the interface name is the same in both directives. (Otherwise it would fail on my machine.) For those looking for where to find this info, in Virtualbox GUI, go to Machine Tools > Details to ensure details are being shown, and then look in the Network pane - for me it was Adapter 2 (Host Only Adapter, 'vboxnet0')

Just wanted to give you some kudos for providing this workaround that doesn't require the entire host machine to be rebooted!

Same problem here. Found out after hours of searching that changing the IP to 192.168.56.4 in Homestead.yaml and /etc/hosts file fixed it for me

Updating the IP solved my issue as well. I also wanted to reference the GitHub issue here for visibility: https://github.com/laravel/homestead/issues/1717

Here, when connected to a VPN using a Windows 11 built-in solution, I couldn't ping/access the 192.168.10.10. After DISCONNECTING from VPN, the virtual machine was accessible.