Seems it was npm's failing to install dependencies correctly?
@alexsir Yep, I guess that's the port NodeBB is configured to listen on my default. At the end of that guide, there's a link to another guide that explains how to configure nginx as a proxy - which would allow you to either configure a domain to point to your NodeBB process, and/or omit the port from the URL.
NodeBB upgrades became worse since 0.7
-
Every time I do an upgrade it does not go well. There is always some kind of error even though I am following the upgrade process from the docs.
I just tried upgrading from v0.7.1 to v0.7.2. The first thing I got was an npm error when I ran the ./nodebb upgrade script. Tried running it again, it worked this time don't know why and how. Tried starting NodeBB with ./nodebb start. It wouldn't start with an uglify.js module error. I install uglify.js, now I get a 503 error.
-
@pichalite Sorry to hear that
Can you paste the error here? To my knowledge, NodeBB does not send 503 errors... -
@julian It was actually 500 not 503.
- error: Error: Failed to lookup view "500" in views directory "/home/pichalite/nodebb/public/templates" at EventEmitter.render (/home/pichalite/nodebb/node_modules/express/lib/application.js:579:17) at ServerResponse.render (/home/pichalite/nodebb/node_modules/express/lib/response.js:961:7) at ServerResponse.res.render (/home/pichalite/nodebb/src/middleware/middleware.js:337:10) at /home/pichalite/nodebb/src/routes/index.js:223:9 at /home/pichalite/nodebb/src/middleware/middleware.js:192:12 at /home/pichalite/nodebb/node_modules/async/lib/async.js:589:17 at done (/home/pichalite/nodebb/node_modules/async/lib/async.js:126:15) at /home/pichalite/nodebb/node_modules/async/lib/async.js:32:16 at /home/pichalite/nodebb/node_modules/async/lib/async.js:586:21 at EventEmitter.render (/home/pichalite/nodebb/node_modules/express/lib/application.js:581:14) Error: Failed to lookup view "500" in views directory "/home/pichalite/nodebb/public/templates"I reset the theme to vanilla too after I got this error to eliminate the possibility of custom theme error.
-
@pichalite the composer has a bug. it does not scroll when I am typing a long message, the page scrolls instead. The composer starts scrolling after it reaches the end of the page.
-
@pichalite Did you update your theme to specify the proper base theme? https://community.nodebb.org/topic/6098/on-changing-the-default-theme-to-persona
-
-
-
@julian deleted the complete NodeBB folder and set it up. got it working.
Don't have too many plugins installed. In addition to the default ones I have sso plugins for Facebook, google and twitter and the rss plugin that's it.
-
i tried upgrading using nodebb upgrade, it still shows 0.7.1, its not a git repo, so i cant do a fetch and checkout
-
@chrismccoy
./nodebb upgradedoes not download new code for you. You need to do that yourself
Please check out the "Upgrading NodeBB" page in the documentation
-
Even I was having trouble installing the update using the method listed in the docs.
I did a little searching and found @julian had mentioned a step of installing dependencies after the fetch, etc and prior to running./nodebb upgradesomewhere in this forum as a reply to a previous update issue.He had asekd to run
npm ito install dependencies and that is what is working for me. I used it to update from v0.7.0.0 to v0.7.1.0 and also to v0.7.2.0. -
-
@pichalite said:
Every time I do an upgrade it does not go well. There is always some kind of error even though I am following the upgrade process from the docs.
Same here. Haven't had one work yet, actually. Not since 0.3 I think.
