Welp, I solved it.
Turns out I had the wrong directory specified in nginx for static assets. It was pointing to a different install of nodebb. For some reason that caused issues with socket.io (and only with safari/opera for some reason).
Now, here's the weird thing. I only recently started using nginx to serve the assets. Recently as in like this morning. Before that I simply had a proxy pass setup and let nodebb serve the assets. I'm not sure what was causing the 400/502 errors then but I'm just glad their solved now.
Hi guys!
I have previous 0.5.0-2 version of forum on Heroku. It works fine. When I updated NodeBB to 0.6.1 version it crashed with error. Any ideas?
2015-04-30T06:31:05.151177+00:00 heroku[web.1]: State changed from crashed to starting
2015-04-30T06:31:12.946261+00:00 heroku[web.1]: Starting process with command npm start
2015-04-30T06:31:16.159469+00:00 app[web.1]: Detected 512 MB available memory, 512 MB limit per process (WEB_MEMORY)
2015-04-30T06:31:16.159494+00:00 app[web.1]: Recommending WEB_CONCURRENCY=1
2015-04-30T06:31:16.817884+00:00 app[web.1]:
2015-04-30T06:31:16.817890+00:00 app[web.1]: > nodebb@0.6.1 start /app
2015-04-30T06:31:16.817892+00:00 app[web.1]: > ./nodebb start
2015-04-30T06:31:16.817893+00:00 app[web.1]:
2015-04-30T06:31:16.854535+00:00 app[web.1]: sh: 1: ./nodebb: Permission denied
2015-04-30T06:31:16.873738+00:00 app[web.1]: npm ERR! Linux 3.13.0-49-generic
2015-04-30T06:31:16.878037+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2015-04-30T06:31:16.878041+00:00 app[web.1]: npm ERR! nodebb@0.6.1 start: ./nodebb start
2015-04-30T06:31:16.878043+00:00 app[web.1]: npm ERR! Exit status 126
2015-04-30T06:31:16.878044+00:00 app[web.1]: npm ERR!
2015-04-30T06:31:16.878046+00:00 app[web.1]: npm ERR! Failed at the nodebb@0.6.1 start script './nodebb start'.
2015-04-30T06:31:16.878048+00:00 app[web.1]: npm ERR! This is most likely a problem with the nodebb package,
2015-04-30T06:31:16.878049+00:00 app[web.1]: npm ERR! not with npm itself.
2015-04-30T06:31:16.878050+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2015-04-30T06:31:16.878052+00:00 app[web.1]: npm ERR! ./nodebb start
2015-04-30T06:31:16.878054+00:00 app[web.1]: npm ERR! You can get their info via:
2015-04-30T06:31:16.878693+00:00 app[web.1]: npm ERR! npm owner ls nodebb
2015-04-30T06:31:16.878696+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2015-04-30T06:31:16.889120+00:00 app[web.1]:
2015-04-30T06:31:16.899848+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2015-04-30T06:31:16.866363+00:00 app[web.1]:
2015-04-30T06:31:16.874577+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2015-04-30T06:31:16.875101+00:00 app[web.1]: npm ERR! node v0.12.2
2015-04-30T06:31:16.876089+00:00 app[web.1]: npm ERR! npm v2.7.4
2015-04-30T06:31:16.897668+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2015-04-30T06:31:17.925842+00:00 heroku[web.1]: Process exited with status 1
2015-04-30T06:31:17.938969+00:00 heroku[web.1]: State changed from starting to crashed
Not an nginx guru so please bear with me here.
For simplicity sake let's assume site lives at forums.example.com rather than a example.com/forums subfolder.
Unless specified otherwise, nginx root dir is /usr/share/nginx/html
Nodebb nginx configuration docs utilize this when describing setting up a custom error page.
Nginx is being used exclusively as reverse proxy and not serving any additional sites. I think I read somewhere that under such configuration an explicit default server docroot should not be specified? But even in such cases I think the hard coded default /usr/share/nginx/html still serves up 50x.html error page.
In absence of a custom error page, nodebb uses nodebb/public/503.html?
Nginx has been configured for scaling.
Nginx Pitfalls and Common Mistakes documentation suggest putting doc root inside a location block is bad practice even though it will work.
Soo... now my question... taking all of above into consideration.. what is proper/correct best practice configuration for a "scaled" nginx nodebb deployment? I know what "could" work. I am curious what "should" be recommended best practice.
(Yeah, I know I already posted this in a different thread but it was a mistake at the time not to have started a new thread because this is pretty specific w.r.t. best practices configuration rather than "why isn't my stuff isn't working" question. Apologies for that.)
