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.
Related
There is an open-source project I want to install on my server, Grav, but it requires PHP 5.5.9. I currently have PHP 5.4.16 installed on a CentOS 7 server running on NGINX. Actually, it is PHP-FPM. So my question is what is the easiest and cleanest way to achieve this?
I have read many articles online regarding this and each one seems to have a different approach such as uninstalling the current version of PHP and reinstalling from scratch.
In order to get a more modern version of PHP you need to use an alternative repo. There are a few out there to choose from, that have traditionally packaged up a newer version of LAMP stack components, like Remi, but for the Centos7 vagrant I'm currently using, I went with webtatic.
You should simply follow the instructions for setting up the alternative repo with yum. Currently that involves:
rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
rpm -Uvh https://mirror.webtatic.com/yum/el7/webtatic-release.rpm
Once installed do a yum search php and you'll find php versions 5.5, 5.6, 7.0 and 7.1 to choose from.
Instead of yum install php you're going to do something like yum install php56w.
For example on my VM, this is what I have for php:
[vagrant#localhost:~]$ rpm -qa | grep php
php56w-5.6.31-1.w7.x86_64
php56w-process-5.6.31-1.w7.x86_64
php56w-opcache-5.6.31-1.w7.x86_64
php56w-xml-5.6.31-1.w7.x86_64
php56w-pear-1.10.4-1.w7.noarch
php56w-common-5.6.31-1.w7.x86_64
php56w-cli-5.6.31-1.w7.x86_64
php56w-mbstring-5.6.31-1.w7.x86_64
php56w-pdo-5.6.31-1.w7.x86_64
php56w-mysqlnd-5.6.31-1.w7.x86_64
php56w-fpm-5.6.31-1.w7.x86_64
php56w-gd-5.6.31-1.w7.x86_64
You will need to uninstall your current php version, so this is an involved operation, and you want to have done a dry run, and be confident that you know what you're doing.
As for confidence that something won't break, with Vagrant/Virtualbox/Docker etc., there is no excuse for not testing this out in a VM first.
Not to mention that these are foundation tech for state of the art development these days.
Here's a quick and simple Vagrantfile for a vanilla Centos7 box you can have up and running (assuming you get Vagrant installed and working).
# -*- mode: ruby -*-
# vi: set ft=ruby :
# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
# The most common configuration options are documented and commented below.
# For a complete reference, please see the online documentation at
# https://docs.vagrantup.com.
# Every Vagrant development environment requires a box. You can search for
# boxes at https://atlas.hashicorp.com/search.
config.vm.box = "centos/7"
# Disable automatic box update checking. If you disable this, then
# boxes will only be checked for updates when the user runs
# `vagrant box outdated`. This is not recommended.
# config.vm.box_check_update = false
# 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.
# NOTE: This will enable public access to the opened port
# config.vm.network "forwarded_port", guest: 8080, host: 8080
# config.vm.network "forwarded_port", guest: 80, host: 80
# config.vm.network "forwarded_port", guest: 3306, host: 3306
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine and only allow access
# via 127.0.0.1 to disable public access
config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"
# Create a private network, which allows host-only access to the machine
# using a specific IP.
config.vm.network "private_network", ip: "192.168.20.20"
# 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"
# 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 "./data", "/vagrant_data"
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
# config.vm.provider "virtualbox" do |vb|
# # Display the VirtualBox GUI when booting the machine
# vb.gui = true
#
# # Customize the amount of memory on the VM:
# vb.memory = "1024"
# end
#
# View the documentation for the provider you are using for more
# information on available options.
# Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
# such as FTP and Heroku are also available. See the documentation at
# https://docs.vagrantup.com/v2/push/atlas.html for more information.
# config.push.define "atlas" do |push|
# push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
# end
# Enable provisioning with a shell script. Additional provisioners such as
# Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
# documentation for more information about their specific syntax and use.
# config.vm.provision "shell", inline: <<-SHELL
# apt-get update
# apt-get install -y apache2
# SHELL
end
I am working away on my first website using the Laravel framework and am attempting top install Homestead on OS X el captin. after failing to sync my shared folders on my host and guest machine, instead of continuing to fiddle with the Homestead.ymal file, I decided to add the shared folders to the Vagrantfile manually:
# -*- mode: ruby -*-
# vi: set ft=ruby :
# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure(2) do |config|
# The most common configuration options are documented and commented below.
# For a complete reference, please see the online documentation at
# https://docs.vagrantup.com.
# Every Vagrant development environment requires a box. You can search for
# boxes at https://atlas.hashicorp.com/search.
config.vm.box = "laravel/homestead"
# Disable automatic box update checking. If you disable this, then
# boxes will only be checked for updates when the user runs
# `vagrant box outdated`. This is not recommended.
# config.vm.box_check_update = false
# 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: "192.168.33.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"
# 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 "../data", "/vagrant_data"
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
# config.vm.provider "virtualbox" do |vb|
# # Display the VirtualBox GUI when booting the machine
# vb.gui = true
#
# # Customize the amount of memory on the VM:
# vb.memory = "1024"
# end
#
# View the documentation for the provider you are using for more
# information on available options.
# Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
# such as FTP and Heroku are also available. See the documentation at
# https://docs.vagrantup.com/v2/push/atlas.html for more information.
# config.push.define "atlas" do |push|
# push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
# end
# Enable provisioning with a shell script. Additional provisioners such as
# Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
# documentation for more information about their specific syntax and use.
# config.vm.provision "shell", inline: <<-SHELL
# sudo apt-get update
# sudo apt-get install -y apache2
# SHELL
end
After making the changes, when I run vagrant up I get the following error message;
There is a syntax error in the following Vagrantfile. The syntax error message is reproduced below for convenience:
/Users/tommorison/vendor/laravel/homestead/Vagrantfile:71: syntax
error, unexpected end-of-input, expecting keyword_end
I am not understanding why i am getting this error/ i just changed the synced folders
I found a solution to this error. just edit the vagrantfile in the homestead directory and the folders would mount to vagrant. make sure there are no whitesoaces in your homestead.ymal file.
I setup a nginx+mysql puphpet/vagrant image, with a virtual host "test.com". I mapped test.com to 192.168.56.101 on the host machine, and put an index.php file inside /var/www/test.
However, when I try opening the browser at the address test.com on the host machine I get no response. I feel like I'm missing something really simple, because I can ping 192.168.56.101. I also checked nginx logs on the virtual machine, but they are empty. Any clues where the problem might be? Am I not supposed to use it this way? I can ssh into vagrant just fine, and also I can access the mysql db.
In your Vagrantfile, you need to forward the port to your host machine.
For example map port 80 of the Vagrant machine to port 8080 of the host machine.
config.vm.network "forwarded_port", guest: 80, host: 8080
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.
This is my vagrantfile:
# -*- mode: ruby -*-
# vi: set ft=ruby :
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.
# Every Vagrant virtual environment requires a box to build off of.
config.vm.box = "ubuntu32"
config.vm.provision :shell, :path => "vagrant/inicio.sh"
# The url from where the 'config.vm.box' box will be fetched if it
# doesn't already exist on the user's system.
config.vm.box_url = "http://cloud-images.ubuntu.com/vagrant/raring/current/raring-server-cloudimg-i386-vagrant-disk1.box"
# 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: 8085, auto_correct: true
config.vm.provider "virtualbox" do |v|
v.name = "funcook"
end
# Create a private network, which allows host-only access to the machine
# using a specific IP.
# config.vm.network :private_network, ip: "192.168.33.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
# 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 "../data", "/vagrant_data"
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
# config.vm.provider :virtualbox do |vb|
# # Don't boot with headless mode
# vb.gui = true
#
# # Use VBoxManage to customize the VM. For example to change memory:
# vb.customize ["modifyvm", :id, "--memory", "1024"]
# end
#
# View the documentation for the provider you're using for more
# information on available options.
# Enable provisioning with Puppet stand alone. Puppet manifests
# are contained in a directory path relative to this Vagrantfile.
# You will need to create the manifests directory and a manifest in
# the file base.pp in the manifests_path directory.
#
# An example Puppet manifest to provision the message of the day:
#
# # group { "puppet":
# # ensure => "present",
# # }
# #
# # File { owner => 0, group => 0, mode => 0644 }
# #
# # file { '/etc/motd':
# # content => "Welcome to your Vagrant-built virtual machine!
# # Managed by Puppet.\n"
# # }
#
# config.vm.provision :puppet do |puppet|
# puppet.manifests_path = "manifests"
# puppet.manifest_file = "init.pp"
# end
# Enable provisioning with chef solo, specifying a cookbooks path, roles
# path, and data_bags path (all relative to this Vagrantfile), and adding
# some recipes and/or roles.
#
# config.vm.provision :chef_solo do |chef|
# chef.cookbooks_path = "../my-recipes/cookbooks"
# chef.roles_path = "../my-recipes/roles"
# chef.data_bags_path = "../my-recipes/data_bags"
# chef.add_recipe "mysql"
# chef.add_role "web"
#
# # You may also specify custom JSON attributes:
# chef.json = { :mysql_password => "foo" }
# end
# Enable provisioning with chef server, specifying the chef server URL,
# and the path to the validation key (relative to this Vagrantfile).
#
# The Opscode Platform uses HTTPS. Substitute your organization for
# ORGNAME in the URL and validation key.
#
# If you have your own Chef Server, use the appropriate URL, which may be
# HTTP instead of HTTPS depending on your configuration. Also change the
# validation key to validation.pem.
#
# config.vm.provision :chef_client do |chef|
# chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
# chef.validation_key_path = "ORGNAME-validator.pem"
# end
#
# If you're using the Opscode platform, your validator client is
# ORGNAME-validator, replacing ORGNAME with your organization name.
#
# If you have your own Chef Server, the default validation client name is
# chef-validator, unless you changed the configuration.
#
# chef.validation_client_name = "ORGNAME-validator"
end
And this is the content of inicio.sh:
#!/usr/bin/env bash
if [ ! -f ~/initial_provosioning_done ];
then
export DEBIAN_FRONTEND=noninteractive
apt-get update
apt-get install -y -q lamp-server^ php5-gd
sed -i 's,www-data,vagrant,g' /etc/apache2/envvars
sed -i 's,/var/www,/vagrant/www,g' /etc/apache2/sites-available/default
sed -i 's,AllowOverride None,AllowOverride All,g' /etc/apache2/sites-available/default
mysqladmin -u root password root
mysql -uroot -proot < /vagrant/bd/script.sql
rm -r /var/lock/apache2
a2enmod rewrite
service apache2 restart
touch ~/initial_provosioning_done
fi
This is how I am starting the VM:
minirafa:beta.funcook.com TONIWEB$ vagrant reload
[default] Attempting graceful shutdown of VM...
[default] Clearing any previously set forwarded ports...
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] -- 80 => 8085 (adapter 1)
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
[default] Machine booted and ready!
[default] Mounting shared folders...
[default] -- /vagrant
minirafa:beta.funcook.com TONIWEB$
The thing is that:
Chrome will log:
ERR_EMPTY_RESPONSE
and:
minirafa:~ TONIWEB$ curl 'http://localhost:80'
curl: (7) couldn't connect to host
Or:
minirafa:~ TONIWEB$ curl 'http://localhost:8085'
curl: (52) Empty reply from server
minirafa:~ TONIWEB$
Usually this settings work for me with other projects,
Any idea what could I try next?
-EDIT-
Also:
minirafa:beta.funcook.com TONIWEB$ curl -v http://localhost:8085
* About to connect() to localhost port 8085 (#0)
* Trying 127.0.0.1... connected
* Connected to localhost (127.0.0.1) port 8085 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.19.7 (universal-apple-darwin10.0) libcurl/7.19.7 OpenSSL/0.9.8y zlib/1.2.3
> Host: localhost:8085
> Accept: */*
>
* Empty reply from server
* Connection #0 to host localhost left intact
curl: (52) Empty reply from server
* Closing connection #0
minirafa:beta.funcook.com TONIWEB$
When you're trying to reach localhost on port 80 with curl, you're actually trying to reach the host machine (not the guest running in virtualbox/vagrant). So if the host doesn't run a webserver (on port 80), it's normal you get a couldn't connect to host message.
You should be trying to reach localhost on port 8085, because that's the port you're forwarding to port 80 on the guest machine. And that apparently tells you Empty reply from server...
I cannot say much about this, unless I can get some additional info about the webserver running on the guest:
Is it running properly? (check the error-logs)
Does it respond to requests from inside the guest machine?
Does the request from the host reach the webserver? (check the access-logs)
If so, does the webserver encounter errors? (check the error-logs)
If not, is there a firewall is running on the guest, dropping requests to port 80?
PS: Just a tip: You could create a private network on the guest by enabling this line:
config.vm.network :private_network, ip: "192.168.33.10"
This way you can reach the webserver at 192.168.33.10:80, and won't need to forward any ports to it.