无法在Vagrant中连接localhost:3000的Ruby on Rails

Question

我尝试在Windows上连接localhost:3000

rails服务器正在vagrant（ubuntu 14.10）中运行

端口转发已完成

当我在Ubuntu中尝试使用lynx 127.0.0.1:3000时，它可以正常工作

但是，在Windows中，我无法连接到localhost:3000或127.0.0.1:3000

只显示ERR_CONNECTION_REFUSED

在cmd中，我运行了netstat -t的结果是：3000 TIME_WAIT

我该如何解决这个问题？

这是我的'Vagrantfile'

# -*- 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 = "ubuntu 14.10"

  # 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 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 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: "3000", host: "3000"

  # 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 install apache2
  # SHELL
end

编辑： 我尝试使用Host-only网络适配器，并尝试在主机上连接192.168.33.10:3000，但仍然无法连接。奇怪的是，我可以在主机上向192.168.33.10发送Ping请求，并且收到了回复。我不知道问题出在哪里。我很困惑，请有人帮帮我 :(

- Henry

---

你是否正在尝试从Windows环境连接到在Ubuntu上运行的Rails应用程序？如果是这样，它们不是同一个本地主机...请确定Ubuntu在网络上的IP地址。 - Logan Murphy

@LoganMurphy 在一些Vagrant的网页中，我看到了自动端口转发。于是我在Vagrantfile中插入了这行代码：config.vm.network "forwarded_port", guest: 3000, host: 3000。 - Henry

@LoganMurphy 但我可以通过ssh连接到Ubuntu的localhost:2222。如果可能的话，我认为localhost:3000也是可达的。 - Henry

你需要在Vagrantfile中设置端口转发。请向我们展示你的Vagrantfile。 - BMW

@BMW，我添加了我的“Vagrantfile”，请检查一下，谢谢。 - Henry

有人建议取消注释 # config.vm.network "private_network", ip:"192.168.33.10"。所以我这么做了，但还是不起作用。 - Henry

Answer 1

解决方案是运行下面的代码来启动您的服务器：

rails s -b 0.0.0.0

我在另一篇有关同样问题的帖子中找到了这个解决方案。答复者说“你需要确保服务器绑定到0.0.0.0，以便所有接口都可以访问它。”

希望这篇文章能帮助遇到同样问题的人们 :)

- Henry

---

实际上应该是 rails s -b 0.0.0.0，其中 "b" 代表 "bind"。 - Victor Marchuk

@user860478 感谢您的帮助。 - Henry

也适用于Thin。谢谢 - Mauro

真是个惊喜...我一直以为 rails server 默认会监听所有接口，除非另有指定。这里有一个很好的答案展示了如何实现这种行为：https://dev59.com/KV4b5IYBdhLWcg3wzUcp#29562898 - Paul

Answer 2

你可以在这里找到原因：http://edgeguides.rubyonrails.org/4_2_release_notes.html

由于 Rack 的更改，现在 rails server 默认监听 localhost 而不是 0.0.0.0。

如果你想使用 rails s 而不是 rails s -b 0.0.0.0，你可以编辑 /config/boot.rb：

ENV['BUNDLE_GEMFILE'] ||= File.expand_path('../../Gemfile', __FILE__)

require 'bundler/setup' if File.exist?(ENV['BUNDLE_GEMFILE'])

require 'rails/commands/server'

module Rails
  class Server
    alias :default_options_alias :default_options
    def default_options
      default_options_alias.merge!(:Host => '0.0.0.0')
    end
  end
end

- Khan Dz

---

shilovk在https://dev59.com/Cl4c5IYBdhLWcg3wia5P的回答更好一些，因为它考虑了环境。 - StringsOnFire

Answer 3

我已经做了类似的事情，以便Guard以这种方式启动： guard 'rails'，force_run：true，host：'0.0.0.0' do watch('Gemfile.lock') watch（％r {^（config | lib）/。*}） end

- user945747