Technical Support

@qwerty yes, after running ./nodebb stop, NodeBB should not be running.

What did you try? Does it work when running with ./nodebb dev?

Probably on nodebb tracker.

Hey there!

I have a nodebb instance i've been customizing through theming and plugins.

I recently came across an issue that has prevented me from running ./nodebb start

Clustering enabled: Spinning up 4 process(es).

2019-07-22T06:23:35.139Z [4567/15633] - info: Initializing NodeBB v1.12.2 https://kratomwatchdog.com 2019-07-22T06:23:35.431Z [4567/15633] - error: NodeBB could not connect to your Mongo database. Mongo returned the following errorconnect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"],"stack":"MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017\n at Socket.err (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:287:16)\n at Object.onceWrapper (events.js:315:30)\n at emitOne (events.js:116:13)\n at Socket.emit (events.js:211:7)\n at emitErrorNT (internal/streams/destroy.js:66:8)\n at _combinedTickCallback (internal/process/next_tick.js:139:11)\n at process._tickCallback (internal/process/next_tick.js:181:9)"} 2019-07-22T06:23:35.443Z [4567/15633] - error: connect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"]} 2019-07-22T06:23:35.446Z [4568/15638] - error: NodeBB could not connect to your Mongo database. Mongo returned the following errorconnect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"],"stack":"MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017\n at Socket.err (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:287:16)\n at Object.onceWrapper (events.js:315:30)\n at emitOne (events.js:116:13)\n at Socket.emit (events.js:211:7)\n at emitErrorNT (internal/streams/destroy.js:66:8)\n at _combinedTickCallback (internal/process/next_tick.js:139:11)\n at process._tickCallback (internal/process/next_tick.js:181:9)"} 2019-07-22T06:23:35.448Z [4568/15638] - error: connect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"]} 2019-07-22T06:23:35.449Z [4569/15640] - error: NodeBB could not connect to your Mongo database. Mongo returned the following errorconnect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"],"stack":"MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017\n at Socket.err (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:287:16)\n at Object.onceWrapper (events.js:315:30)\n at emitOne (events.js:116:13)\n at Socket.emit (events.js:211:7)\n at emitErrorNT (internal/streams/destroy.js:66:8)\n at _combinedTickCallback (internal/process/next_tick.js:139:11)\n at process._tickCallback (internal/process/next_tick.js:181:9)"} [cluster] Child Process (15633) has exited (code: 0, signal: null) 2019-07-22T06:23:35.454Z [4569/15640] - error: connect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"]} [cluster] Child Process (15638) has exited (code: 0, signal: null) [cluster] Child Process (15640) has exited (code: 0, signal: null) 2019-07-22T06:23:35.462Z [4570/15645] - error: NodeBB could not connect to your Mongo database. Mongo returned the following errorconnect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"],"stack":"MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017\n at Socket.err (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:287:16)\n at Object.onceWrapper (events.js:315:30)\n at emitOne (events.js:116:13)\n at Socket.emit (events.js:211:7)\n at emitErrorNT (internal/streams/destroy.js:66:8)\n at _combinedTickCallback (internal/process/next_tick.js:139:11)\n at process._tickCallback (internal/process/next_tick.js:181:9)"} 2019-07-22T06:23:35.464Z [4570/15645] - error: connect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"]} [cluster] Child Process (15645) has exited (code: 0, signal: null)

I am able to run nodebb in dev mode, and have had to run it in a screens session to keep the forum online until i'm able to resolve the issue.

@PitaJ Actually never mind, I just changed the color of the entire bar instead of trying to figure what the text color was!
You can delete this thread.

Although I still think you should add in the next version to ability to change all colors using color selectors in the control panel, as it does not make sense to have some but not others.

@qwerty Are you freakin' serious or punking us? If basics such as this are beyond you then you have absolutely no business deploying server based anything on the Internet. Much less a juicy target for crackers like a forum. Seriously irresponsible. Your name/reputation will be crap once your site is cracked and your users forever hate you. If this sounds harsh, it is because it is meant to. Moderator was being polite.

That said:

ESC : wq! Return/Enter

Good luck!

Hello, I'm hosting my NodeBB on Digital Ocean and I want to move everything to an other database. We use MongoDB and we have a few problems. We don't know the MongoDB admin password/username.

Do you know a way to do this or is there a plugin that makes this easier to do?
Any help/advice is welcome and are there things we should do and don't do?

Hello folks,
I want to have hackernews-like interface for topic screen. Is there a way to disable all the categories system completely?
When I disable all categories users can t open new topic anymore.
When I left only one topic and put everything in users still have to select category while open new topics.
Any idea?

Solved, thank you

Thanks for the reply

I added it the config, I had over 300 objects in the session database

It's already fixed on latest master.

Can you connect to the database from the mongo cli client? If not, them you're using the wrong credentials.

Additionally, I recommend following the official NodeBB docs: https://docs.nodebb.org/installing/os/ubuntu/

Third party tutorials can be outdated or incorrect.

Yes it should be no problem. It used to be that this wasn't possible but now it should just work.

You can set up a 404 response from the x url inside your reverse proxy. Pretty sure there's a way to report this kind of abuse to Google.

@PitaJ
Ahh I see, thank you

@JJSagan Thanks for your answer. I tried it but it was making things bad on reloading the page or loading other pages. I will not use datatables (and it will be easier for me on future updates).

@julian Yes absolutely. I'd be very happy to have a script that searched for imgur profile pictures and removes them as I'm not experienced with NodeJS at all.

@julian said in HUh.. where is delete category/sub-category?:

The way we use "purge" is for clearing out an item from the db, so in our eyes, the nomenclature is correct.

The function is specific to removing the category from the database. We are careful to not call it deleting because deleting implies that it can be "undeleted", whereas you cannot unpurge something.

You say potatoes I say tomatoes! 😉

Is that change made to my plugin? If so, can you open a pull request to get it in? 😄

@PitaJ said in welcome page error:

Please ensure the URL value in config.json matches exactly the URL at which you access your site.

thanks, that solved the issue.