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.
  • [Solved] Socket.io 400/500 Errors

    3
    1 Votes
    3 Posts
    4k Views
    hekH
    Done... https://github.com/NodeBB/NodeBB/issues/5393
  • Error when trying to start NodeBB

    6
    0 Votes
    6 Posts
    4k Views
    PitaJP
    @SparaxVenator try running npm install
  • Prova de pregunta

    Unsolved
    1
    0 Votes
    1 Posts
    539 Views
    Octavi RodriguezO
    Prova de pregunta
  • Start fails with UnhandledPromiseRejectionWarning on plain 1.3.0 and 1.4.0

    12
    0 Votes
    12 Posts
    7k Views
    N
    I just tried out 1.4.2 on my docker image. The result: No Google fonts error and it starts up. So, whatever caused the problem is gone in 1.4.2. Very nice.
  • Looking for descriptions and complete list of hooks

    5
    0 Votes
    5 Posts
    2k Views
    T
    @baris Thank you, it explains a lot.
  • Upgraded NodeBB To V1.4.2 Errors

    3
    0 Votes
    3 Posts
    1k Views
    C
    @pichalite Thank you for the response. That was most peculiar, but I reset the config.json to be how it was and it stopped having this error. Besides I still think it's best to check data.config, before extracting data.config.loggedin anyway.
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    53 Views
  • Error on plugin update while executing nodebb with non root user

    8
    0 Votes
    8 Posts
    3k Views
    E
    restarted a few times again nodebb working now thanks
  • Issue with Admin Panel since upgrade to 1.4.2

    43
    0 Votes
    43 Posts
    21k Views
    M
    @PitaJ said in Issue with Admin Panel since upgrade to 1.4.2: @Michael-Pfaff well you need to reload nginx That worked! Sorry I'm such a noob, @PitaJ. Very much appreciate your assistance.
  • Cannot post or reply to posts in Nodebb mobile version.

    14
    0 Votes
    14 Posts
    4k Views
    I
    @julian I've disabled plugins and now it's working ok. Thanks for your help!
  • Weird Stuff in Admin Panel After Upgrading

    4
    0 Votes
    4 Posts
    2k Views
    M
    Awesome! Thank you @PitaJ!
  • Rotating Banner Ad? Can I create one?

    4
    0 Votes
    4 Posts
    2k Views
    PitaJP
    adblock probably
  • Can't post, javascript not loading

    7
    0 Votes
    7 Posts
    3k Views
    M
    @julian I found this after re-reading the NodeBB NGINX configuration docs nginx must be on version 1.4.x to properly support websockets. Debian/Ubuntu uses 1.2, although it will work there will be a reduction in functionality. Previously, in the same doc: NGINX version v1.3.13 or greater I'm not sure if that is just a sign of an outdated doc, or if there is actually some type of incompatibility (which apparently doesn't surface everywhere). All I know is that by reverting to 1.4.x, all functionality was restored.
  • [SOLVED] nodebb upgrade script freezing

    2
    0 Votes
    2 Posts
    1k Views
    L
    During the upgrade the following url is fetched: https://fonts.googleapis.com/css?family=Roboto:300,400,500,700 I was getting a 501 http error.. It was caused by the proxy, and solved by bypassing it. The upgrade completed successfully.
  • Questions

    9
    1 Votes
    9 Posts
    3k Views
    A
    @Aoki are you still having issues with installing it?
  • PDF attachments and Photo adding?

    4
    1 Votes
    4 Posts
    2k Views
    educatorE
    @jarey The amount of good replies I get in this nodebb is great. Thank you. So, I am going with nodebb. Having a positive energy that people will help us in the long run
  • Show post edit timestamp

    5
    0 Votes
    5 Posts
    2k Views
    J
    @pichalite said in Show post edit timestamp: @JaredBusch you can create a plugin to listen to the filter for getting category posts and modify the data as required. I have no desire (well not much of one) to become a dev for something like this. I taught myself how to write VB in 1995 and VB .Net back in the early 2000's and have a number of applications to my credit, but it is not my desired path. But, if there is nothing out there for this already, I guess it is something I can look into.
  • Loading nodebb in my site through iframe

    4
    0 Votes
    4 Posts
    3k Views
    P
    @Jonathan-O'Donnell232 why don't you modify the theme to add the branding to the header?
  • Meta tags do not get new value on navigation across topics

    2
    0 Votes
    2 Posts
    1k Views
    PitaJP
    @Jenni-D'Silva if you share the topic it's a permalink. The meta tags should be correct in the share. Meta tags only matter for SEO and that sort of thing, which use raw loads anyways, so I don't see the issue.
  • 0 Votes
    2 Posts
    2k Views
    Pramvir RatheeP
    Found the solution, importing too much topics in a single category hangs the nodebb, import some data than move it to some temporary category. Thasn import remaining data, meanwhile delete mongodb import Garbaze in using these mongo commands db.objects.update({},{$unset: {_imported_tid:1}},{multi: true}); db.objects.update({},{$unset: {_imported_uid:1}},{multi: true}); db.objects.update({},{$unset: {_imported_cid:1}},{multi: true}); db.objects.update({},{$unset: {_imported_slug:1}},{multi: true}); db.objects.update({},{$unset: {_imported_locked:1}},{multi: true}); db.objects.update({},{$unset: {_imported_path:1}},{multi: true}); db.objects.update({},{$unset: {_imported_title:1}},{multi: true}); db.objects.update({},{$unset: {_imported_content:1}},{multi: true}); db.objects.update({},{$unset: {_imported_guest:1}},{multi: true}); db.objects.update({},{$unset: {_imported_ip:1}},{multi: true}); db.objects.update({},{$unset: {_imported_user_slug:1}},{multi: true}); db.objects.update({},{$unset: {_imported_user_path:1}},{multi: true}); db.objects.update({},{$unset: {_imported_category_path:1}},{multi: true}); db.objects.update({},{$unset: {_imported_category_slug:1}},{multi: true}); But keep in mind this will also delete the history of import will result in duplicate categories get imported or the posts, to prevent this keep writing post ids and category ids which you imported and delete them from the old database.