vagrant laravel homestead http server IP-адрес

Question

После запуска «бродяги вверх», я не могу получить доступ к http-серверу в своем браузере при доступе к «http://192.168.10.10/». Я просто получаю ошибку «404 файл не найден».

Ниже приведены мои файлы конфигурации и журнал из «vagrant up».

Благодаря А.

YAML файл:

ip: "192.168.10.10" 
memory: 2048 
cpus: 1 
provider: virtualbox 

authorize: ~/Vagrant/Homestead/homestead.pub 

keys: 
    - ~/.ssh/id_rsa 

folders: 
    - map: ~/Code 
     to: /home/vagrant/Code 

sites: 
    - map: homestead.app 
     to: ~/Code/public 
     hhvm: true 

databases: 
    - homestead 

Vagrantfile:

require 'json' 
require 'yaml' 

VAGRANTFILE_API_VERSION = "2" 
confDir = $confDir ||= File.expand_path("~/.homestead") 

homesteadYamlPath = confDir + "/Homestead.yaml" 
homesteadJsonPath = confDir + "/Homestead.json" 
afterScriptPath = confDir + "/after.sh" 
aliasesPath = confDir + "/aliases" 

require File.expand_path(File.dirname(__FILE__) + '/scripts/homestead.rb') 

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| 
    if File.exists? aliasesPath then 
     config.vm.provision "file", source: aliasesPath, destination: "~/.bash_aliases" 
    end 

    if File.exists? homesteadYamlPath then 
     Homestead.configure(config, YAML::load(File.read(homesteadYamlPath))) 
    elsif File.exists? homesteadJsonPath then 
     Homestead.configure(config, JSON.parse(File.read(homesteadJsonPath))) 
    end 

    if File.exists? afterScriptPath then 
     config.vm.provision "shell", path: afterScriptPath 
    end 
end 

Войти с "Бродячей вверх":

C:\Users\Anders\Vagrant\Homestead>vagrant reload 
==> default: Attempting graceful shutdown of VM... 
==> default: Checking if box 'laravel/homestead' is up to date... 
==> default: Clearing any previously set forwarded ports... 
==> default: Clearing any previously set network interfaces... 
==> default: Preparing network interfaces based on configuration... 
    default: Adapter 1: nat 
    default: Adapter 2: hostonly 
==> default: Forwarding ports... 
    default: 80 (guest) => 8000 (host) (adapter 1) 
    default: 443 (guest) => 44300 (host) (adapter 1) 
    default: 3306 (guest) => 33060 (host) (adapter 1) 
    default: 5432 (guest) => 54320 (host) (adapter 1) 
    default: 22 (guest) => 2222 (host) (adapter 1) 
==> default: Running 'pre-boot' VM customizations... 
==> default: Booting VM... 
==> default: Waiting for machine to boot. This may take a few minutes... 
    default: SSH address: 127.0.0.1:2222 
    default: SSH username: vagrant 
    default: SSH auth method: private key 
==> default: Machine booted and ready! 
Got different reports about installed GuestAdditions version: 
Virtualbox on your host claims: 5.0.12 
VBoxService inside the vm claims: 5.0.16 
Going on, assuming VBoxService is correct... 
GuestAdditions seems to be installed (5.0.16) correctly, but not running. 
Got different reports about installed GuestAdditions version: 
Virtualbox on your host claims: 5.0.12 
VBoxService inside the vm claims: 5.0.16 
Going on, assuming VBoxService is correct... 
Usage: service <option> | --status-all | [ service_name [ command | --full-restart ] ] 
bash: line 4: vboxadd: command not found 
Got different reports about installed GuestAdditions version: 
Virtualbox on your host claims: 5.0.12 
VBoxService inside the vm claims: 5.0.16 
Going on, assuming VBoxService is correct... 
Removing existing VirtualBox DKMS kernel modules ...done. 
Removing existing VirtualBox non-DKMS kernel modules ...done. 
Building the VirtualBox Guest Additions kernel modules ...done. 
Doing non-kernel setup of the Guest Additions ...done. 
You should restart your guest to make sure the new modules are actually used 

Restarting VM to apply changes... 
==> default: Attempting graceful shutdown of VM... 
==> default: Booting VM... 
==> default: Waiting for machine to boot. This may take a few minutes... 
    default: SSH address: 127.0.0.1:2222 
    default: SSH username: vagrant 
    default: SSH auth method: private key 
==> default: Machine booted and ready! 
==> default: Checking for guest additions in VM... 
==> default: Setting hostname... 
==> default: Configuring and enabling network interfaces... 
==> default: Mounting shared folders... 
    default: /vagrant => C:/Users/Anders/Vagrant/Homestead 
    default: /home/vagrant/Code => C:/Users/Anders/Code 
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision` 
==> default: flag to force provisioning. Provisioners marked to run always will still run. 

C:\Users\Anders\Vagrant\Homestead> 

Answer 1

Если вы используете Windows, установите map (под folder) в homestead.yaml что-то вроде: c:\projects\my_laravel_project вместо ~/Code. После этого запускают vagrant provision.

Answer 2

Ничего плохого в конфигурациях. Но когда вы вводите этот адрес, у вас должно быть что-то вроде index.html внутри вашей сопоставленной по умолчанию папки.

Может быть устройство, использующее 192.168.10.10, так как оно может использоваться в вашей реальной домашней сети. Если это так, попробуйте изменить его.