Access webrick/rails from another computer on local network

Asked 6/9, 2011 at 20:19 Answered 10/5, 2018 at 16:35

I have a rails application running on localhost:3000. I wish to access it from another computer on the same network. I feel like i've done this before with ease, but it's giving me some grief. I can ping the IP of the computer just fine, but hitting ip:3000 in the browser doesnt work. I tried launching rails s -b ipaddress as well, and no luck.

Suggestions?

Dactylology answered 6/9, 2011 at 20:19 Comment(7)

Do you have a firewall blocking this access? – Jeannajeanne 6/9, 2011 at 20:23

Hard to say as it is on my works network, not at home. The computer running it is wired in to the 192.168.100 subnet. My second computer is a laptop on wifi, same subnet. – Dactylology 6/9, 2011 at 20:26

Try running it on port 80 instead of 3000 – Anfractuous 6/9, 2011 at 20:28

yep, that would do it. Works now :). If you wish, post your answer and i shall accept, – Dactylology 6/9, 2011 at 20:31

I'm having the same issue, though I'm already running rails on port 80 (-p 80) and I still can't access it from other computer on same network. I still can access other apps like SVN and UberSVN web interface from other computers, but not ruby. Any help? – Daystar 26/10, 2012 at 11:30

did you broadcast on its IP as well? Let's say the machine it sits on is 192.168.100.50, on that machine, run: rails s -b 192.168.100.50 -p 80 – Dactylology 26/10, 2012 at 13:43

@agmcleod, yep, tried that too! I got it to work on port 3000, but I'd appreciate to have it sitting on port 80 – Daystar 26/10, 2012 at 22:23

Try running the server on port 80 instead, your firewall is probably blocking port 3000.

Anfractuous answered 6/9, 2011 at 20:40 Comment(3)

I did this, but still can't access myip:80 either from the same machine or another one in the same network – Mantelet 14/12, 2012 at 0:38

OneHoopyFrood answer is perfect – Tetter 22/12, 2015 at 6:53

OneHoopyFrood's answer should be the one checked. This answer is rather wishy washy – Riparian 14/10, 2016 at 14:19

201

After making sure your server side firewall is open to the incoming connection on high ports (this is normally true and the default port is 3000, so you probably don't have to do anything) you must also start the server like this:

rails server -b 0.0.0.0

which binds it to the universal address. It binds to localhost by default.

Using this method you don't have to bind to port 80, but you can like this:

rails server -b 0.0.0.0 -p 80

(If you're using rvm then you may need to use rvmsudo)

To make this change more permanent edit your config/boot.rb and add this:

require 'rails/commands/server'
module Rails
  class Server
    def default_options
      super.merge(Host:  '0.0.0.0', Port: 3000)
    end
  end
end

Then you should only have to use rails s

_{Source: https://mcmap.net/q/195841/-how-to-change-the-default-binding-ip-of-rails-4-2-development-server}

Phototypy answered 9/3, 2015 at 17:35 Comment(5)

Chosen answer didn't help me as firewall was already disabled, however, this one did. – Loeffler 29/3, 2015 at 18:49

Without disabling the firewall "rails server -b 0.0.0.0" did not work for me. First I had to disable the firewall using: "sudo ufw disable" then ran server using: "rails server -b 0.0.0.0" – Clemons 4/8, 2016 at 8:7

@AfzalMasood, sounds like you pre-configured you ufw to deny all by default. That's a good practice! Just allow port 3000 in your rules and it should play nice. :) – Phototypy 16/8, 2016 at 22:5

@Phototypy May be but I never changed anything related to firewall or deny all by defualt. – Clemons 17/8, 2016 at 8:22

If you don't have rvmsudo you can simply use sudo rails server -b 0.0.0.0 -p 80 (or just sudo rails s if you edit boot.rb) if you want to use port 80. – Torpedo 14/3, 2017 at 15:41

rails server -b 0.0.0.0 -p 8000

This worked for me. No firewall issues, and no need to give super user permissions.

Legitimist answered 2/9, 2015 at 14:29 Comment(0)

Yes, this was a good answer in general:
```
rails server -b 0.0.0.0
```
If you use Ubuntu, you probably have to open the port in the firewall:
```
sudo ufw allow 3000
```
If your system is running in VirtualBox, you have to check your Network Settings.

In the case of network mode NAT you have to click to the extended options and there to Port Forwarding. Add a rule for TCP protocoll, host port 3000 (or any other), and guest port 3000.

Rom answered 18/12, 2016 at 20:32 Comment(0)

Assuming Webrick starts without issue, this is 100% a firewall issue. You should provide some specifications, like what operating system your host is running and whether or not you have administrator privileges as far as controlling the firewall.

If you're on Linux and running the iptables firewall service, you need to add a rule to accept traffic over port 3000. It would look something like:

iptables -A INPUT -p tcp --dport 3000 -j ACCEPT

That command would be a one-time-only solution though, you'd need to extend your current iptables rules script to make it permanent every time your system boots or logs in.

If you're running Windows, depending on whether you're running XP or Vista/7, you'd need to do something similar. I'm going to assume you're in the Vista/7 environment, and you would just need to follow the steps provided through this guide http://windows.microsoft.com/en-US/windows7/Open-a-port-in-Windows-Firewall.

Salient answered 6/9, 2011 at 20:38 Comment(0)

I am using foreman to manage my Procfile-based application.

Adding -b 0.0.0.0 to my bundle exec rails s command in Procfile worked for me.

Synchronous answered 10/5, 2018 at 16:35 Comment(0)

Try running the server on port 80 instead, your firewall is probably blocking port 3000.

Anfractuous answered 6/9, 2011 at 20:40 Comment(3)

I did this, but still can't access myip:80 either from the same machine or another one in the same network – Mantelet 14/12, 2012 at 0:38

OneHoopyFrood answer is perfect – Tetter 22/12, 2015 at 6:53

OneHoopyFrood's answer should be the one checked. This answer is rather wishy washy – Riparian 14/10, 2016 at 14:19

One reason is your ip is not bind to the rails server. You can bind the ip with -b command option.

Usage: rails server [mongrel, thin etc] [options]
-p, --port=port                  Runs Rails on the specified port.
                                 Default: 3000
-b, --binding=IP                 Binds Rails to the specified IP.
                                 Default: localhost

Distrustful answered 21/10, 2015 at 10:20 Comment(0)

Recommended topics

Hot tags