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.
  • Minifer.js not found; nodebb.min.js not created

    3
    0 Votes
    3 Posts
    2k Views
    danielflippanceD
    Found the answer - The script starting NodeBB must be in the nodebb directory otherwise the minifier will fail as above. Changed my Upstart script as follows: cd $LIVE_DIR exec node app.js >> /var/log/blahblahblah/nodebb.log
  • docs.nodebb.org where is the link?

    3
    1 Votes
    3 Posts
    1k Views
    frissdiegurkeF
    +1 for a direct link. I guess the most direct at the moment is via github (pricing -> github -> Documentation & Installation Instructions) o_O . docs.nodebb.org <-- now it's in mine too
  • Authentication, Mongo and Upstart

    11
    0 Votes
    11 Posts
    6k Views
    tqwhiteT
    @qgp9 I can't say exactly how I installed Mongo. When I google, "ubuntu install mongo", my web browser tells me that this page https://docs.mongodb.org/v3.0/tutorial/install-mongodb-on-ubuntu/ has been visited and it looks familiar. I think it's what I used to guide me. And, no, I did not compile. And no, I am not using docker. A detail, since you seem to be interested, is that the install does not leave my system with a functioning "service mongod restart" command. At present, Upstart runs Mongo. "stop mongod" does not work.
  • 0 Votes
    2 Posts
    3k Views
    V
    managed to fix it by putting the ip address in the facebook url.. not the same one that is in config.json
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    2 Views
  • Browser Console Always Empty

    1
    0 Votes
    1 Posts
    752 Views
    Jason NealJ
    I first noticed this when I ran into issues with jquery not executing on the ACP, but now with a separate installation, on a totally different server, I'm seeing it again. I can see clearly that jQuery or javascript isn't executing, but the browser console remains totally blank. In the previous case, another user here was able to display the contents from his browser console, but mine stayed blank. This time around, the lavender theme's masonry script isn't executing, but there's no output from my browser console. Thoughts? NOTE I am running this directly from an IP address without a FQDN. Could this be part of the issue? UPDATE I started up nodebb in dev mode and watched the terminal, but I'm not getting any errors or warning after the site loads. I'm totally stumped why masonry.js isn't loading. It's not even showing up in the console's resources, but there was no error thrown either in the client or the terminal.
  • Clean install cannot GET /

    10
    0 Votes
    10 Posts
    3k Views
    ?
    @zero how about your webserver config or are you running NodeBB on Port 80?
  • Offline Installation

    2
    0 Votes
    2 Posts
    902 Views
    ?
    @charles no. Unless you try this: https://addyosmani.com/blog/using-npm-offline/
  • Upgrading from v0.9.x to v1.x.x

    2
    0 Votes
    2 Posts
    1k Views
    C
    @SimonQ try the commands here https://community.nodebb.org/topic/8285/easy-nodebb-upgrade-process
  • Background Intermittent - Custom CSS

    8
    0 Votes
    8 Posts
    3k Views
    L
    Interesting. I'll have to keep this one in my back pocket for the future.
  • install camo for nodebb-plugin-iframely

    6
    0 Votes
    6 Posts
    4k Views
    L
    @j.b.-o. sorry for the late reply! @yariplus and me just released nodebb-plugin-camo which should make this whole process a lot more easier and automatic. You can find the explanation post here.
  • Facebook MetaTag problem

    3
    0 Votes
    3 Posts
    1k Views
    P
    according to their scraped info they have the correct og:title but don't display it, might be because of the arabic(?) characters here is a debug of this site and it works fine https://developers.facebook.com/tools/debug/og/object/?q=https%3A%2F%2Fcommunity.nodebb.org edit: you might have to set opengraph locale with <meta property="og:locale" content="ar_AR" /> you can just add this on your admin page under appearance > custom html & css > custom header
  • v1.0.1: Upgrade fails during 'adding message to chat room'

    1
    0 Votes
    1 Posts
    788 Views
    R
    I had this problem going from v0.9.4 -> v1.0.0 and now still have it going from v0.9.4 -> v1.0.1 but now I have additional information about it. See here for my original post. The tl;dr is $ ./nodebb upgrade 1. Bringing base dependencies up to date... OK 2. Checking installed plugins for updates... OK 3. Updating NodeBB data store schema... 18/3 15:15 [1511] - info: Beginning database schema update 18/3 15:15 [1511] - info: [2015/09/30] Converting default Gravatar image to default User Avatar skipped 18/3 15:15 [1511] - info: [2015/11/06] Gravatar removal skipped 18/3 15:15 [1511] - info: [2015/12/15] Upgrading chats 18/3 15:15 [1511] - info: adding message 1 to new roomID 1 18/3 15:15 [1511] - info: adding message 2 to existing roomID 2 18/3 15:15 [1511] - info: adding message 3 to existing roomID 2 18/3 15:15 [1511] - info: adding message 4 to new roomID 2 18/3 15:15 [1511] - info: adding message 5 to new roomID 3 18/3 15:15 [1511] - error: [upgrade] Errors were encountered while updating the NodeBB schema: ERR value is not a valid float OK NodeBB Upgrade Complete! Before deleting the "message:x" keys from my redis database (to attempt the upgrade again) I noticed that message:5 was different than the other message keys. Specifically it seems the upgrader is choking on message:5 "Bad" Message 5 key: [image: LOaR026.png] "Good" message key: [image: u4UOzyC.png] So it appears that the NodeBB upgrader does not like messages that do not have a touid or fromuid or possibly timestamp information. Should this be reported as a bug?
  • v1.0.1: Plugin checker did not run on upgrade

    1
    0 Votes
    1 Posts
    645 Views
    R
    I've run the v1.0.1 updater against my DEV and it did not see that I have 8 plugins with updates available. I ran the ./nodebb upgrade command which should have triggered the update mechanism according to: [image: NZF0iym.png] But now with v1.0.1 running I see these updates available: [image: pElivfY.png]
  • what will happen with new install

    3
    0 Votes
    3 Posts
    963 Views
    C
    @pichalite had problems and will have to test again and report back.
  • Forum Stats Being Shown While in Maintenance Mode

    3
    0 Votes
    3 Posts
    985 Views
    R
    To comment further after much mulling it over, the Extend > Widgets should have a specific entry for the maintenance mode page.
  • Authorization and registration on the one page

    3
    0 Votes
    3 Posts
    2k Views
    X
    @julian said: You'll want to investigate how the request is made, and mimic it with the new fields Yes.
  • Showing Subcategories on the Mainpage with 0.9.3

    9
    0 Votes
    9 Posts
    3k Views
    Danny McWilliamsD
    Thanks @pichalite I'm currently on v1.0.0. It'd be nice to have, but I think I should just get my forum online again before looking at cosmetic alterations!
  • 1 Votes
    4 Posts
    2k Views
    julianJ
    Fixed in the package manager, your plugin lists should be working again.
  • PHP page in /public/ ?

    3
    0 Votes
    3 Posts
    1k Views
    H
    Ok, thank you for your fast response