Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialJoe Li
8,104 PointsOops! Google Chrome could not connect to 0.0.0.0:3000
Hello,
I'm hoping someone can help. I was following along with the installing devise section on Rails Development and I got the message "Oops! Google Chrome could not connect to 0.0.0.0:3000" on the browser, which i'm assuming is a server issue on terminal. So I typed "rails s" to get the server back up and running and I got this message.
$ rails s Usage: rails new APP_PATH [options]
Options: -r, [--ruby=PATH] # Path to the Ruby binary of your choice # Default: /usr/local/rvm/rubies/ruby-2.1.0/bin/ruby -m, [--template=TEMPLATE] # Path to some application template (can be a filesystem path or URL) [--skip-gemfile] # Don't create a Gemfile -B, [--skip-bundle] # Don't run bundle install -G, [--skip-git] # Skip .gitignore file [--skip-keeps] # Skip source control .keep files -O, [--skip-active-record] # Skip Active Record files -S, [--skip-sprockets] # Skip Sprockets files -d, [--database=DATABASE] # Preconfigure for selected database (options: mysql/oracle/postgresql/sqlite3/frontbase/ibm_db/sqlserver/jdbcmysql/jdbcsqlite3/jdbcpostgresql/jdbc) # Default: sqlite3 -j, [--javascript=JAVASCRIPT] # Preconfigure for selected JavaScript library # Default: jquery -J, [--skip-javascript] # Skip JavaScript files [--dev] # Setup the application with Gemfile pointing to your Rails checkout [--edge] # Setup the application with Gemfile pointing to Rails repository -T, [--skip-test-unit] # Skip Test::Unit files [--rc=RC] # Path to file containing extra configuration options for rails command [--no-rc] # Skip loading of extra configuration options from .railsrc file
Runtime options: -f, [--force] # Overwrite files that already exist -p, [--pretend] # Run but do not make any changes -q, [--quiet] # Suppress status output -s, [--skip] # Skip files that already exist
Rails options: -h, [--help] # Show this help message and quit -v, [--version] # Show Rails version number and quit
Description: The 'rails new' command creates a new Rails application with a default directory structure and configuration at the path you specify.
You can specify extra command-line arguments to be used every time
'rails new' runs in the .railsrc configuration file in your home directory.
Note that the arguments specified in the .railsrc file don't affect the
defaults values shown above in this help message.
Example: rails new ~/Code/Ruby/weblog
This generates a skeletal Rails installation in ~/Code/Ruby/weblog.
See the README in the newly created application to get going.
Anyone got any ideas?
Thanks,
Joe
3 Answers
Ender Ahmet Yurt
5,599 PointsYou should go to your app folder after you create your rails app with 'rails new my_app'
you need to type;
cd my_app
and run 'rails s' on that path.
James Barnett
39,199 PointsAre you on Windows by any chance? If so there's a teacher's note that mentions to use the IP 127.0.0.1
instead of 0.0.0.0
on Windows.
Joe Li
8,104 PointsHey James,
No I'm on a mac.
Thanks,
Joe