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.
  • 0 Votes
    7 Posts
    1k Views
    J
    @PitaJ said in Image uploading: "Something went wrong while parsing server response": Try running npm rebuild Alright, image upload works now! I'll keep an eye for the other crashes and let you know in case!
  • How do I get rid of this warning message on the console?

    Solved
    4
    0 Votes
    4 Posts
    644 Views
    J
    @jtsimoes said in How do I get rid of this warning message on the console?: Damn it, I knew about that command and I didn't remember to use it... I totally know that feeling.
  • is PHP the correct way ?

    2
    0 Votes
    2 Posts
    388 Views
    yariplusY
    @flexxall said in is PHP the correct way ?: You can still use PHP by installing in on your webserver (nginx/apache), that may be the best option if you have a large amount of PHP code already.
  • Redactor Error Handler / PostgreSQL Error on 8000+ characters message

    9
    0 Votes
    9 Posts
    1k Views
    J
    @kfirba try updating socket.io-adapter-postgres (replace index.js with https://github.com/BenLubar/socket.io-adapter-postgres/blob/master/index.js). It should resolve the issue you have encountered in earlier releases. I reported this in github if you wish follow: https://github.com/NodeBB/NodeBB/issues/7215
  • Dark theme.

    Moved
    7
    0 Votes
    7 Posts
    2k Views
    julianJ
    @rfc2822 hm, well we don't normalize anything. Bootstrap does, however, although I can't imagine why they'd be using a version of normalize that is older than Jan 2016!
  • Header image for a fresh install

    7
    0 Votes
    7 Posts
    918 Views
    F
    @baris said in Header image for a fresh install: /assets/uploads/<filename>.jpg Excelent. Thank you
  • Delaying sockets start

    6
    0 Votes
    6 Posts
    675 Views
    G
    It looks like is a configuration problem. When I load the page, there is this network error: socket.io.js:8 WebSocket connection to 'wss://example.com/socket.io/?EIO=3&transport=websocket&sid=zV8kYkx-87ULGIjGAAAF' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR On Chrome's inspector window it says it was canceled. But then it works normal. So all I need is to bypass the first error... or even better, fix it.
  • nodebb on aws is throwing sockets error

    10
    0 Votes
    10 Posts
    2k Views
    S
    We got ours fixed, ignore me Nothing to do with AWS, someone had changed our nGinx config and not told me.
  • Changes to nodebb-plugin-rss in light of YQL shutdown

    9
    1 Votes
    9 Posts
    1k Views
    The WormsT
    @JJSagan Too Thanks
  • 0 Votes
    8 Posts
    987 Views
    PitaJP
    I don't think that commit has been released yet, which would explain why you'd still have the error. You could have just cherry-picked that commit you linked, but what you did works as well. It might just end up conflicting with future upgrades.
  • 0 Votes
    5 Posts
    645 Views
    barisB
    https://github.com/NodeBB/NodeBB/issues/7236
  • Badges showing only randomized

    4
    0 Votes
    4 Posts
    569 Views
    PitaJP
    You can't change the groups you're a part of, but you can choose which badges show up with your avatar. Go to https://community.nodebb.org/me/edit and you'll see a "Group Title" select box. That's where you configure which titles show up below your avatar.
  • Hosting NodeBB on bare metal EC2

    5
    0 Votes
    5 Posts
    709 Views
    R
    Thank you.
  • Old Pic Showing Instead of New Pic

    1
    0 Votes
    1 Posts
    211 Views
    SaeedS
    Hi, there is an issue of new pic not showing when uploaded. Instead the old pic from cache is showing. The new pic only shows once I close and reopen the browser. This can easily be fixed if someone can save the last modified datetime of the pic in the db and put that datetime in the pic query string like this: <img id="user-current-picture" class="avatar avatar-xl avatar-rounded" src="/assets/uploads/profile/1-profileavatar.jpeg?mod=2018-12-30 22:59:00" data-original-title="" title=""> thanks, Saeed
  • How to config Categories Sidebar like nodebb communitiy style?

    6
    0 Votes
    6 Posts
    869 Views
    JsonHiveJ
    @JJSagan thanks
  • Email configuration (mailgun) issues

    6
    0 Votes
    6 Posts
    740 Views
    G
    @PitaJ and who else may encounter this issue, here is how I solved it. The root problem was the image format used for "Site Logo" in general/settings. I've uploaded a png file and the information was not saved in the database, althoughthe fields remained filled across the sessions. Once I've changed the site logo with a jpg file, the emails were properly formatted too.
  • Using any sso plugin results in 404

    9
    0 Votes
    9 Posts
    1k Views
    GeferonG
    @gorgiselkov I believe that one might not be working because it's a skeleton plugin, and not an actual SSO auth (as stated on github page), unless you've configured it yourself but, it doesn't seem like it.
  • Is there a way to set initial category-watch-state for a category?

    5
    0 Votes
    5 Posts
    596 Views
    J
    Thanks @baris it might be useful to add to the acp at the category editing page...
  • nodebb-plugin-rss: getaddrinfo enotfound

    4
    0 Votes
    4 Posts
    1k Views
    J
    @The-Worms and anyone else following this topic: the RSS plugin may be fixed. See this topic for howto: https://community.nodebb.org/topic/13540/changes-to-nodebb-plugin-rss-in-light-of-yql-shutdown
  • 0 Votes
    17 Posts
    2k Views
    S
    I run into this problem as well, and I fixed it by simply npm install --build-from-source sharp, FYI.