Skip to content

Technical Support

Need help with installing or configuring NodeBB? Look here.

4.8k Topics 26.5k Posts

Subcategories


  • User documentation for NodeBB

    44 Topics
    44 Posts
    Jay MoonahJ
    One of the first important things to do after setting up NodeBB is to set up an emailer plugin. While NodeBB does include a local emailer, if your forum is particularly active we recommend using an third-party emailer such as SendGrid which provides better deliverability for sites that send a high volume of email. Setting up SendGrid in NodeBB is very easy. Open the administrative dashboard using the 'gear' icon on your forum. Open the Extend > Plugins menu, and select the Find Plugins tab. Use the search on the right. Type 'SendGrid' and the plugin should appear -- select Install when you see it. From Installed tab on the Plugins menu, search again for 'SendGrid' and select Activate. Activating the plugin will require a restart of your forum. To restart, select the Dashboard menu and press the Restart button to the right. After NodeBB restarts, the SendGrid plugin will be active. After you restart, there should be a item called Emailer (SendGrid) under the Plugins menu -- if you don't see this right away, try refreshing your browser. Sign up to SendGrid Go to the SendGrid website, open the pricing page and scroll to the bottom. Click on the link and create your free account. Once you've confirmed your SendGrid account via email, you should be able to login to the SendGrid website. On the left side of your SendGrid dashboard, open Settings and click on API Keys. Click the button in the top right to create a new key. Make sure that the key has Full Access for Send Mail and Alerts.  When you are done, the new key to your clipboard. Now, return to the SendGrid menu on your NodeBB admin panel. Paste the API key into the field, and save your changes. Now go back to the Dashboard to restart your forum one more time. SendGrid should now be working for your forum. [image: youtubelogo.png] Setting up SendGrid mailer for NodeBB
  • NodeBB guides, how-to's and general tips and tricks

    83 Topics
    601 Posts
    Z
    not sure the plugin worked for firefox. saw a-z in the sort icon. when i used it, i expected the topics in the category would be sorted a-z. they werent
  • 25 Topics
    201 Posts
    eeeeeE
    I think you answered my point, by agreeing there are issues. I didn't even attempt to deploy nodebb, I had problems with much smaller projects! Nextjs routing was going through a change of design at the time, so perhaps that is less confusing now, but there were multiple other headaches. I would get build errors and issues with package management.
  • Error when upgrade to install plugin

    2
    0 Votes
    2 Posts
    756 Views
    barisB
    This should be fixed on latest master, related issue https://github.com/NodeBB/NodeBB/issues/7860
  • 'Popular' date filter

    2
    0 Votes
    2 Posts
    401 Views
    D
    I re-wrote the category controller (src > controllers > category.js) to handle passing ?term=x query through and only getting the relevant topics.
  • dynamic router in navigation menu

    3
    0 Votes
    3 Posts
    459 Views
    Z
    @PitaJ it worked. Thank you
  • Database queries - topics

    3
    0 Votes
    3 Posts
    531 Views
    D
    Thanks @baris, the latter approach works so I'll go with that
  • nodebb suddently stopped working

    5
    0 Votes
    5 Posts
    784 Views
    Z
    pulling.js: //# sourceMappingURL=pulling-drawer.js.map pulling.js.map: {"version":3,"sources":["node_modules/pulling/build/pulling-drawer.js"]
  • A bad HTTP response code (404) was received when fetching the script.

    2
    0 Votes
    2 Posts
    1k Views
    Z
    It seems like this fixed it: https://github.com/vuejs-templates/webpack/issues/446#issuecomment-278503745
  • Error Logging In

    2
    0 Votes
    2 Posts
    472 Views
    Madeline JonesM
    @PaigeLynn Navigate to your nodebb folder in the console/command prompt, then type ./nodebb restart
  • Error: Failed to look up latest version of NodeBB

    2
    0 Votes
    2 Posts
    413 Views
    barisB
    This is happening since the code to get the version was moved to the server side, https://github.com/NodeBB/NodeBB/issues/6540
  • how to remove register/complete?

    3
    0 Votes
    3 Posts
    431 Views
    G
    @baris Thanks, I'm just very blind))))))
  • Show all groups a user belongs to?

    1
    0 Votes
    1 Posts
    203 Views
    D
    Is there a way to show all the group badges a user belongs to, without them having to select them all from the edit profile page?
  • Registeration API

    1
    0 Votes
    1 Posts
    253 Views
    T
    Is there any way that we can use nodebb register as an external API. If yes the please let me know
  • Nodebb Service always restart

    1
    0 Votes
    1 Posts
    309 Views
    巫易澄
    Earlier I installed a search plugin on nodebb, and then I restarted the nodebb service, it shows that the nodebb service has been restarting. I searched for it. I can disable the plugin via ./nodebb reset -p, but my nodebb is installed. In the container, what can I do to knock this order?
  • MongoDB Create User Erro

    11
    0 Votes
    11 Posts
    2k Views
    P
    Now this has happened on both AWS AND DIGITAL OCEAN so I be followed these steps step by step so either I'm stupid and can't follow directions or something's missing that I'm not able to connect with
  • "Restart Required" warning does not go away

    10
    0 Votes
    10 Posts
    2k Views
    crazycellsC
    I did... here it is: https://github.com/NodeBB/nodebb-plugin-poll/issues/105
  • Error Conecting to Database

    1
    0 Votes
    1 Posts
    257 Views
    P
    I got Mongo finally and now Im having this issues error: NodeBB could not connect to your Mongo database. Mongo returned the following error MongoError: Authentication failed. at /home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:581:63 at authenticateStragglers (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:504:16) at Connection.messageHandler (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:540:5) at emitMessageHandler (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:310:10) at Socket.<anonymous> (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:453:17) at Socket.emit (events.js:198:13) at addChunk (_stream_readable.js:288:12) at readableAddChunk (_stream_readable.js:269:11) at Socket.Readable.push (_stream_readable.js:224:10) at TCP.onStreamRead [as _originalOnread] (internal/stream_base_commons.js:94:17) 2019-08-12T16:15:24.766Z [4280] - warn: NodeBB Setup Aborted. MongoError: Authentication failed. at /home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:581:63 at authenticateStragglers (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:504:16) at Connection.messageHandler (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:540:5) at emitMessageHandler (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:310:10) at Socket.<anonymous> (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:453:17) at Socket.emit (events.js:198:13) at addChunk (_stream_readable.js:288:12) at readableAddChunk (_stream_readable.js:269:11) at Socket.Readable.push (_stream_readable.js:224:10) at TCP.onStreamRead [as _originalOnread] (internal/stream_base_commons.js:94:17)
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    10 Views
  • Issue with caching

    6
    0 Votes
    6 Posts
    744 Views
    D
    Thank you both, this resolved the issue
  • Unable To Update NodeBB Schema

    1
    0 Votes
    1 Posts
    277 Views
    LazL
    Hey friends. So. I reinstalled my forums after I accidentally deleted some stuff I wasn't meant to, and now stuff is properly borked. I completely cleaned NodeBB and MongoDB from the system. I'm running off the master branch, and I'm fairly certain that the db search plugin is to blame, as the issue only occurs after installing that. I'm working off the master branch and upon restarting after activating that plugin, I'm met with the following error: 2019-08-11T09:44:59.042Z [4567/8372] - error: Your NodeBB schema is out-of-date. Please run the following command to bring your dataset up to spec: 2019-08-11T09:44:59.042Z [4567/8372] - error: ./nodebb upgrade [cluster] Child Process (8372) has exited (code: 0, signal: null) That's fine, but when I go to run the upgrade, I get the following: [2018/11/26] Changing dbsearch mongodb search schema to use _id... 2019-08-11T09:46:07.205Z [4567/8392] - error: ns not found {"ok":0,"errmsg":"ns not found","code":26,"codeName":"NamespaceNotFound","name":"MongoError"} 2019-08-11T09:46:07.207Z [4567/8392] - error: ns not found {"ok":0,"errmsg":"ns not found","code":26,"codeName":"NamespaceNotFound","name":"MongoError"} and that leaves me pretty stuck. I've disabled the plugin for now, but I'd really like to know what's going on here.
  • Login to Widget

    2
    0 Votes
    2 Posts
    406 Views
    G
    @TestNew-dsdsds who can help ?
  • 0 Votes
    2 Posts
    1k Views
    PitaJP
    https://community.nodebb.org/topic/13388/faq-websockets-not-working-due-to-misconfigured-origins