Quick answer, try starting your node server with DEBUG=express:* node server.js and watch what Express tells you is happening.
Try develop/test with script tags in package.json along following lines:
"start": "NODE_ENV=production DEBUG=*:error node server.js",
"dev": "DEBUG=nodemon:* nodemon server.js",
and a nodemon config: nodemon.json that has all tracing on:
# cat nodemon.json
{
"restartable": "rs",
"ignore": [
"*.md",
"notes"
],
"verbose": true,
"execMap": {
"js": "node"
},
"env": {
"DEBUG": "*",
"NODE_DEBUG": "",
"NODE_ENV": "development"
},
"ext": "js, json, html"
}
NODE_DEBUG is likely too low level and you would only turn on one at a time NODE_DEBUG=cluster,net,http,fs,tls,module,timers
Probably not best way to do it, but create a logger per module(*.js file) (change myApp to match module) and you can do stuff like DEBUG=*:error,myRoutes:*,express:* ... whatever you feel like.
appLog = { // logger
/* eslint-disable sort-keys */
err: debug("myApp:error"), // 0 -- a problem occured
warn: debug("myApp:warning"), // 1 -- this could be a problem
info: debug("myApp:info"), // 2 -- normal event
debug: debug("myApp:debug") // 3 -- use for debugging/development
/* eslint-enable sort-keys */
}
Not sure how well this would scale out and or behave in production... but you need some basic logging functionality. Never built real production apps.
A couple questions.
1.) Are you seeing your custom 404 page defined in your app or the default one from nginx?
2.) Are you seeing a 404 for all pages including
/or just for certain ones?