Skip to content

Technical Support

Need help with installing or configuring NodeBB? Look here.

4.7k Topics 26.1k 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.

    YouTube Setting up SendGrid mailer for NodeBB

  • NodeBB guides, how-to's and general tips and tricks

    82 Topics
    599 Posts
    barisB

    Quick start plugin has an example on how to add a new api route https://github.com/NodeBB/nodebb-plugin-quickstart/blob/master/library.js#L40-L76.

    The hooks that are fired client side are for client side code in plugins. If you want to pass data from the client to the server you have two options.

    Create an api route like in quick start plugin Create a new socket event listener on the server side and use socket.emit() client side. Example here
  • 25 Topics
    196 Posts
    phenomlabP

    @baris updated to 3.7.2 and now just waiting for the plugin to be updated.

  • NodeBB in inframe throws invalid csrf token

    Moved
    6
    0 Votes
    6 Posts
    562 Views
    E

    were you actually able to solve that? Running into a very related problem here (Nodebb running in an iframe, authenticated through session-sharing plugin. Users are logged in but any interaction results in an 403 / invalid csrf token... I'm running the board on a different domain than the embedding page.

  • 0 Votes
    5 Posts
    162 Views
    C

    @julian Thank you so much for getting back to me, I'll give that a shot!

  • Customize email titles

    Solved
    8
    0 Votes
    8 Posts
    267 Views
    S

    this was fixed in NodeBB v3.6.6
    🙂

  • 3.0.0 Upgrade Support Thread

    39
    1 Votes
    39 Posts
    2k Views
    barisB

    @Sebastián-Cisneros maybe you are missing this file in your composer-default plugin?

    It was added in nodebb 3.4.0 https://github.com/NodeBB/NodeBB/issues/11949

    So add that file into plugin.json of quill,

    "composer/post-queue.js": "../nodebb-plugin-composer-default/static/lib/composer/post-queue.js",
  • Error getaddrinfo EAI_AGAIN after running out of memory

    Solved
    8
    1 Votes
    8 Posts
    363 Views
    dave1904D

    Fortunately, the problem has been solved. I don't know yet if DigitalOcean has changed anything, but the last thing I did were these prompts for diagnostics:

    ping 8.8.8.8 ping google.com dig google.com dig google.com @1.1.1.1 cat /etc/resolv.conf systemd-resolve --status cat /etc/*release
  • 0 Votes
    2 Posts
    55 Views
    barisB

    Make sure you add jobsDisabled: true to all the machines except one so they don't run jobs.

    That error is usually fine since multiple machines will try to write out their analytics at the same time. The ones failing will retry and it will work on the second try.

  • 0 Votes
    7 Posts
    209 Views
    phenomlabP

    @enzo said in Displaying an image when the topic is shared on social media.:

    (btw, I'm using the S3 plugin, so all images are hosted there, not sure if this affects the behavior)

    This is a good point. Can the S3 bin be viewed publicly? If not, then this may restrict the ability to retrieve the image. On checking the URL from @baris, there is nothing wrong with this

    f38e1a48-de98-4b93-a512-a7c2bb4e138d-image.png

    The same applies to mine

    7415f46b-fa3e-4d71-b835-e5ad2781f888-image.png

    Are you using any browser plugins that could potentially alter the result?

  • Migrating existing forum from / to a subpath

    Solved
    2
    0 Votes
    2 Posts
    78 Views
    barisB

    That should be it, all the paths in template use {config.relative_path} as a prefix so things should work as normal

  • 1 Votes
    34 Posts
    4k Views
    B-738B

    @scottalanmiller

    pkg search mongodb
    mongodb-tools-100.9.4 Tools for MongoDB 4.4.x and up
    mongodb44-4.4.26 Distributed document-oriented "NoSQL" database (4.4.x Branch)
    mongodb50-5.0.23 Distributed document-oriented "NoSQL" database (5.0.x Branch)
    mongodb60-6.0.12 Distributed document-oriented "NoSQL" database (6.0.x Branch)
    mongodb70-7.0.4 Distributed document-oriented "NoSQL" data

  • This topic is deleted!

    Unsolved
    1
    0 Votes
    1 Posts
    5 Views
  • Login failing, "likely due to an expired session."

    Unsolved
    14
    0 Votes
    14 Posts
    420 Views
    M

    Are you able to make the appropriate changes in our docs?

    Yes, can do, I should have something ready to go soon-ish.

    [edit]
    https://github.com/NodeBB/docs/pull/89
    [/edit]

  • Transfer host to new server

    7
    0 Votes
    7 Posts
    631 Views
    catC

    @julian Yeah I was wondering why my default avatars, default headers, etc were broken. Other than that, zipping the nodebb folder on old server, then deploying on Heroku git should just work ☺

  • Modifying manifest.webmanifest

    Solved
    6
    0 Votes
    6 Posts
    123 Views
    barisB

    Oh if you don't have access then build a plugin that serves the file. You can use any url you want that way.

    app.get('/some/custom/url', function (req, res) { res.sendFile('path/to/hello.txt'); });
  • CSRF Error - NodeBB 3.x

    Solved
    4
    0 Votes
    4 Posts
    134 Views
    yasasY

    @DownPW Haha jinxx

  • Import plugin issues

    Unsolved
    2
    0 Votes
    2 Posts
    67 Views
    PitaJP

    Was this not clear?

    Link Preview Image Plugin Nodebb Plugin-Import: error Loading

    I recommend you read the instructions: https://github.com/akhoury/nodebb-plugin-import THIS PLUGIN ONLY SUPPORTS: NodeBB v1.12.1 but you can upgrade after t...

    favicon

    NodeBB Community (community.nodebb.org)

    The import plugin does not support latest NodeBB

  • Plugin Nodebb Plugin-Import: error Loading

    Unsolved
    4
    0 Votes
    4 Posts
    360 Views
    barisB

    Once you import on nodebb 1.12.1, you can then upgrade all the way to 3.x with ./nodebb upgrade

  • Guest priviledges for Posts

    Unsolved
    2
    0 Votes
    2 Posts
    58 Views
    julianJ

    Can you show us what you mean? The guests row should not be greyed out

  • CORS problems using NodeBB API

    Unsolved
    3
    0 Votes
    3 Posts
    95 Views
    Antonio Peña BatistaA

    @PitaJ said in CORS problems using NodeBB API:

    Certain browsers treat localhost differently with CORS stuff. I recommend you try using 127.0.0.1 or some other IP address instead.

    but for my app or for the forum?

  • Performing bulk actions on "flags" causes nginx 503 error

    Solved
    4
    0 Votes
    4 Posts
    115 Views
    julianJ

    This likely cropped up because flag actions now use the v3 API instead of socket.io, so it could be it overloaded the backend, which started sending 503s.

  • No Admin account after first setup

    Moved
    3
    0 Votes
    3 Posts
    115 Views
    fishcoderF

    yeah, thank you. I've solved it with deleting the database. In the logs I found the error of skipping the creation of the admin user, because it already exists.