CODEWITHSUNDEEP
ruby-on-rails
EamonnMcElroy
EamonnMcElroy

Reputation: 607

Why is rails server listing on tcp

I am working on a project which is an updated version of a new project. Using vagrant to load virtual environment and when i run

RAILS_ENV=development bundle exec rails s

The following is returned:

=> Booting Puma
=> Rails 5.0.0.1 application starting in development on http://localhost:3000
=> Run `rails server -h` for more startup options
Puma starting in single mode...
* Version 3.6.0 (ruby 2.3.3-p222), codename: Sleepy Sunday Serenity
* Min threads: 5, max threads: 5
* Environment: development
* Listening on tcp://localhost:3000
Use Ctrl-C to stop

When i visit the browser I have tried localhost:3000 and 127.0.0.1:3000 but keep getting:

ERR_CONNECTION_REFUSED

On the previous version of this project on a different repository loaded it was accessible via these URL's. This project has been updated to Rails 5 but dont know why it is listening on TCP rather than HTTP. Any suggestions?

Upvotes: 15

Views: 6010

Answers (1)

borjagvo
borjagvo

Reputation: 2081

As it has been already suggested, make sure that the server is bounden to 0.0.0.0 so that all interfaces can access it.

You might try:

RAILS_ENV=development bundle exec rails s -b 0.0.0.0

Upvotes: 1

Related Questions