Squashing a bug

NodeBB Development
  • I'm trying to run the app locally and it's worked fine in the past. I don't remember making any changes, but maybe I accidentally did something with git that messed things up. When I run it now, here's what happens:

    $ node app
    info: NodeBB v0.3.0 Copyright (C) 2013 DesignCreatePlay Inc.
    info: This program comes with ABSOLUTELY NO WARRANTY.
    info: This is free software, and you are welcome to redistribute it under certain conditions.
    info: Initializing NodeBB v0.3.0, on port 4567, using redis store at
    info: NodeBB instance bound to: Any address (
    error: undefined

    if (meta.config['social:twitter:key'] && meta.config['social:twitter:secret']
    TypeError: Cannot read property 'social:twitter:key' of undefined
    at /Users/aaronclaytondunn/Documents/WebDev/forum/nodebb/forum/src/routes/authentication.js:35:17
    at Object.<anonymous> (/Users/aaronclaytondunn/Documents/WebDev/forum/nodebb/forum/src/routes/authentication.js:220:2)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:349:32)
    at Function.Module._load (module.js:305:12)
    at Module.require (module.js:357:17)
    at require (module.js:373:17)
    at Object.<anonymous> (/Users/aaronclaytondunn/Documents/WebDev/forum/nodebb/forum/src/routes/api.js:8:9)
    at Module._compile (module.js:449:26)
    Aarons-MacBook-Air-2:forum aaronclaytondunn$

    Any ideas? Thanks!

  • Mmm, that usually means your redis server is not turned on, or NodeBB can't communicate with it!

  • Haha oops. Thanks! I just started the redis and node servers and everything looked fine. But when I try to visit localhost:4567, there's nothing to be found at that address! Any idea what happened?

  • @aaron - What does your config.json say? Perhaps it's serving on a different port?

  • config.json:

        "base_url": "http://localhost",
        "port": "4567",
        "use_port": true,
        "secret": "somesecret",
        "bind_address": "",
        "database": "redis",
        "redis": {
            "host": "",
            "port": "6379",
            "password": "",
            "database": "0"
        "bcrypt_rounds": 12,
        "upload_path": "/public/uploads",
        "relative_path": ""

    That should be fine, right?

  • This post is deleted!
  • Hm, that looks to be alright. Does NodeBB say "NodeBB Ready." when you start it? What errors crop up in the console or in the browser (using Chrome Inspector or Firebug) when you try to go to port 4567?

  • Sometimes on your "host" file .. it doesnt point "localhost" to thats your original root ip.. 🙂

    could u check it?

  • Thanks everyone! Here's a screenshot of what happens when I run the app and try to visit the homepage with developer tools turned on. The only other thing that isn't working properly is redis. If I type in redis-cli ping, I get a blank cursor in response. You can see that happening in the image below. That said, I did kill and restart redis pointing to the proper configuration file that's worked before.

    Screen Shot 2014-02-04 at 10.23.15 AM.png

  • I re-downloaded Redis from scratch and it worked.

Suggested Topics

  • NodeBB 3.4.0

    NodeBB Development
    8 Votes
    23 Posts

    I don't know @baris I didn't notice it right away.
    Juste today, 3 or 4 day ago after creation.

    I suggest that I monitor this if that suits you of course

  • 5 Votes
    1 Posts

    We recently received some inquiries about how long we will support 1.x and 2.x with security fixes.

    1.x will be supported for another 12 months up until August 2024 2.x will be supported for another 24 months up until August 2025

    We also released https://github.com/NodeBB/NodeBB/releases/tag/v2.8.16 and https://github.com/NodeBB/NodeBB/releases/tag/v1.19.12 containing some of the fixes from the 3.x line. If you are not able to upgrade to 3.x we encourage you to upgrade to these releases.

  • 8 Votes
    7 Posts

    @phenomlab very true. A lot of talented people have done some surprisingly cool things with just the custom css panel.

  • 9 Votes
    40 Posts

    @julian said in What's next after v3?:

    I've said it there and I'll say it here. NodeBB will follow the ActivityPub spec and, if possible, will be tested against both Flarum and Discourse integrations because doing so makes federated forums a force to be reckoned with.

    This is good. More and more development efforts too are focusing so little on the Mastodon API and instead focusing on the actual standards - S2S & C2S as they should.

    Building Federation for the Fediverse is of paramount consideration, while making sure one federates with a single Fediverse platform whose significance is waning as the bellweather for social communications. Even entire Mastodon communities have left that platform and migrated en masse to other, more capable platforms - some outright forks like Glitch-Soc or Hometown, and many more to other more promising Fediverse platforms that have enjoyed greater adoption due to their more accommodating utility for their userbases.

    In the End, it's not really about communities built on an instance and provided to the user base - it's about users across the entire #Fediverse building communities that span the myriad platforms and instances; especially as smolweb / smallweb and single user platforms continue to build critical mass in terms of installed instances.

    #Friendica, being one of the great-grandaddy's of, and staples in, the Fediverse, is a great platform chosen by many projects to effectively represent the branding, marketing, and social communications needs - blogs, announcements, changelogs, newsletters, and public dialog... Things a limited microblogging software cannot deliver.

  • 1 Votes
    4 Posts

    @baris He said he uses 1.4.5 and Chrome in Mac OS.He tried to destroy his friend's experimental community,and then my friend's forum throwed an error:(See the image)