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.
  • Block 1 user from seeing category

    6
    0 Votes
    6 Posts
    2k Views
    absurdsmashA
    @pitaj said in Block 1 user from seeing category: NodeBB permissions are additive only, there are no negative permissions such as denying a specific user or group. Sorry to bump an old topic; are there any plans to implement such a feature anyway? Or is there a way we can build this ourselves? Its a pain right now to organize birthday gifts and allow everyone but one person.
  • Downgrading from 1.8 to 1.7

    3
    0 Votes
    3 Posts
    1k Views
    julianJ
    Hi @RogerLevy -- the import process should be fine, there aren't any major breaking changes. In fact, if you really want, our upgrade scripts are supposed to be idempotent, so you can run them again (by deleting the schemaLog value from the database) so that ./nodebb upgrade runs them all again. Alternatively, delete individual items from that sorted set. Alternatively, run individual upgrades by executing ./nodebb upgrade upgrade_script_name Lots of options!
  • Connection to NodeBB was lost

    3
    0 Votes
    3 Posts
    1k Views
    T
    @pitaj yes you are right. Issue found, wrong redirect. Thanks
  • NodeBB AWS auto scaling

    14
    2 Votes
    14 Posts
    3k Views
    F
    @yariplus my config { "url": "https://staging.XXXX.org", "secret": "XXXX", "database": "mongo", "port": 4567, "mongo": { "host": "172.31.42.228", "port": 27017, "database": "nodebb", "username": "nodebb", "password": "AAAAA" }, "oauth": { "id": "2bb8010d070f0be6f58d", "secret": "36a6b6da7df8e96f92b2aae22e24306a619a5413" }, "socket.io": { "origins": "https://staging.XXXX.org:* https://staging.XXXX.org:*", "transports": ["websocket"], "address": "https://staging.XXXX.org" }, "socket.io:origins": "https://staging.XXX.org", "sessionKey": "express.sid", "cookieDomain": ".philanthropyu.org", "socket.io:transports": ["websocket"], "redis": { "host":"nodebb.ifinyn.0001.euc1.cache.amazonaws.com", "port":"6379", "database": 0 }, "edx_host": "https://staging.XXXXX.org", "aws_access_key_id": "xxxxxxx", "s3_path": "https://XXX-community-uploads.s3.amazonaws.com/", "aws_secret_access_key": "xxxxxxxxxx", "master_token": "xxxxxxxxxx" }
  • Is there a tutorial for installing nodebb on heroku

    2
    0 Votes
    2 Posts
    840 Views
    G
    https://docs.nodebb.org/installing/cloud/heroku/
  • This topic is deleted!

    2
    0 Votes
    2 Posts
    38 Views
  • Locked out of the forum: Error: misconfigured csrf

    Unsolved
    1
    0 Votes
    1 Posts
    1k Views
    J
    Hello, I have a forum hosted on AWS. The code is synced to master. I am using nginx on the same server, with SSL. Furthermore I am using Redis (provided by AWS). As of today's noon, when I browse the forum's address, I get ERR_TOO_MANY_REDIRECTS on the client side. Looking at the server logs I see "Error: misconfigured csrf". Let me assure you that the config file was not changed. Furthermore Redis is up and running (I can browse the database via Redis desktop manager). I tried resolving it till now (removing all plugins, removing nginx, removing FW, removing SSL, etc. etc.). In addition I changed the config file to: http://www.mysite.com https... www.mysite.com (the original value). 127.0.0.1:4567 (nginx forwards to that address) Nada... Its frustrating... Any idea ? Thank you in advance! JJ.
  • nodebb-plugin-groups-autoassigncategory permission change

    1
    0 Votes
    1 Posts
    611 Views
    B
    Hello, just wondered if you could quickly point me in the right direction. I'm using the autoassigncategory plugin, however I would like it to auto remove the find/read permissions for newly created categories for guests and registered-public, do you know how I could do this or point me to the correct documentation? Thanks.
  • NodeBB Configurations Migration

    3
    0 Votes
    3 Posts
    878 Views
    Y
    @giggiux I want to store the configuration/settings into SCM so that in the worst case scenario we can rebuild the instance. And i don't want to clone the datasets either
  • Custom theme being removed when installing new modules

    3
    0 Votes
    3 Posts
    2k Views
    B
    Thank you very much! @Giggiux
  • Paypal Subscription Plugin

    2
    0 Votes
    2 Posts
    1k Views
    B
    There seems to be one thats newer than the one that npm installs (npm installs a forked version rather than the original author). I manually put this one (https://github.com/psychobunny/nodebb-plugin-paypal-subscriptions) in and now it works (don't forget to rebuild too)
  • Failed to look up latest available version of NodeBB

    2
    0 Votes
    2 Posts
    923 Views
    PitaJP
    https://community.nodebb.org/topic/12080/error-acp-failed-to-fetch-latest-version
  • regaring running nodebb

    4
    0 Votes
    4 Posts
    1k Views
    J
    @abhinov-singh If you are using Nginx on Ubuntu, the configuration files or symlinks (including ports, etc.) are at /etc/nginx/sites-enabled/ See also which ports are left open by your firewalls (server, PC).
  • Urgent help regrading nodebb running

    2
    0 Votes
    2 Posts
    825 Views
    J
    @abhinov-singh With a normal configuration, NodeBB needs MongoDB running. You can check it with: service mongod status Also, you can try from your nodebb folder: ./nodebb status ./nodebb restart See also your nodebb/logs/output.log file, or just the recent lines with: ./nodebb log (Ctrl-C to exit)
  • Debug Nodebb load

    15
    0 Votes
    15 Posts
    3k Views
    barisB
    @damian-gądziak Maybe you can try to debug by adding this in that function console.log(tids.length, uid, new Error('test').stack); Topics.filterWatchedTids = function (tids, uid, callback) { console.log(tids.length, uid, new Error('test').stack); async.waterfall([ function (next) { db.sortedSetScores('uid:' + uid + ':followed_tids', tids, next); }, function (scores, next) { tids = tids.filter(function (tid, index) { return tid && !!scores[index]; }); next(null, tids); }, ], callback); }; I am guessing the function is called by a huge amount of tids, so the next step would be to find out why and from where.
  • Internet connection broken while running upgrade

    3
    0 Votes
    3 Posts
    785 Views
    Damian GądziakD
    Protip for someone in the future who will visit this topic: DB keeps schemaDate (timestamp) and schemaLog (table), you can read this keys to check which schema upgrades are already applied. topic can be closed
  • after mongoDB-Update, nodeBB doesn't work

    Unsolved
    2
    0 Votes
    2 Posts
    896 Views
    PitaJP
    What version of node and npm do you have installed?
  • 1 Votes
    3 Posts
    2k Views
    J
    @h7 Thanks, this helped, in my case with no need to make the app public. It's still "In Development", but working. The settings at Facebook for Developers are like the following: Settings > Basic Display Name: Example Community Login App Domains: example.com Contact Email: [email protected] Privacy Policy URL: https://example.com/privacy/ Category: Some category Site URL: https://example.com/community/ Facebook Login > Settings [yes] Client OAuth Login [yes] Web OAuth Login [no] Force Web OAuth Reauthentication [yes] Use Strict Mode for Redirect URIs [yes] Enforce HTTPS [no] Embedded Browser OAuth Login Valid OAuth Redirect URIs: https://example.com/community/auth/facebook/callback [no] Login from Devices Well, not sure if all this is needed, but after many tests it's working this way. There is also the interesting video Facebook SSO for NodeBB - YouTube, which is helpful although not complete.
  • nodeBB 1.8.2 ubuntu16.04.2 redis install from scratch

    6
    0 Votes
    6 Posts
    1k Views
    S
    @sfchun said in nodeBB 1.8.2 ubuntu16.04.2 redis install from scratch: node app --setup I guess that was not the right step here. I copied the content of package.json from my running nodebb { "name": "nodebb", "license": "GPL-3.0", "description": "NodeBB Forum", "version": "1.8.2", "homepage": "http://www.nodebb.org", "repository": { "type": "git", "url": "https://github.com/NodeBB/NodeBB/" }, "main": "app.js", "scripts": { "start": "node loader.js", "lint": "eslint --cache ./nodebb .", "pretest": "npm run lint", "test": "nyc --reporter=html --reporter=text-summary mocha", "coveralls": "nyc report --reporter=text-lcov | coveralls && rm -r coverage" }, "dependencies": { "ace-builds": "^1.2.9", "async": "2.6.0", "autoprefixer": "7.2.4", "bcryptjs": "2.4.3", "benchpressjs": "^1.2.1", "body-parser": "^1.18.2", "bootstrap": "^3.3.7", "chart.js": "^2.7.1", "clipboard": "1.7.1", "colors": "^1.1.2", "commander": "^2.12.2", "compression": "^1.7.1", "connect-ensure-login": "^0.1.1", "connect-flash": "^0.1.1", "connect-mongo": "2.0.1", "connect-multiparty": "^2.1.0", "connect-redis": "3.3.3", "cookie-parser": "^1.4.3", "cron": "^1.3.0", "cropperjs": "^1.2.2", "csurf": "^1.9.0", "daemon": "^1.1.0", "diff": "^3.4.0", "express": "^4.16.2", "express-session": "^1.15.6", "express-useragent": "1.0.8", "graceful-fs": "^4.1.11", "helmet": "^3.11.0", "html-to-text": "3.3.0", "ipaddr.js": "^1.5.4", "jimp": "0.2.28", "jquery": "^3.2.1", "jsesc": "2.5.1", "json-2-csv": "^2.1.2", "less": "^2.7.3", "lodash": "^4.17.4", "logrotate-stream": "^0.2.5", "lru-cache": "4.1.1", "material-design-lite": "^1.3.0", "mime": "^2.2.0", "minimist": "^1.2.0", "mkdirp": "^0.5.1", "mongodb": "2.2.33", "morgan": "^1.9.0", "mousetrap": "^1.6.1", "mubsub": "^1.4.0", "nconf": "^0.9.1", "nodebb-plugin-composer-default": "6.0.20", "nodebb-plugin-composer-redactor": "^3.2.0", "nodebb-plugin-dbsearch": "2.0.13", "nodebb-plugin-emailer-local": "0.2.1", "nodebb-plugin-embed-videos": "0.1.9", "nodebb-plugin-emoji": "^2.2.3", "nodebb-plugin-emoji-android": "2.0.0", "nodebb-plugin-emoji-extended": "1.1.1", "nodebb-plugin-emoji-one": "^2.0.0", "nodebb-plugin-imagemagick": "^2.0.5", "nodebb-plugin-imgbed": "1.0.2", "nodebb-plugin-markdown": "8.4.2", "nodebb-plugin-mentions": "2.2.4", "nodebb-plugin-poll": "^0.2.17", "nodebb-plugin-registration-question": "0.1.8", "nodebb-plugin-rss": "1.1.9", "nodebb-plugin-soundpack-default": "1.0.0", "nodebb-plugin-spam-be-gone": "0.5.3", "nodebb-plugin-sso-steam-v2": "2.0.1", "nodebb-plugin-topic-tags": "0.1.3", "nodebb-plugin-youtube-lite": "0.4.8", "nodebb-rewards-essentials": "0.0.11", "nodebb-theme-lavender": "5.0.4", "nodebb-theme-persona": "8.0.9", "nodebb-theme-slick": "1.2.1", "nodebb-theme-vanilla": "9.0.7", "nodebb-widget-advanced-essentials": "0.1.5", "nodebb-widget-essentials": "4.0.2", "nodemailer": "4.4.1", "passport": "^0.4.0", "passport-local": "1.0.0", "postcss": "6.0.15", "postcss-clean": "1.1.0", "promise-polyfill": "^7.0.0", "prompt": "^1.0.0", "redis": "2.8.0", "request": "2.83.0", "rimraf": "2.6.2", "rss": "^1.2.2", "sanitize-html": "^1.16.3", "semver": "^5.4.1", "serve-favicon": "^2.4.5", "sitemap": "^1.13.0", "socket.io": "2.0.4", "socket.io-adapter-mongo": "^2.0.1", "socket.io-client": "2.0.4", "socket.io-redis": "5.2.0", "socketio-wildcard": "2.0.0", "spdx-license-list": "^3.0.1", "spider-detector": "1.0.18", "toobusy-js": "^0.5.1", "uglify-es": "^3.3.9", "uglify-js": "^3.3.4", "validator": "9.2.0", "winston": "^2.4.0", "xml": "^1.0.1", "xregexp": "3.2.0", "zxcvbn": "^4.4.2" }, "devDependencies": { "coveralls": "^3.0.0", "eslint": "^4.14.0", "eslint-config-airbnb-base": "^12.1.0", "eslint-plugin-import": "^2.8.0", "grunt": "^1.0.1", "grunt-contrib-watch": "^1.0.0", "jsdom": "^11.5.1", "mocha": "^4.1.0", "mocha-lcov-reporter": "^1.3.0", "nyc": "^11.4.1", "smtp-server": "^3.4.1" }, "bugs": { "url": "https://github.com/NodeBB/NodeBB/issues" }, "engines": { "node": ">=6" }, "maintainers": [ { "name": "Andrew Rodrigues", "email": "[email protected]", "url": "https://github.com/psychobunny" }, { "name": "Julian Lam", "email": "[email protected]", "url": "https://github.com/julianlam" }, { "name": "Barış Soner Uşaklı", "email": "[email protected]", "url": "https://github.com/barisusakli" } ] } then run $ npm start > [email protected] start /var/www/mydomain.com > node loader.js 2018-04-19T07:47:44.529Z [450] - info: Launching web installer on port 4567 2018-04-19T07:47:44.931Z [450] - info: Web installer listening on http://0.0.0.0:4567 Now everything is fine, but sadly I dont know how this file was originaly generated it seems it does not come from nodebb github repo ... At least I can continue !...
  • Moving to another server.

    4
    0 Votes
    4 Posts
    1k Views
    J
    You can also see some details at Moving a NodeBB mongo DB from one server to another.