My machine and Android devices are on the same network.
Machine IP: 192.168.0.11
The IP where Homestead is running: 192.168.10.10
If I enter 192.168.0.11:8000 on my Android device I can use only one site.
How can I enter all sites stored in Homestead?
This is my Homestead.yaml file:
---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: ~/Homestead-Projects
to: /home/vagrant/Homestead-Projects
sites:
- map: site1.com
to: /home/vagrant/Homestead-Projects/Site1/public
- map: site2.app
to: /home/vagrant/Homestead-Projects/Site2/public
databases:
- homestead
- db_site1
- db_site2
variables:
- key: APP_ENV
value: local
# blackfire:
# - id: foo
# token: bar
# client-id: foo
# client-token: bar
# ports:
# - send: 93000
# to: 9300
# - send: 7777
# to: 777
# protocol: udp
This is my hosts file:
127.0.0.1 localhost
127.0.1.1 host
#Virtual Hosts on Homestead
192.168.10.10 site1.com
192.168.10.10 site2.com
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
tl;dr
You have to add a row for each site in your host file on the remote machine (just like in the server where Homestead is running) but with the server's IP adress. Then just type sitename.local:8000.
Example
In your case the server's IP is 192.168.0.11. Within this server, Homestead serves requests on 192.168.10.10. So in the host file of the server you have these lines:
192.168.10.10 site1.com
192.168.10.10 site2.com
You have to copy these rows to the remote PC's host file and then replace the IP address with the server's IP: 192.168.0.11.
192.168.0.11 site1.com
192.168.0.11 site2.com
Depending on your OS you may have to restart the PC or the DNS service. After that, you can access the sites from the remote PC in these addresses:
site1.com:8000
site2.com:8000
Note
Keep in mind that editing (writing) the hosts file requires superuser/administrator permissions. This is easy to solve in a PC, if you have access to the administrator account, but can be complicated on a mobile device. For Android check out these questions:
Android Enthusiasts: How to edit 'etc/hosts' file?
Stack Overflow: How to change the hosts file on android?
You can use http://xip.io/ to setup a magic domain name and you can use these domains to access virtual hosts on your development web server from devices on your local network.
Installation is also easy too https://github.com/basecamp/xip-pdns
If you are using vagrant you can also use vagrant share.
I believe this is the right answer acess homestead from external
all you need to just add default server on your nginx.conf
listen 80 default_server;
Related
I am new in laravel. I have installed homestead 10.0.0. and successfully created a project.
I am facing a problem accessing my laravel project website via typing custom web address for the website "udemylaravel.app" but if I enter 192.168.10.10 I can access the website.
here is my configuration of nano /etc/hosts
127.0.0.1 localhost
127.0.1.1 laravel-udemy laravel-udemy
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
#### HOMESTEAD-SITES-BEGIN
192.168.10.10 udemylaravel.app
#### HOMESTEAD-SITES-END
# Laravel
192.168.10.10 udemylaravel.app
And here is my homestead.yaml file
ip: 192.168.10.10
memory: 2048
cpus: 2
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
-
map: 'C:\Users\S\laravel-udemy'
to: /home/vagrant/code
sites:
-
map: udemylaravel.app
to: /home/vagrant/code/public
databases:
- homestead
features:
-
mariadb: false
-
ohmyzsh: false
-
webdriver: false
name: laravel-udemy
hostname: laravel-udemy
please help me.
Thanks in advance.
Everything seems fine. Try vagrant reload --provision to update the Nginx configuration on the virtual machine.
When I goto my host ao.dev:8000 or ao.dev, "this site can't be reached,ao.dev refused to connect" is displayed.
My yaml file:
also i've my view file:
i've checked:
I've run vagrant up command by going to Homestead directory .
Also see: https://stackoverflow.com/questions/38801375/vagrant-up-not-forwarding-all-portshomesteadlaravel-5-2windows-10
Actually I was using WAMP before installing homestead.
So I uninstalled both i.e. wamp and homestead setup including vagrant and virtual box.
Then I installed homestead setup again and it worked.
I dont know the logic behind but maybe wamp and homestead were conflicting.
It worked so I posted the answer.
What I needed to do to get my local Laravel up and running:
use 127.0.0.1 rather than 192.168.10.10 in my hosts file
make sure the .env file had the correct hostname listed as the APP_URL
make sure to use the :8000 port to access the site
Additionally:
if you're adding multiple sites, make sure to run vagrant provision after adding each site to your Homestead.yaml
not sure if it makes a difference, but you might want to put a space after the colon for the map command, i.e. map: ao.dev
I did not need to add hostname or name elements to Homestead.yaml
Here is an example Homestead.yaml file from one of my own projects:
---
ip: "192.168.10.10"
memory: 2048
cpus: 2
hostname: vm
name: vm
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: "."
to: "/home/vagrant/example"
sites:
- map: example.dev
to: "/home/vagrant/example/public"
databases:
- example
# blackfire:
# - id: foo
# token: bar
# client-id: foo
# client-token: bar
# ports:
# - send: 50000
# to: 5000
# - send: 7777
# to: 777
# protocol: udp
Notice how my paths are double-quoted (to: "/home/vagrant/example")? In your code above, these paths are not double-quoted as they should be.
I also recommend after you fix your configuration that you completely destroy and re-create your VM by running:
vagrant destroy -f && vagrant up
In your Laravel project root directory.
Your Vagrant VM machine is up but you can't reach to the machine.
Can you paste your hosts file on your host machine?
Can you paste the output of a "nmap 192.168.10.10" from your host machine?
Can you paste "ls /etc/nginx/sites-enabled/ -la" on your Vagrant VM machine?
I had the same problem, I installed and run fiddler and it was enough to solve it.
I'm following larcast tutorials for up and running laravel i have setup the laravel its working fine now i wanted it through vagrant on my windows.
But i can't run my app when ever i browse "todo.app:8000" the pages doesn't response and displays the message "web page not avaliable".
however when i was setting it up on the first time i could access the page through "localhost:8000" and i was accessing it without "php artisan serve" command, but couldn't with "todo.app:8000" after that i updated composer and restarted machine and things gone even worst now i can't even access it with "localhost:8000" while if i run "php artisan serve" it works right.
Also there is no error on running homestead,vagrant or laravel commands they are working just fine. Can anyone please tell what i'm doing wrong ?
This is my homestead.yml file
---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: ~/code
to: /home/vagrant/code
sites:
- map: todo.app
to: /home/vagrant/code/learning-laravel-5/public
databases:
- homestead
variables:
- key: AAP_ENV
value: local
# blackfire:
# - id: foo
# token: bar
# client-id: foo
# client-token: bar
# ports:
# - send: 50000
# to: 5000
# - send: 7777
# to: 777
# protocol: udp
These are the configuration i have done in windows host file
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
127.0.0.1 todo.app
127.0.0.1 mynew.app
If anything else is needed then please tell that also. I have already spent whole day in figure it out but i'm stuck here. Thanks in advance
There are a couple of points to address (1 and 2 should fix your issue):
you cannot have todo.app point to your 127.0.0.1, you need to change 127.0.0.1 to the IP of your VM (192.168.10.10)
It would be http://todo.app not http://todo
Do you have port forwarding ? from your excerpt its commented, do you forward 80 to 8000, or do you have something running on the 8000 port of the VM ?
If you do localhost:8000, it assumes that you have forwarded port 80 from the VM to 8000 on the host while todo.app:8000 will directly point you to the VM and get what is running from the 8000 port of the VM.
You have a fixed IP address, so you can use http://192.168.10.10 to access your laravel
I have been trying to get laravel working for over a week now and have come close, but I am unable the project in my web browser. I receive the 'No input file specified" when I direct to 127.0.0.1:8000. I have tried every solution I have found on the web, but can not find a solution. I am using the latest version of vagrant, virtualbox, composer and homestead.
My Yaml is:
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: ~/Projects
to: /home/vagrant/Code
sites:
- map: laravel.dev
to: /home/vagrant/Code/laravel-basics/public
hhvm: true
databases:
- homestead
variables:
- key: APP_ENV
value: local
Vagrant file is:
require 'json'
require 'yaml'
VAGRANTFILE_API_VERSION = "2"
confDir = $confDir ||= File.expand_path("~/.homestead")
homesteadYamlPath = confDir + "/Homestead.yaml"
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
Homestead.configure(config, YAML::load(File.read(homesteadYamlPath)))
if File.exists? afterScriptPath then
config.vm.provision "shell", path: afterScriptPath
end
end
Vagrant.configure("2") do |config|
config.vm.box = "laravel/homestead"
config.vm.network :forwarded_port, host: 4567, guest: 80
end
Hosts File
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
127.0.0.1 laravel.dev
I'm not sure where you got port 8000 from.
This line:
config.vm.network :forwarded_port, host: 4567, guest: 80
Says that, on your master machine (what you're reading this from), port 4567 will be forwarded to your guest machine's (the VM you spin up) port 80.
However, this is not necessary to know. Apache and Nginx listen to port 80 by default, and all browsers us it when you visit a URL.
This means that this line in your /etc/hosts file,
127.0.0.1 laravel.dev
allows you go to go http://laravel.dev without anything further.
If this is still not working, you have a few options:
Use $ vagrant ssh to go into the VM and read the Nginx logs. I believe they should be at /var/logs/nginx/{vhost_name}.
I have an older, more mature, more powerful alternative to Homestead: https://puphpet.com. I've successfully spun up Laravel, SF2, ZF2 and countless other frameworks through this.
I am unable to connect to the internet from within a Vagrant virtual machine I have set up.
For example, at the root, when I type:
curl http://google.com
It fails with the message:
curl: (6) Couldn't resolve host 'google.com'
I'm not sure if it's a firewall setting, although as far as I know I have not created any firewall rules for port 80 or any other port.
Here is the relevant section of my Vagrantfile. If there is any other information I can provide please let me know in the comments:
Vagrant.configure("2") do |config|
# All Vagrant configuration is done here. The most common configuration
# options are documented and commented below. For a complete reference,
# please see the online documentation at vagrantup.com.
# Let Vagrant manage the hostname at boot
config.vm.hostname = "devbox"
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing "localhost:8080" will access port 80 on the guest machine.
# config.vm.network :forwarded_port, guest: 80, host: 8080
# Create a private network, which allows host-only access to the machine
# using a specific IP.
config.vm.network :private_network, ip: "10.0.0.10"
# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
# config.vm.network :public_network
# Create a public network with a given hardware address. You can
# configure your DHCP server (on your router) to assign a particular IP
# address to the VM. Update your hosts file accordingly.
# config.vm.network :public_network, mac: "0a00251010101"
# Share an additional folder to the guest VM. The first argument is
# the path on the host to the actual folder. The second argument is
# the path on the guest to mount the folder. And the optional third
# argument is a set of non-required options.
#config.vm.synced_folder "vagrant/logs", "/logs",
# owner: "root", group: "root"
# Base box to use with Virtualbox provider
config.vm.box = "debian-7.0.0-amd64-base"
config.vm.box_url = "http:/mysite.com/debian-7.0.0-amd64-base.box"
This looks like a DNS configuration issue. Do a nslookup google.com and see what the result is.
Try to add the following block in your Vagrantfile, set --natdnshostresolver1 to on so as to force the VirtualBox NAT engine to intercept DNS requests and forward them to host's resolver
config.vm.provider :virtualbox do |vb|
vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
end
BTW: Without vagrant reload, you can directly look into the /etc/resolv.conf inside the VM, can manually set it to the DNS server of your network, most likely it'll work fine.