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.
  • /manifest.webmanifest 401 (Unauthorized)

    Solved
    9
    0 Votes
    9 Posts
    2k Views
    B
    @pitaj Oh, this looks very promising. Thank you for the pointer.
  • How to set email as verified using REST API ?

    Unsolved
    1
    0 Votes
    1 Posts
    286 Views
    Sanka DarshanaS
    I'm trying to set the user's email as verified programmatically. But the following doesn't seems to work. Is there a way to do this or is currently not supported? [image: 1633449959606-3c817e01-1e02-407d-9208-6e49b5a732ab-image.png]
  • This topic is deleted!

    Solved
    1
    0 Votes
    1 Posts
    10 Views
  • CSP HSTS et al. regarding nodebb srv security

    Unsolved
    1
    0 Votes
    1 Posts
    205 Views
    B
    Currently, I'm deploying with the following security config. Working fine so far, I'd like to get some community feedback. add_header Content-Security-Policy "default-src 'none'; \ connect-src 'self' https://forum.myforum.com/ wss://forum.myforum.com/ https://bootswatch.com/ https://api.github.com/; \ script-src 'self' 'unsafe-inline https://forum.myforum.com/ https://storage.googleapis.com/; \ img-src 'self' data: https://forum.myforum.com/ https://bootswatch.com/ https://i.imgur.com/ https://www.gravatar.com/; \ style-src 'self' 'unsafe-inline' https://forum.myforum.com/ https://fonts.googleapis.com/ https://maxcdn.bootstrapcdn.com/; \ font-src https://forum.myforum.com/ https://maxcdn.bootstrapcdn.com/bootswatch/latest/fonts/ chrome-extension://* https://fonts.gstatic.com/; \ frame-ancestors 'self'; \ object-src 'none'; manifest-src https://forum.myforum.com/;"; add_header Strict-Transport-Security "max-age=63072000; includeSubDomains; preload";׬ add_header 'Referrer-Policy' 'same-origin';¬ add_header X-Content-Type-Options nosniff;¬ add_header X-XSS-Protection "1; mode=block";¬ add_header X-Download-Options noopen;¬ add_header X-Permitted-Cross-Domain-Policies none;¬ add_header X-Frame-Options "SAMEORIGIN"; Helpful website for testing was https://observatory.mozilla.org/ edit: add manifest-src to enable webmanifest loading
  • Is the PICTURE button outdated in the EDITOR MENU?

    Unsolved
    9
    0 Votes
    9 Posts
    958 Views
    gotwfG
    @zandertrek said in Is the PICTURE button outdated in the EDITOR MENU?: @gotwf said [The icons] could perhaps use better mouse hover labels? I've noted for quite some time that PICTURE doesn't accurately describe that button's function. I offer DISPLAY WEB IMAGE as more meaningful. I concur. Maybe "External Image Link" would be descriptive? Maybe a bit on the long side so maybe edit that down to "Image Link"? Cuz I also guess that said image link may well be to some other image already uploaded. My $0.02. Ymmv. Peace.
  • Can't make api/user work with a token

    Solved
    2
    0 Votes
    2 Posts
    506 Views
    F
    Well i found a solution with the users query : const axiosInstanceForNativeAPI = axios.create({ baseURL: ENDPOINT_URL, headers: { Authorization: ADMIN_TOKEN_FOR_NATIVE_API }, }); export const getUserByEmail = email => axiosInstanceForNativeAPI.get(`/users?searchBy=email&query=${email}`); export const getUserByUsername = username => axiosInstanceForNativeAPI.get(`/users?searchBy=username&query=${username}`);
  • New Install - Plugin Page Freezes

    Solved
    73
    0 Votes
    73 Posts
    12k Views
    Sampo2910S
    I will mark this now as solved. That is on the basis that this only happened when I was running nodebb as a service. I have changed nothing other than removing the service and the plugin page loads no problem. I will try later and add the service again and see if i can reproduce the error.
  • Forbid links to new users

    Unsolved
    2
    0 Votes
    2 Posts
    389 Views
    barisB
    This has been requested before https://github.com/NodeBB/NodeBB/issues/6021 So far it's not implemented, so you would need a plugin.
  • Forum down after restart

    Solved
    76
    0 Votes
    76 Posts
    11k Views
    phenomlabP
    @PitaJ Sorry I'm a little late responding here. I've used systemd as defined below, which works fine, and survives a rebuilt and restart [Unit] Description=Sudonix Documentation=https://docs.nodebb.org After=system.slice multi-user.target mongod.service [Service] Type=forking User=sudonix StandardOutput=syslog StandardError=syslog SyslogIdentifier=nodebb WorkingDirectory=/home/sudonix/nodebb PIDFile=/home/sudonix/nodebb/pidfile ExecStart=/usr/bin/env node loader.js Restart=always [Install] WantedBy=multi-user.target Many thanks for all the help and support. Greatly appreciated.
  • Upgrade to 1.17.2 and cluster configurtaion

    Solved
    7
    0 Votes
    7 Posts
    846 Views
    E
    @baris Thank you so much for confirming this. Since my config was working before, I changed my focus only to network and found the issue. In my nginx config I had: listen 80 listen 443 default ssl Miraculously this had worked for last four years without issue. My server has 4 nic cards and nginx was listening to the wrong interface. Modified nginx config to bound it to the right ip:port to solve the issue. Happy to be back on-line and thanks for your support.
  • 0 Votes
    2 Posts
    485 Views
    barisB
    You can change this in the ACP. [image: 1632977464071-edb50722-b698-4032-bde7-ba07963bd6f9-image.png]
  • Does the client-nojs element exist in the nodebb system?

    Unsolved
    1
    0 Votes
    1 Posts
    257 Views
    J
    Hi, In a MediaWiki system you can use a class called client-nojs. To apply CSS formatting to anyone who disables JavaScript in browser settings / using a plugin. I tried to use this class with the same code (just for example: .client-nojs * { display: none } This code should hide all the elements on the page for anyone who disables js. In the MediaWiki system I tried this code it worked well, but in the Nodebb system nothing happened.) The question is is there a parallel to this in the nodebb system?
  • How to post in chat room using API

    Unsolved
    1
    0 Votes
    1 Posts
    324 Views
    Spin0usS
    Hi there, I'm working on a script that interact with NodeBB using API. I need to create a new chat room between 2 users and post content in it. In the API documentation, there's some data concerning "Accessing a chat room" and "Getting a chat room", but in write api there's nothing at all. Is it currently impossible to post content in the chat room from the api? I'm using NodeBB v1.17.0. Api key created in admin panel. No problem to read chat room but writing failed. { "status": { "code": "not-found", "message": "Invalid API call" }, "response": {} }
  • How to solve the invalid login after closing cloudflare

    Unsolved
    1
    0 Votes
    1 Posts
    228 Views
    hmilyldH
    I deployed nodebb in a docker container, and a strange problem occurred after the deployment was completed. When I turned on the cloudflare proxy, I could log in and register normally, but after I turned off the cloudflare proxy, I couldn’t log in. Although the login was successful, But the actual situation is still a tourist. How should this problem be solved? thanks
  • Invalid Session It looks like your login session is no longer active

    Solved
    3
    0 Votes
    3 Posts
    879 Views
    B
    SOLVED Found the solution. Still had proxy directives in nginx config envs other than location / {}. So it was again an error introduced by an nginx config deviating from the recommendation by https://docs.nodebb.org/configuring/scaling/ .
  • theme-quickstart: template created, is found (no 404) but not rendered.

    Solved
    6
    0 Votes
    6 Posts
    734 Views
    B
    SOLVED In the end, it was a proxy/cache issue, I assume. After fixing the proxy directives' placement in nginx config, disabling nginx caching, rebuilding and reloading nodebb and switching themes and back again, the issue was no longer there. After reenabling caching, everything was still ok. In case it should become clearer what caused the issue, I'll update this answer. For the JS issue, refer to https://community.nodebb.org/topic/16031/template-js-not-executed . Thanks.
  • How to host nodebb within a specific path ?

    Solved
    2
    0 Votes
    2 Posts
    359 Views
    PitaJP
    Yeah essentially you just set the correct url with your /forum path in config.json and set your reverse proxy to forward that path onto NodeBB: https://docs.nodebb.org/configuring/proxies/nginx/#basic-with-subfolder-install
  • Yet another error upon upgrade.

    Solved
    3
    0 Votes
    3 Posts
    1k Views
    Sampo2910S
    @pitaj said in Yet another error upon upgrade.: npm install --global npm@6 That worked. Thanks as always
  • Forum Time

    Unsolved
    18
    0 Votes
    18 Posts
    2k Views
    PitaJP
    We log UTC time because then it doesn't matter where your server is or where you live. This isn't likely to change, but as I said, you can always ask on GitHub.
  • Header issues

    Unsolved
    2
    0 Votes
    2 Posts
    359 Views
    barisB
    Looks like assets aren't built. Try ./nodeb stop ./nodebb build ./nodebb start