Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7864143
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 2, 20262026-06-02T23:41:53+00:00 2026-06-02T23:41:53+00:00

I have installed node.js and necessary packages to run browserquest . I have started

  • 0

I have installed node.js and necessary packages to run browserquest. I have started the browserquest server, which is running on port 8080 and when I go to my browser and type http://localhost:8080/status I can see that server is running and currently no clients are connected. I build the client with configurations like this in client/config/build_config.json file

{
   "host": "http://127.0.0.1",
   "port": 8080
}

I build my client within bin/build.sh. Then I run this command to create http-server to serve client files.

http-server path-to-client-build -p 8000

I can see the index page with the httpserver running by going to http://localhost:8000/index.html but when I try to connect it gets stuck after saying connecting to server.

NOTE: I am using this http-server to host client files http://search.npmjs.org/#/http-server

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-02T23:41:54+00:00Added an answer on June 2, 2026 at 11:41 pm

    I think the client-build has some problems on the current release on github. Instead I have used the actual client folder. I have followed these steps to make it work.

    Make sure you have installed node and npm.

    1) get a copy from github repo.

    git clone https://github.com/mozilla/BrowserQuest.git
    

    2) Install the required node packages for the server

    npm install underscore log bison websocket websocket-server sanitizer memcache
    

    3) Start the server

    node server/js/main.js
    

    4) go to the client directory and install http-server module to serve the client files

    cd client
    npm install -g http-server
    

    5) edit config_build.json-dist to point to your host ip and port (in my case 127.0.0.1 localhost)

    {
    "host": "127.0.0.1",
    "port": 8000,
    "dispatcher": false
    }
    

    6) copy the edited config_build.json-dist to 2 new files

    cp config_build.json-dist config_build.json
    cp config_build.json-dist config_local.json
    

    7) copy shared folder into client folder

    cp -r ../shared .
    

    8) start the http-server to serve the client files

    http-server
    

    And your server and client should be running. You can check if the server is running by going to http://ipaddress:port/status which should display an array of connected clients. If none an empty array. And your client should be running on http://ipaddress:8000/index.html

    based on the tutorial from dirkk0
    https://gist.github.com/2275361

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have installed a program called node.js on my server to listen on port
I'm running on Windows 7 and have node installed fine with cygwin. I am
I have a perl script (call it worker) installed on each node/machine (4 total)
I have installed php5 and mysql5 on my server , I can login to
I have installed the latest node.js from here . I see the %Path% variables
Have installed Node version manager 'n'. Installed 'mocha' using n npm 0.6.4 install mocha
I'm developing on Ubuntu, I have installed the mongoid gem, and when I run
I have installed latest version of Node.js and I still have problems with SSL
I am having trouble with kiwi, the package loader from node.js I have installed
I have just installed MongoDB in my machine (Windows 7) and installed node-mongodb-native using

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.