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.
  • Problem with registration

    6
    0 Votes
    6 Posts
    743 Views
    M
    I was fix problem.
  • Referrer doesn't redirect?

    8
    0 Votes
    8 Posts
    789 Views
    magnusvhendinM
    @baris Awesome, thanks a lot!
  • Trying to pinpoint a problem potentially related to caching

    2
    0 Votes
    2 Posts
    338 Views
    julianJ
    Can you share more about your setup? Is it a single heroku instance running off a single database backend? All-in-one server? This could be an issue if you are using multiple NodeBB instances...
  • Category Privileges PUT and DELETE APIs Results Not Reflected

    3
    0 Votes
    3 Posts
    486 Views
    Ethan YuE
    Hey Baris, In my Node.js code with superagent, the privilege should've been groups:posts:downvote rather than group:posts:downvote. I got privileges manipulation to work now!
  • SSO google- no icon @login page?

    Unsolved
    6
    1 Votes
    6 Posts
    785 Views
    巫易澄
    I found that google's sso button is in the edit in the profile, but after clicking it shows not found.Currently I am using ssl reverse proxy, do I need to configure redirects? [image: CeDdz5X.png] [image: 7o8MH1M.png]
  • change http to https but cannot login

    11
    0 Votes
    11 Posts
    935 Views
    Peter  DongP
    The problem already solve thankyou for all the help. It works when u rewrite the the http rq to https.
  • 0 Votes
    1 Posts
    291 Views
    I want to show only the widgets that have a link to the homepage. What should I do?
  • Support for docker / docker-compose and out-of-date documentation

    13
    1 Votes
    13 Posts
    2k Views
    E
    Forget it buddy. I think your reading skills a flawed. As i said before i dont have problems with my containers. The official NodeBB docker container does not adhere to essential docker rules, which are: do not mess with persistant data. But i doubt you are able to grasp that. Lets leave it here.
  • Private (profile image) uploads

    1
    0 Votes
    1 Posts
    579 Views
    yusfY
    When I enable the setting Make uploaded files private I expect profile images to go private as well, but it does not. I've tried to reupload avatars to check if the setting would apply to new uploads only, but there's no difference. How do I make profile images accessibly to logged in users only?
  • Make codes LTR in RTL forums

    2
    0 Votes
    2 Posts
    474 Views
    I
    Hello, Any comments or suggestion or any future updates?
  • Setting the language - server-side / client-side

    7
    0 Votes
    7 Posts
    884 Views
    D
    @PitaJ I think I have a very edge-case scenario, I've found a solution for guests and logged in users. Thanks for your help and point in the right direction!
  • Bulk "unsubscribe" emails

    7
    0 Votes
    7 Posts
    739 Views
    D
    @julian As a followup, I received an email from Postmark. They basically told me that they prefer that customers manage their own lists. They're a transnational email provider not a service to maintain lists. I'm with them on this. It's the responsibility of the owner of the list to maintain the list. Right now NodeBB punts that to the email provider.
  • non-english url slug

    2
    0 Votes
    2 Posts
    394 Views
    PitaJP
    This isn't an option at the moment. Why do you want to do this?
  • ERROR invalid-event

    11
    0 Votes
    11 Posts
    1k Views
    y hY
    plugins.browsingUsers
  • error: /logout invalid csrf token [use ssl, nginx, master branch]

    10
    0 Votes
    10 Posts
    3k Views
    PitaJP
    @KevinPan your problem is not exactly the same, because according to your reply over there, you're using IIS not nginx. I don't know how to use IIS (don't know if any one else here who does) but you'll need to set the same headers that we do in the example nginx file: https://docs.nodebb.org/configuring/proxies/nginx/#basic-setup
  • Double URL problem after login | https in config.json gives session error

    19
    1 Votes
    19 Posts
    2k Views
    K
    I have deployed NodeBB via Windows IIS (IIS Node), and I have met the same problem, how can I hot fix this issue.
  • Password will not save between user side and admin area.

    1
    0 Votes
    1 Posts
    745 Views
    emccaE
    I am using Heroku to host a nodeBB instance. When using the heroku supplied subdomain (and setting it in the config.json), everything works fine. I can log in as admin account, use admin GUI, and everything works well. When I set up custom domain (.me tld if that matters), configure it in Heroku, config.json, and DNS, I can get to the site, log in, but when I try to go to the admin area, it asks me to sign in. Once I sign in, it brings me back to the homepage (not admin GUI). I am using cloudflare for DNS and have tried with no plugins, vanilla install. I am using redis. I have tried both proxying through cloudflare "orange cloud" and not proxying "grey cloud" record. Any ideas?
  • Apache + nginx SSL config for csrf token

    10
    1 Votes
    10 Posts
    5k Views
    K
    I have the same problem, I host the NodeBB with IIS (IIS Node)
  • Notification email does not display correctly

    3
    0 Votes
    3 Posts
    495 Views
    seadogS
    I am running Nodebb v.1.12.2.
  • How i force https?

    4
    0 Votes
    4 Posts
    465 Views
    Sandeep BhuiyaS
    hello you can create two separate vhosts for 80 and 443 and add redirect to htttps in http (port 80) vhost rewrite ^(.*)$ https://www.$host$1 permanent; or return 301 https://$server_name$request_uri;