Skip to content

Technical Support

Need help with installing or configuring NodeBB? Look here.

4.8k Topics 26.7k 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.
  • Need help with Mongodb

    5
    0 Votes
    5 Posts
    2k Views
    L
    i just hate those breaking changes that node introduce ... dafuq..... hope you guys dont use 3.6+ features in the near future
  • How to upgrade nodebb from 1.70 to 1.72

    3
    0 Votes
    3 Posts
    1k Views
    julianJ
    After git checkout, you might also need to git pull to get the latest code
  • Installing plugins via commandline in Docker

    Unsolved
    2
    0 Votes
    2 Posts
    1k Views
    PitaJP
    ./nodebb build
  • can not start nodebb after upgrade

    8
    0 Votes
    8 Posts
    2k Views
    P
    @teh_g after running npm i following error comes on console npm WARN deprecated [email protected]: connect 2.x series is deprecated npm WARN deprecated [email protected]: Use uuid module instead npm WARN deprecated [email protected]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130 npm ERR! Linux 3.10.0-693.11.1.el7.x86_64 npm ERR! argv "/usr/bin/node" "/bin/npm" "i" npm ERR! node v6.12.0 npm ERR! npm v3.10.10 npm ERR! code ETARGET npm ERR! notarget No compatible version found: [email protected] npm ERR! notarget Valid install targets: npm ERR! notarget 0.3.6, 0.3.5, 0.3.4, 0.3.3, 0.3.1, 0.3.0, 0.2.0 npm ERR! notarget npm ERR! notarget This is most likely not a problem with npm itself. npm ERR! notarget In most cases you or one of your dependencies are requesting npm ERR! notarget a package version that doesn't exist. npm ERR! Please include the following file with any support request: npm ERR! /home/pawan/Discussion forum/nodebb/npm-debug.log @julien
  • nodebb-plugin-session-sharing broken in 1.7.2

    9
    0 Votes
    9 Posts
    2k Views
    J
    @baris tried right after you posted it yesterday and it worked, thank you! @julian it was definitely staying at 3.2.1 for me, both in the admin panel and through SSH. Were the commands I've used correct?
  • What wrong with my NodeBB? [HELP]

    Moved
    2
    0 Votes
    2 Posts
    900 Views
    PitaJP
    Di you use sudo for any of the commands?
  • Need some help, upgrade error.

    4
    0 Votes
    4 Posts
    1k Views
    J
    @baris problem solved, many thanks!
  • CSS Script to change the background of text/threads

    3
    0 Votes
    3 Posts
    1k Views
    Hawks CastH
    Thank you. I've trying to isolate a few things now: [image: 8gSWJ12.png] I can't find a way to colorize this white strip. [image: HdbkQOJ.png] The font color for the "chat, quote, and reply" so it's easier to see. [image: DOFlaNx.png] And then the widgets (header/side bar) and button bar (I don't know what it's called). I've tried looking up the classes but they haven't provided a result that fixes it. Again, all help is greatly appreciated.
  • [Solved] Problem with reputation : How can I set it manually to 0 ?

    4
    0 Votes
    4 Posts
    1k Views
    frju365F
    PS for other users : What I did is : 1° / Go in you admin panel, in Gestion > Users, and write/see the UID of the user(s) you want to set the reputation to 0 2° / Go in a terminal, and write : # mongod > use <yourdatabase> > db.objects.update({_key: "user:<uid>"}, {$set: {"reputation": 0}}); > db.objects.update({_key: "users:reputation", value: "<uid>"}, {$set: {"score": 0}}); That's it !
  • Hell of installation

    4
    0 Votes
    4 Posts
    1k Views
    J
    @rami7250 said in Hell of installation: I own VPS Apache WHM server based on centos 6 Don't use anything this old to start with.
  • v1.6.0 permission problems after upgrade/update

    73
    0 Votes
    73 Posts
    16k Views
    M
    @pitaj said in v1.6.0 permission problems after upgrade/update: I don't know. Make a backup and try whatever you want. Sounds good. Thanks for all of your help and pointing me in the right direction! I'll mess with it and see what I can figure out.
  • No package.json in the root folder anymore

    3
    0 Votes
    3 Posts
    2k Views
    JenklerJ
    Ok, Thanks
  • This topic is deleted!

    2
    0 Votes
    2 Posts
    12 Views
  • Are the Ubuntu setup docs current

    2
    0 Votes
    2 Posts
    1k Views
    julianJ
    Can you share your mongod.conf? It sounds like a config option there isn't quite right.
  • How to add reputation number to the global header?

    Moved
    4
    0 Votes
    4 Posts
    2k Views
    J
    WOW thank you so much!!
  • Slight issue with skins on v1.7.x

    Moved
    5
    0 Votes
    5 Posts
    2k Views
    MrCakeSlayerM
    Do you have an estimated time this will be out? For the default nodebb theme at the least as we don't currently use a custom theme. As a side question, I know you can manipulate web pages with JS/JQuery but I dont use them, Would we be able to use JS/JQuery to modify the dropdown list in the user settings and remove specific dropdown items from the skins dropdown? This would perhaps work as a temporary solution. Edit: Ignore the above,I found the JS to hide them. Note For Others: You can use code below to hide specific skins from the dropdown menu $("#bootswatchSkin option[value='cosmo']").remove();
  • Category notifications / watching categories etc

    2
    1 Votes
    2 Posts
    1k Views
    PitaJP
    There is existing discussion about this here: https://github.com/NodeBB/NodeBB/issues/5172 You can voice your support for whatever option you see as best there.
  • package.json after update to 1.7.1

    12
    0 Votes
    12 Posts
    3k Views
    mudmanc4M
    Done! git status On branch v1.7.x Your branch is up-to-date with 'origin/v1.7.x'. Still out there (which I'm not sure I care) since it's not an issue, is to how this happened. At any rate, thanks for the help, it's much appreciated you took the time!
  • This topic is deleted!

    Locked
    17
    0 Votes
    17 Posts
    2k Views
  • This topic is deleted!

    8
    0 Votes
    8 Posts
    19 Views