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.
  • Recent page and Recent Card update doesn't work for one account

    Unsolved
    3
    0 Votes
    3 Posts
    302 Views
    DownPWD
    @baris @baris said in Recent page and Recent Card update doesn't work for one account: So this started after you migrated your server? 2 or 3 days after @baris said in Recent page and Recent Card update doesn't work for one account: I would login with that user and make a new reply and see if that shows up in recent he use his account, he can answer tot topic but nothing in recent @baris said in Recent page and Recent Card update doesn't work for one account: Other things to check are blocked users, ignored categories Where can I check this? I put this user in the admin group and same things @baris said in Recent page and Recent Card update doesn't work for one account: If all else fails you need add some console.logs into src/controllers/recent.js to figure out why no topics are returned for that user. So there I am dropped
  • Docker deployment issue

    Unsolved
    1
    0 Votes
    1 Posts
    204 Views
    pedrogaudencioP
    I'm trying to setup a Digital Ocean app using the Dockerfile below - this is based on the original Dockerfile from the Docker container packages. I managed to get this working locally having little changes made to the original Dockerfile, since I'm using a custom template and this is pulled from a public git repo on the NodeBB package.json file, so no major changes from the normal setup. Here's the Dockerfile I'm using: FROM --platform=linux/amd64 node:lts as npm RUN mkdir -p /usr/src/build && \ chown -R node:node /usr/src/build WORKDIR /usr/src/build ARG NODE_ENV=production ENV NODE_ENV $NODE_ENV # nodebb-docker/ folder contains the repo https://github.com/NodeBB/NodeBB COPY --chown=node:node nodebb-docker/install/package.json /usr/src/build/package.json USER node RUN npm install --omit=dev FROM --platform=linux/amd64 node:lts RUN mkdir -p /usr/src/app && \ chown -R node:node /usr/src/app WORKDIR /usr/src/app ARG NODE_ENV ENV NODE_ENV $NODE_ENV COPY --chown=node:node --from=npm /usr/src/build /usr/src/app USER node RUN npm rebuild && \ npm cache clean --force COPY --chown=node:node nodebb-docker /usr/src/app ENV NODE_ENV=production \ daemon=false \ silent=false EXPOSE 4567 CMD test -n "${SETUP}" && ./nodebb setup || node ./nodebb build; node ./nodebb start Even though the build is running successfully (locally and in production) and I can run the container locally, I get this message on failed deployment: [2023-07-27 13:56:26] 2023-07-27T13:56:26.239Z [3] - info: Launching web installer on port 4567 [] Anyone has had this before? Thank you
  • Is it possible to run node in diffrent context root

    Unsolved
    5
    0 Votes
    5 Posts
    296 Views
    FrankMF
    Example for nginx https://docs.nodebb.org/configuring/proxies/nginx/
  • Looking for Dark Gaming Theme

    Moved
    6
    0 Votes
    6 Posts
    4k Views
    DownPWD
    [image: ren%C3%A9e-slater.gif]
  • Remove Google Fonts - is it possible?

    Solved
    9
    0 Votes
    9 Posts
    712 Views
    J
    @Andreas-Niemeyer said in Remove Google Fonts - is it possible?: • restart server ./nodebb restart in form folder
  • Finding code behind route /api/category/:cid

    Solved
    3
    0 Votes
    3 Posts
    315 Views
    nullpointerN
    @baris said in Finding code behind route /api/category/:cid: https://github.com/NodeBB/NodeBB/blob/master/src/controllers/category.js#L24 Thank you!
  • Install failed on Ubuntu 22.04

    Solved
    4
    0 Votes
    4 Posts
    381 Views
    julianJ
    I will say that we only test the $6 droplet (used to be 5).
  • Trying to get PrismJS to work with NodeBB

    Solved
    15
    0 Votes
    15 Posts
    875 Views
    phenomlabP
    @tankerkiller125 Very strange. I'm using the latest version of highlight.js with my own functions I provided, and everything works as intended. I had an issue before where basic text was being detected as bash for example, meaning every word almost was a different colour! Now I've disabled the Markdown version and implemented my own, it looks so much better. I'm using a theme switcher I wrote so that when themes change, it also pulls the highlight.js theme css file.
  • Add icons from FontAwesome to Icons list on Nodebb

    28
    0 Votes
    28 Posts
    5k Views
    oplik0O
    Okay, so I have fixes for both issues in a working state now Not sure it'll be done in time for 3.3 though https://github.com/NodeBB/NodeBB/pull/11820 If this is merged, other than fixing the issue with the icon selector, NodeBB will have support for FA pro enabled by installing the npm package (see instructions here: https://fontawesome.com/docs/web/setup/packages - this step requires setting up access to their package repo so it can't be done by NodeBB) and adding a configuration value (two if you want additional styles - FA seems to recommend not including all styles at once, so NodeBB will just use solid, regular and brands by default. Others require adding to configuration and rebuilding css)
  • This topic is deleted!

    Unsolved
    1
    0 Votes
    1 Posts
    6 Views
  • Slick Theme Not Compatible With v3?

    Solved
    11
    0 Votes
    11 Posts
    677 Views
    T
    @baris said in Slick Theme Not Compatible With v3?: https://community.nodebb.org/topic/17428/support-for-security-vulnerability-in-1-x-and-2-x Thank you! I'll bookmark the link.
  • Access to admin account

    Unsolved
    3
    0 Votes
    3 Posts
    1k Views
    oplik0O
    There are also two cli commands for this! ./nodebb user make admin <uid> for what you and Baris described - giving an existing user administrative privileges ./nodebb user reset <uid> to reset the password (<uid> will be 1 for default admin; the command will auto-generate a password and return it, you can also set your own with -p/--password option)
  • Skins - colors

    Moved
    3
    0 Votes
    3 Posts
    880 Views
    barisB
    When a skin is applied the body tag gets a class that identifies it so you can use custom CSS to only target that skin, for example if you use flatly then body has class="skin-flatly". In your css you can do. body.skin-flatly { // css that only applies to flatly skin }
  • Server restart, lost plugin

    Solved
    8
    0 Votes
    8 Posts
    461 Views
    C
    I found solution, I add my pluggin on the default puggin enabled.
  • SendGrid Contact List Sync Crashing NodeBB

    Solved
    15
    0 Votes
    15 Posts
    850 Views
    barisB
    @tankerkiller125 this is done in 3.1.5 https://github.com/julianlam/nodebb-plugin-emailer-sendgrid/commit/dd834cbf47a053644c3ebfb67e799a6fd9a929e9
  • nodebb shows cloudflare IP as user IP

    Unsolved
    10
    0 Votes
    10 Posts
    968 Views
    J
    @julian If you use nodebb's IP blacklist option (I do not), it does make a difference But in any case something needs to be defined, there are 2 options: Set a trusted proxy otherwise the forum will never know the real IP addresses, the cloudflare address will always appear, and IP addresses are a very useful thing to identify duplicate spam users, for example. 1.1 Optional - define a transform rule that will verify that the received address is real and not faked by a slightly advanced user Add the line I brought, and thus actually refer to CF-Connecting-IP I don't see any security advantage for trusted proxy (method 1) over the definition I brought.
  • Some incompatible plugins (GDPR/NTFY)

    Unsolved
    12
    1 Votes
    12 Posts
    790 Views
    phenomlabP
    @julian No rush - just good to know it's still on the map
  • current user data

    Unsolved
    5
    0 Votes
    5 Posts
    620 Views
    barisB
    In that case you can use the hook filter:middleware.renderAdminHeader this is fired when we are building the admin header which includes the plugins dropdown. Inside the hook you can look at the hookDatar.req.uid to get the uid of the user making the request. Below is a sample: myPlugin.filterMiddlewareRenderAdminHeader = async (hookData) => { console.log(hookData.req.uid, hookData.templateData.plugins); // TODO: filter plugins in `hookData.templateData.plugins` based on hookData.req.uid return hookData; }
  • Problem with searchbox in SEO

    Solved
    3
    0 Votes
    3 Posts
    310 Views
    B
    Thank you, @PitaJ! Now are no errors and google console sees the value!
  • filtering plugins

    Unsolved
    1
    0 Votes
    1 Posts
    147 Views
    A
    hey, i was wondering how i can filter the list of plugins that are being shown in the (ACP plugins section, and dropdown items), meaning i wanna show the emoji plugins in that dropdown menu as an example.