Technical Support

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]: > [email protected] 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! [email protected] 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 [email protected] 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

@Dim said:

".modal-backdrop {
z-index: 0;
} "

.modal-backdrop { z-index: auto; }

Would probably be preferable, since auto makes it behave like no z-index property has been specified (as is the case in the default Bootstrap theme used in lavender and persona) which makes the element inherit the z-index of its parent, whereas z-index: 0 forces the z-index to be, well, 0.

Thanks @nhl-pl I was using Ajenti V and the only reason I switched away from using it was do to the lack of documentation. I have used the traditional Apache based web server setups for many years and the Nginx server was all foreign to me so it was a challenge any time I wanted to add something or even troubleshooting issues.

It reminds me of when I was evaluating blog/cms alternatives for a Coldfusion based website back when Wordpress was less than a year old. I looked at Wordpress and Drupal and decided to go with Wordpress because at the time Drupal was too complicated and didn't have very good documentation. I switched to Drupal just before Drupal 7 came out and was amazed at the progress it had made and how much simpler it was from what I remembered. It is possible however, that it seemed easier because my knowledge base was a lot bigger.

That was a long winded way of saying I may revisit Ajenti eventually once I have learned more about the Nginx and Node.js way of server management.

Thanks ... Pops

I'm writing a bot that GETs a specific post from a category on my forum, and this category is only accessable by admins. Only problem is, GETting that post always returns a 401 Not Authorized response, because it's not open to users.

I've tried using auth=(username, password), Authorization: Bearer, even sending it in the GET params, but they all just return 401.

Any way of doing this?

yep, just update theme

solved

in package.json is old version for 6.1.x

or how to combine difference acc in one?
simple auth + sso steam + sso vk + ... = in one profile

thx, solved

perfect, thx

just installed dev version 0.7, in console log that buildin plugins can cause err -)
installed sso steam in 0.7, plugin unstable, sometime working, sometime not working
is there compabality list for plugins? or compabality tests for plugins?

thx solved -)

Might be a separate issue then, unfortunately I'm not familiar with those plugins.

@yariplus Strangely, I tried to run this command but redis-server does not turn off.

ok . thanks a lot

This is the manual how to update/upgrade from v0.5.0 to v0.6.1 git checkout c9228f14837fcf2903923ebca3d90a0d1517a713 (I don't now why v0.5.1 doesn't work in cli and csrf token error) ./nodebb upgrade git checkout d341428ca1b88d56f7c7fe37d3e5e87d83bb0698 (v0.5.2 doesn`t work in cli too) ./nodebb upgrade git checkout cce076fc83e6a29c7d385ee757cce4b40c63daf2 (v0.5.3 work in cli, but I am not interesting in experiments) ./nodebb upgrade git checkout 1943f8fdfa573b40e8b0c5e23e68142a71b2cf93 (v0.5.4) ./nodebb upgrade git checkout d6c17d5cae66f2ab0d4174e1b6bdda24856eacbe (v0.5.5) ./nodebb upgrade git checkout e7ecd0f1eb81c54f33f51958b64aa937613bc99d (v0.5.6) ./nodebb upgrade git checkout 6748013c6534ed672184145ee7b5120eb07e7b47 (v0.5.7) ./nodebb upgrade git checkout accee7d05ba3f791627d439ac1c73cf5f858eebe (v0.6.0) ./nodebb upgrade git checkout 4686ae992318eeaaff1945868ee4cc094dcda17d (v0.6.1) ./nodebb upgrade git checkout c2656bf0b69ec05b1cbc123ef06ec0b14657cc8b (stable) ./nodebb upgrade npm up clear cache and cookies

Is anybody knowing the better solution? Please, give me to know.

@meetdilip said:

@a_5mith

A few doubts,

Copy files from folder to which we have installed ?

The github repo, so you'd have a folder called nodebb with all of the nodebb files in, then a folder called nodebb2, which also contains all the nodebb files.

Share the command to change port no. please..

./nodebb setup, but change :4567 to something else.

How to assign new folder / installation to database 2 ?

You answered this in your next post, change the 0 in database to 1.

Should we run ./nodebb setup after copying the files ( installed ? ) to a new folder ?

You will need to yes in order to set it up, you'll also need to run npm install to get the dependencies installed in that location.

Just to put this issue to bed. I trashed the old forum. Installed new. New git clone... new database. Problem solved.

Rich

@baris said:

The error message is telling you that it can't access/save the file. Make sure the user you are running the commands has the proper permissions.

I wondered that too, I was using a user I specifically created for this task in order to not use the root user as I thought it was not a good practice to do. Especially since the instructions indicate a sudo user. Usually I can figure out permission issues, but for some reason I have not been able to solve this one. The installation does get further when using the root user, so there is definitely a permission issue.

The error I get now is related to the connection of the Redis database. I get a connection refused error when using the IP of the server.

The abort error shows the IP address and default port number so I have no idea how to connect the database.

Here's the latest console information ...

[email protected] node_modules/connect-redis └── [email protected] ([email protected]) 25/4 19:08 [21628] - info: Populating database with default configs, if not already set... 25/4 19:08 [21628] - error: Error: Redis connection to myserverIP:6379 failed - connect ECONNREFUSED at RedisClient.flush_and_error (/mydomainpath/nodebb/node_modules/redis/index.js:142:13) at RedisClient.on_error (/mydomainpath/nodebb/node_modules/redis/index.js:180:10) at Socket.<anonymous> (/mydomainpath/nodebb/node_modules/redis/index.js:95:14) at Socket.EventEmitter.emit (events.js:95:17) at net.js:441:14 at process._tickCallback (node.js:415:13) 25/4 19:08 [21628] - warn: NodeBB Setup Aborted. Redis connection to myserverIP:6379 failed - connect ECONNREFUSED

Thanks ... Pops

@hek said:

It's not interesting to know which groups people have joined

I know what you're saying here. In theory a User could join multiple groups without too much thought. ( a mouse click )

Admin assigned groups 'some' should have the option of being automatically displayed, and maybe only admin assigned roles. This integration would give better handling for what @psychobunny is mentioning, with mobile/ipad integration.

I guess you could say, user groups and admin groups (roles?) are very different, and perhaps should not be displayed as user 'groups' under the groups page. Separated perhaps ?

@baris I have 470mo usage and 17mo free. The main sources are NodeJS (31%) and Redis (10%). My server has been up during 180 days might be worth considering a reboot no ? (if some process are stuck since there's 82 spleeping task and only two running.)
I'm looking forward 0.7.0, thanks for the great job and the quick answers.