Vagrant refuses to connect in private_network mode [closed]

Question

I have set my Vagrant (1.2.2) VM running VistualBox to :private_network and I have started a Sinatra server on it. However I am not able to connect to that Sinatra instance. However the VM runs and responds to pings.

Here is my Vagrantfile

Vagrant.configure("2") do |config|
    config.vm.box = "precise64"
    config.vm.network :private_network, ip: "192.168.33.10"
end

So I start the Vagrant VM and ssh into it

prodserv$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Setting the name of the 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] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /vagrant

prodserv$ vagrant ssh
Welcome to Ubuntu 12.04.2 LTS (GNU/Linux 3.2.0-23-generic x86_64)

* Documentation:  https://help.ubuntu.com/
Welcome to your Vagrant-built virtual machine.
Last login: Thu May 23 14:01:05 2013 from 10.0.2.2

So up to here all is fine and dandy. A ping to the VM will work fine (I also checked that this is really the VMs ip. So pinging without vagrant up will lead to package loss)

prodserv$ ping 192.168.33.10
PING 192.168.33.10 (192.168.33.10): 56 data bytes
64 bytes from 192.168.33.10: icmp_seq=0 ttl=64 time=0.543 ms
64 bytes from 192.168.33.10: icmp_seq=1 ttl=64 time=0.328 ms

great! Now I start the server on the VM

vagrant@precise64:~$ sudo ruby /vagrant/server.rb
== Sinatra/1.4.2 has taken the stage on 4567 for development with backup from Thin
>> Thin web server (v1.5.1 codename Straight Razor)
>> Maximum connections set to 1024
>> Listening on localhost:4567, CTRL+C to stop

this is the corresponding server.rb

require 'rubygems'
require 'sinatra'

get '/' do
    puts "WOW!"
    'Hello, world!'
end

if I curl now from the guest VM to Sinatra everything works fine and "hello, world!" will be returned.

vagrant@precise64:~$ curl 'http://localhost:4567'
Hello, world!vagrant@precise64:~$

#and the Sintra/Ruby process gets me this
WOW!
127.0.0.1 - - [23/May/2013 16:06:36] "GET / HTTP/1.1" 200 13 0.0026

However if I try to to curl from the host machine the connection gets refused.

prodserv$ curl -v 'http://192.168.33.10:4567'
* About to connect() to 192.168.33.10 port 4567 (#0)
*   Trying 192.168.33.10...
* Connection refused
* couldn't connect to host
* Closing connection #0
curl: (7) couldn't connect to host

So whats up?

Answer 1

Your sinatra is listening on localhost:4567, instead of 0.0.0.0 so it's only available for localhost.