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.
  • Online users widget & ACP

    Solved
    6
    0 Votes
    6 Posts
    306 Views
    barisB
    You can change it to 5 minutes in the ACP using the online cutoff setting.
  • Admin Invites and Registration Queue

    Unsolved
    1
    0 Votes
    1 Posts
    84 Views
    mutahar aliM
    Is there a way to enable registration queue but make it so that user's registering with admin invites are able to register bypassing registration queue and admin approval? Since it would only make sense since the admins are the ones who invited the user. Many thanks!
  • nodebb-plugin-composer-quill: WYSIWYG alternative to redactor

    89
    1 Votes
    89 Posts
    18k Views
    nhl.plN
    Quill 2.0 has been released. https://slab.com/blog/announcing-quill-2-0/
  • Email Services Novice and issues sending to Gmail

    Unsolved
    8
    0 Votes
    8 Posts
    414 Views
    PitaJP
    Word that from would bee messed up. Can you try undoing your change and console.loging those values to see what they end up being?
  • 0 Votes
    10 Posts
    489 Views
    Nuran AkimbekN
    @baris Yes, I test develop branch and it's really worked now. But community still loaded slow and shows from time to time 503 error
  • Posting in Activity pub

    Unsolved
    15
    0 Votes
    15 Posts
    703 Views
    julianJ
    @crazycells yes, just like normal topics.
  • Registration email links pointing to 127.0.0.1

    6
    0 Votes
    6 Posts
    2k Views
    julianJ
    @Renan-Birlem-Deves make sure you're not using some other way to send a config in, otherwise config.json may not be read (or its values overridden).
  • Harmony Theme - Help with Chat & File Structure

    Solved
    6
    0 Votes
    6 Posts
    250 Views
    T
    @baris thanks!
  • Docker compose

    Unsolved
    5
    0 Votes
    5 Posts
    1k Views
    F
    @schwach I have two installations dependent on this image and I am stuck as there are no updates for a while, i wouldn't advise using it. I'm still looking for an efficient way to setup a docker-compose file that can be used to update with new release (both nodebb and mongodb). I wish updating nodebb was much simpler, i have an old forum started from 1.7, it has been such a pain keeping it up to date because of the need of dependencies.
  • Fresh Install With No Email Being Sent Out.

    Solved
    7
    0 Votes
    7 Posts
    277 Views
    2TonWaffle2
    Found the issue!! You must use the main account API key and secret and not a subaccount key for everything to work. Getting emails now through both the Cloudron side and NodeBB
  • Guest

    Moved
    6
    0 Votes
    6 Posts
    1k Views
    julianJ
    @tchesley85 when creating a category you can always clone the settings (that includes privileges) of an existing category.
  • Upgrade from v1.19.x to v2.0.x failed

    Unsolved
    7
    1 Votes
    7 Posts
    320 Views
    W
    Yes, the errors are still there with v3.x. I even deleted the build/ and node_modules/ directories because I thought there might be outdated files in there. But that didn't help. However, since the MongoDB schema upgrades were successful during the ./nodebb upgrade runs, I was able to complete the upgrade by doing a fresh git install and copying back the old config.json before running the setup routine. I then manually restored all the static files in public/uploads via rsync.
  • "tag list" to choose from?

    Solved
    10
    2 Votes
    10 Posts
    1k Views
    barisB
    Not sure how that will be implemented since Tag1 and tag1 would end up being two different tags. Lowercasing solves that problem.
  • dark mode on mobile?

    Solved
    6
    0 Votes
    6 Posts
    279 Views
    phenomlabP
    @crazycells Agree - you can have as many or as few as you'd like though.
  • /user/<xyz>/2factor Access Denied?

    Unsolved
    5
    0 Votes
    5 Posts
    187 Views
    ww9riversW
    @julian - Done! Thank you for the quick responses.
  • Performance insights of NodeBB

    Unsolved
    10
    0 Votes
    10 Posts
    459 Views
    barisB
    Yeah I think having a folder under public/uploads/profile for each user would make deleting easier. We can get rid of the glob and delete that folder on user deletion. But we would have to write an upgrade script to move all files and update the path in the user object since they are stored as "/assets/uploads/profile/1-profileavatar-1709738685611.jpeg"
  • Failed to look up latest available version of NodeBB

    Solved
    5
    0 Votes
    5 Posts
    178 Views
    Sampo2910S
    @PitaJ v16.13.0 obviosuly very old Ooops..installed latest version and now it is all ok.. Thanks for the gentle reminder.
  • Themeing... Started with Quickstart got some bad results

    Moved
    15
    0 Votes
    15 Posts
    704 Views
    Chad AugurC
    @baris TY. Despite having been a JS developer for more than 10years I had never published my own npm package. Now I have. TY.
  • This topic is deleted!

    Unsolved
    2
    0 Votes
    2 Posts
    5 Views
  • Invalid CSRF token when authenticating via third-party app

    Unsolved
    7
    1 Votes
    7 Posts
    1k Views
    S
    @hnipps said in Invalid CSRF token when authenticating via third-party app: I'm trying to use NodeBB as a headless forum (i.e. just a REST API with a separate front end) but keep getting an "invalid csrf token" error when I try to authenticate. I've confirmed I can authenticate via the NodeBB UI on the same instance. I've also tried getting the NodeBB config and using the csrf token from there in my requests but it still does not work. My frontend is a NextJS app that rewrites all /api/:path* requests to http://<MY-NODE-BB-INSTANCE>/api/:path*. It also rewrites the auth paths. I can see the requests reach NodeBB but always get "invalid csrf token". I've verified that I can successfully call GET endpoints from my app, e.g. I can get the user list from /api/users. This is a 2 yr old thread, but @hnipps have you gone any further with the React/NextJS frontend with a headless nodebb? If you have made any progress I would love to contribute on the frontend build. It is daunting to start as a new project but if any foundations were laid I would love to jump in and build upon it.