无法连接 localhost:3000 ruby​​ on rails in vagrant

Posted 2023-03-04

【中文标题】无法连接 localhost:3000 ruby​​ on rails in vagrant

【英文标题】：can't connect localhost:3000 ruby on rails in vagrant

【发布时间】：2015-02-22 00:06:06

【问题描述】：

我尝试在 windows 中连接 localhost:3000

rails 服务器在 vagrant(ubuntu 14.10) 中运行

端口转发完成

什么时候，我试过 lynx 127.0.0.1:3000 在 ubunutu 中，它可以工作

但是，在 Windows 中，我也无法连接 localhost:3000, 127.0.0.1:3000

刚刚显示 ERR_CONNECTION_REFUSED

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

我该如何解决这个问题？

这是我的“流浪文件”

# -*- 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 仍然无法连接。一件奇怪的事情，我可以在主机中发送 Ping 到 192.168.33.10 并得到回复。我不知道问题是什么。我很困惑。有人帮助我，请:(

【问题讨论】：

您是否尝试从 Windows 环境连接到在 ubuntu 中运行的 Rails 应用程序？如果是这样，它们不是同一个本地主机...确定您的 ubuntu 在网络上的 ip

@LoganMurphy 在一些关于 vagrant 的网页中，我看到 vagrant portforward 是自动的。我在 Vagrantfile 中插入行 config.vm.network "forwarded_port", guest: 3000, host: 3000

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

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

@BMW 我添加了我的'Vagrantfile'，请检查一下，谢谢

【参考方案1】：

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

rails s -b 0.0.0.0

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

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

【讨论】：

其实应该是rails s -b 0.0.0.0，“b”代表“绑定”

@user860478 感谢您的帮助。

也适用于 Thin。谢谢

真是惊喜...我一直认为rails server 除非指定，否则默认侦听所有接口。有一个很好的答案展示了如何实现这种行为：***.com/questions/28668436/…

【参考方案2】：

我也做了这样的事情，所以 Guard 以这种方式开始： guard 'rails', force_run: true, host: '0.0.0.0' do watch('Gemfile.lock') watch(%r^(config|lib)/.*) end

【参考方案3】：

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

由于 Rack 的变化，rails 服务器现在默认侦听 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

【讨论】：

shilovk 在***.com/questions/27799260 的回答要好一些，因为它考虑了环境