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.
  • show new post after submit no longer works

    5
    0 Votes
    5 Posts
    612 Views
    S
    thanks all.. admin disabled a plugin which was trying to send a notification to another system (discord) as part of posting message to bb topic
  • NodeBB Bootstrap error

    2
    0 Votes
    2 Posts
    488 Views
    barisB
    https://community.nodebb.org/post/77781
  • Conditional elements in theme based on tags

    Moved
    5
    0 Votes
    5 Posts
    553 Views
    barisB
    You can find some info about the topic/post structures here https://github.com/NodeBB/NodeBB/wiki/Database-Structure. For plugin development info you can take a look at https://docs.nodebb.org/development/plugins/ You can look into the hook filter:topic.build which already has the tags of the topic in the tags field. Then you can add the additional data in that hook for the template to use. Sample hook: myPlugin.filterTopicBuild = async function (hookData) { if (hookData.templateData.tags.includes('marvel') { hookData.templateData.posts[0].content += '<br/>this user likes marvel'; } } This is just a simple example feel free to modiyy & improve.
  • Subscribing to a category (after the plugin was activated)

    2
    0 Votes
    2 Posts
    181 Views
    Patrick MP
    Forgive me if this is a very obvious question. I just can't find the solution for the life of me. I've installed and activated the following plugin: nodebb-plugin-category-notifications (https://github.com/NodeBB/nodebb-plugin-category-notifications#readme) I then rebuilt & restarted the forum. I was able to get into the admin screen. According to the description, my users should now have the ability to subscribe to categories. How do they do so? I don't see a button or option anywhere in proximity to the categories. Thanks Patrick
  • Install on Debian error: [build] admin control panel styles build failed

    1
    0 Votes
    1 Posts
    306 Views
    Tj GiengerT
    The entire error below. I've been searching for some clues, but coming up empty handed and hoping someone can help. This is a fresh install on a debian 10 server. 2020-04-17T16:33:02.636Z [26376] - error: [build] admin control panel styles build failed 2020-04-17T16:33:02.639Z [26376] - error: resource 'https://fonts.googleapis.com/css?family=Roboto:300,400,500,700' gave this Error: Error: socket hang up {"type":"File","filename":"/var/www/nodebb/nodebb/public/less/admin/paper/bootswatch.less","index":87,"line":5,"column":0,"callLine":null,"extract":["","@import url(\"https://fonts.googleapis.com/css?family=Roboto:300,400,500,700\");",""]} ==================================================================================================================================== 2020-04-17T16:33:02.647Z [26376] - error: resource 'https://fonts.googleapis.com/css?family=Roboto:300,400,500,700' gave this Error: Error: socket hang up {"type":"File","filename":"/var/www/nodebb/nodebb/public/less/admin/paper/bootswatch.less","index":87,"line":5,"column":0,"callLine":null,"extract":["","@import url(\"https://fonts.googleapis.com/css?family=Roboto:300,400,500,700\");",""]} (node:26376) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:26376) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
  • Error while restarting the forum after several plugin update

    22
    0 Votes
    22 Posts
    2k Views
    F
    @gotwf I truly miss zfs
  • SMTP parameters reset

    3
    0 Votes
    3 Posts
    686 Views
    gotwfG
    @qxpd Possible and maybe even likely if your uninstall was incomplete. What platform are you on? How are you sending mail? Are you running your own smtp relay? If so, what are you using? Exim? Postfix? Or using third party SMTP relay service? Cuz those types of small details really do make a big difference. As to the error message above, port 587 is the "well known" Submission port for SMTP. 127.0.0.1 is the local host's "loop back" interface which your machine favors for moving bits about whilst talking to itself. In this case: NodeBB is trying, unsuccessfully, to relay mail to the world via an SMTP server running on your local host. Is there one? If you do not know, you should not be running your own mail server as there be lots of security related dragons lurking thereabouts for even seasoned sysadmins. Hence, unless you want to shoulder the responsibility of running your own SMTP server I'd suggest using a third party relay. Now, one thing that IS relatively simple to set up is a Null Client Relay, that ONLY accepts mail from the trusted local host and then relays that mail via SMTP protocol to your upstream internet facing smtp relay. Faster than the nodejs built in. And it is nice to have a "mail spool" in event outbound mail gets backed up for some reason. But that built-in works too. And a non issue with smaller sites. At least last time I looked at it. Hope this helps some.
  • Consider add to documentation: Node version

    7
    0 Votes
    7 Posts
    998 Views
    gotwfG
    Sharp seems to have a bit of history for being somewhat of a thorn in the side.... https://community.nodebb.org/topic/12940/1-10-1-1-10-2-libvips-whole-x-server-dependency/4?_=1586907702860&lang=en-US It was confusing to me as well when I first tried taking NodeBB for a test drive. Great support here though for getting such glitches sorted.
  • Fresh installation seems broken

    14
    0 Votes
    14 Posts
    4k Views
    J4ckk3J
    @baris Sorry, school got in the way of me responding. I'll try downgrading jQuery. Thank's for the help, I was really confused.
  • Custom Nav bar above NodeBB nav bar

    4
    1 Votes
    4 Posts
    2k Views
    crazycellsC
    @oplik0 thanks a lot for the great explanation. I will update the topic later...
  • Just setup my first bbs with NodeBB

    6
    0 Votes
    6 Posts
    925 Views
    crazycellsC
    @xinbenlv I think you can change this setting from Admin Control Panel... (or completely remove restriction)
  • Fresh installation seemingly broken

    Locked
    2
    0 Votes
    2 Posts
    374 Views
    barisB
    https://community.nodebb.org/topic/14672/fresh-installation-seems-broken/6
  • Where is menu?

    3
    0 Votes
    3 Posts
    364 Views
    oplik0O
    Could you try rebuilding NodeBB? Perhaps something happend with just this step and redoing it will fix the forum. If this doesn't work, then reinstallation will probably be required (or at least the easiest way).
  • Force group badge display for users

    1
    0 Votes
    1 Posts
    246 Views
    Damien JayD
    Hey there, I'm using Persona theme and would like to force the display of badges (effectively removing the "no group" option from users), is this possible? Thanks,
  • Overriding template in Persona theme

    11
    0 Votes
    11 Posts
    1k Views
    PitaJP
    @Damien-Jay nice job man. glad you figured it out
  • Changing Terms of Use

    2
    0 Votes
    2 Posts
    500 Views
    gotwfG
    Good question. I had similar bridge to cross a while back w.r.t. some minor changes. I ended up posting locked sticky under "Announcements" with the updated terms. One of the terms might be "Use of this site constitutes implicit acceptance of the terms above"? Not getting you all the way there but maybe a little cya in the meantime?
  • Gif as Profile Images

    7
    0 Votes
    7 Posts
    1k Views
    F
    @scottalanmiller Do Gifs work with cover photos for you? Do you know how that can work?
  • Daily Digest bug

    12
    0 Votes
    12 Posts
    1k Views
    magnusvhendinM
    Great, then there shouldn't be any issues when the digests are sent for real.
  • Cyrillic url transliteration

    1
    0 Votes
    1 Posts
    219 Views
    Vladislav IvanovV
    Hi. Sorry for my bad english. I installed Nodebb, I really liked the forum. I think Nodebb is the best forum in the world. But 1 big drawback upset me. I did not find a solution how to enable transliteration cyrillic urls. It is very important in terms of seo. For example: Now i have links as /topic/1/заработок-в-интернете I need /topic/1/zarabotok-v-internete
  • Redirect after login?

    10
    0 Votes
    10 Posts
    1k Views
    glassdimlyG
    Here's what I ended up doing. Feels reeealy hacky. in footer.tpl window.addEventListener('DOMContentLoaded', function () { $(window).on('action:ajaxify.contentLoaded', function(data) { // attach to all login/reg buttons except for the login and register buttons on the login page. $("a[href$='/login'], a[href$='/register']").not('#login').not('#login__no-acct').each(function(i, el){ $(el).off('click').on('click', function(){ window.setCookie('login:referrer', window.location.href, 10); }); }); }); }); </script> in profile.tpl <script> var referrer = window.getCookie('login:referrer'); if (referrer && window.getCookie('login:shouldRedirect')) { window.setCookie('login:shouldRedirect', '', 0) window.setCookie('login:referrer', '', 0) window.location.href = referrer; } </script> in registerComplete.tpl <script> window.setCookie('login:shouldRedirect', 'true', 10); </script> ...and attaching setCookie/getCookie on window in header. Probably could do this all with client-side hooks now that I understand them though.