62

I'm trying to start serving some static web pages using connect like this:

var connect = require("connect");
var nowjs = require("now");
var io = require("socket.io");


var app = connect.createServer(
  connect.static(__dirname + '/public')
);

app.listen(8180);

So I added a simple index.html at the /public directory on the same directory as the app.js file is, but when I try to view the page on my browser I get this response from node:

Cannot GET /

What am I doing wrong and how can I correct it?

Judith
  • 105
  • 8
Nathan Campos
  • 28,769
  • 59
  • 194
  • 300

13 Answers13

37

You'll see the message Cannot GET / if you don't specify which page it is that you're trying to get, in other words if your URL is something like http://localhost:8180. Make sure you enter a page name, e.g. http://localhost:8180/index.html.

Stuart Hallows
  • 8,795
  • 5
  • 45
  • 57
26

You may be here because you're reading the Apress PRO AngularJS book...

As is described in a comment to this question by KnarfaLingus:

[START QUOTE]

The connect module has been reorganized. do:

npm install connect 

and also

npm install serve-static

Afterward your server.js can be written as:

var connect = require('connect');
var serveStatic = require('serve-static'); 
var app = connect(); 

app.use(serveStatic('../angularjs')); 

app.listen(5000);

[END QUOTE]

Although I do it, as the book suggests, in a more concise way like this:

var connect = require('connect');
var serveStatic = require('serve-static');

connect().use(
    serveStatic("../angularjs")
).listen(5000);
Community
  • 1
  • 1
Serj Sagan
  • 28,927
  • 17
  • 154
  • 183
  • 1
    Thanks for that also, helped me solve mine. Incidentally I'm going through the ProAngularJS book trying to get it set up on my MacBookPro and I ended up structuring my directory as "Apress/angularjs", where server.js resides in the "Apress" directory; in that case the path in the server.js code would be serveStatic("angularjs"). Once I did that the simple test in Chapter 1 of the Apress book succeeded and I'm now successfully serving up the test page. Thanks again @Serj for your post. – David Barrows Aug 10 '14 at 07:05
14

This code should work:

var connect = require("connect");

var app = connect.createServer().use(connect.static(__dirname + '/public'));

app.listen(8180);

Also in connect 2.0 .createServer() method deprecated. Use connect() instead.

var connect = require("connect");

var app = connect().use(connect.static(__dirname + '/public'));

app.listen(8180);
Vadim Baryshev
  • 25,689
  • 4
  • 56
  • 48
  • 8
    Ahh, thanks very much. All these old node.js articles makes me really confused with the deprecated things. – Nathan Campos Mar 09 '12 at 01:42
  • 1
    I have tried both of these and they both say that undefined is not a function. In the first example this tells me that .createServer() is not a function and in the second example __dirname is invalid. – Coded Container Oct 16 '15 at 14:16
3

You might be needed to restart the process if app.get not working. Press ctl+c and then restart node app.

Ashwani Panwar
  • 3,819
  • 3
  • 46
  • 66
2

Had the same issue. It was resolved as described above.

In my index.js

var port = 1338,
express = require('express'),
app = express().use(express.static(__dirname + '/')),
http = require('http').Server(app),
io = require('socket.io')(http);

app.get('/', function(req, res){
    res.sendFile(__dirname + '/index.html');
});

io.on('connection', function(socket){
    console.log('a user connected');
});

http.listen(port, function(){
    console.log("Node server listening on port " + port);
});

and in my index.html

<!doctype html>
<html>
    <head>
        <title>
            My page
        </title>
    </head>
    <body>
        <script src = "lib/socket.io.js"></script>
        <script src = "lib/three.js"></script>
        <script>
            var socket = io();
        </script>
    </body>
</html>

the three.js was just in there for path testing. This will set all child files to start at the root directory of your app. Also socket.io.js can be called automatically using <script src = "/socket.io/socket.io.js"> through some dark magic (since there is physically a node_modules and lib directory in between) .

2

The solution to "Cannot Get /" can usually be determined if you do an "ng build" in the command line. You will find most often that one of your "imports" does not have the correct path.

1
var connect = require('connect');
var serveStatic = require('serve-static');
var app = connect(); 
app.use(serveStatic('../angularjs'),  {default: 'angular.min.js'}); app.listen(3000); 
prashantsahni
  • 2,128
  • 19
  • 20
1

You may also want to try st, a node module for serving static files. Setup is trivial.

npm install connect

npm install st

And here's how my server-dev.js file looks like:

var connect = require('connect');
var http = require('http');
var st = require('st');

var app = connect()
    .use(st('app/dev'));

http.createServer(app).listen(8000);

or (with cache disabled):

var connect = require('connect');
var http = require('http');
var st = require('st');

var app = connect();

var mount = st({
  path: 'app/dev',
  cache: false
});

http.createServer(function (req, res) {
  if (mount(req, res)) return;
}).listen(8000);

app.use(mount);
Wojciech Fornal
  • 1,265
  • 11
  • 11
0

The easiest way to serve static files is to use "harp". It can be found here. You can serve up your files from the location you want via node is:

var harp = require("harp")
harp.server(projectPath [,args] [,callback])

Hope this helps.

Sesha Kiran
  • 199
  • 1
  • 4
0
  1. open cmd and go to the path of your project.(make sure that you are in "clientApp")
  2. then build your project with "ng build" command. if there is an error the console will give you the error. build error

now you know what your error is.

0

The Straight Forward Answer, include the code in your Node/Server index.js file

const path = require("path"); // include this in the file

router.get("/*", function(req, res) {
  res.sendFile(path.join(__dirname, "../public", "index.html"));
});

And if your are using navigate() in your reactApp use the above code at the end of the file.

Tyler2P
  • 2,324
  • 26
  • 22
  • 31
0

That was a silly mistake , I commented out the line that app.js uses for referencing routes.

This fix was to remove using express() directly.

enter image description here

And inside app.js you can define your customize routes

enter image description here

TAHA SULTAN TEMURI
  • 4,031
  • 2
  • 40
  • 66
-1

You typically want to render templates like this:

app.get('/', function(req, res){
  res.render('index.ejs');
});

However you can also deliver static content - to do so use:

app.use(express.static(__dirname + '/public'));

Now everything in the /public directory of your project will be delivered as static content at the root of your site e.g. if you place default.htm in the public folder if will be available by visiting /default.htm

Take a look through the express API and Connect Static middleware docs for more info.

Tarun Gupta
  • 6,305
  • 2
  • 42
  • 39