Go to " homestead/scripts/homestead.rb "
and set
config.vm.network "forwarded_port", guest: 80, host: 1050
And you done .
If you are running any host process in the port 8000 you could kill it and re-run the vagrant up command.
Today I had the same issue and I search the process with the netstat command and searching the PID process I killed it and follow the process.
In my case was a VirtualBox process that I killed and solve my issue.
Hope it helps you.
I've done this:
I encountered this when running per-project homestead instances.
Looking at the homestead.rb file in the latest v2 version there is a port override, so rather than modifying the Vagrantfile or the homestead.rb file you can just provide the new ports in the Homestead.yaml e.g.
ports:
- guest: 80
host: 8001
- guest: 443
host: 44301
- guest: 3306
host: 33061
- guest: 5432
host: 54321
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community