Mo time mo problems

Technical Support
  • Was playing around with nodebb today and loving it! Unfortunately, I decided to change the theme (to one of the other default included themes) and it nuked the forum. I don't know why, but it was no longer accessible. I tried running the restart command but it said there was no instance running. The start command didn't do much, either.

    So.....destroy droplet (am on DigitalOcean) and start again.

    Well, funny thing is I can't install nodebb this time around. I've been following the same steps to a tee. Even tried CentoOS, too. Regardless of the flavor of 'nix I try I always get this same error when running the setup:

    Error: Cannot find module 'mmmagic'

    I use the defaults during setup (see below for full details):

    **[root@forum nodebb]# ./nodebb setup
    19/10 04:03 [26348] - info: NodeBB Setup Triggered via Command Line

    Welcome to NodeBB!

    This looks like a new installation, so you'll have to answer a few questions about your environment before we can proceed.
    Press enter to accept the default setting (shown in brackets).
    URL used to access this NodeBB (http://localhost:4567)
    Please enter a NodeBB secret (feea4985-9f12-4f38-b284-be1c982a63a9)
    Which database to use (redis)

    19/10 04:03 [26348] - info: Now configuring redis database:
    Host IP or address of your Redis instance (127.0.0.1)
    Host port of your Redis instance (6379)
    Password of your Redis database
    Which database to use (0..n) (0)
    Configuration Saved OK
    [email protected] node_modules/redis

    [email protected] node_modules/connect-redis
    ā””ā”€ā”€ [email protected] ([email protected])
    Populating database with default configs, if not already set...

    module.js:340
    throw err;
    ^
    Error: Cannot find module 'mmmagic'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/home/bmmcadmin/nodebb/src/file.js:7:12)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    [root@forum nodebb]#
    **

  • Which version of node are you using? I think there are issues with the most recent release and mmmagic

  • @BDHarrington7 No idea, and wouldn't know how to check it. Anyway, I already destroyed the Droplet so I can't answer that question. In a bit I will rebuild a new CentOS droplet and start from scratch.

    I think my biggest issue is simply not understanding file and directory paths. I am likely in the wrong folder running commands that expect me to be in another folder, etc.

    If I had hair on my head it would be gone by now.


Suggested Topics


  • problem on profile page

    Unsolved Technical Support
    0 Votes
    1 Posts
    129 Views

    There is a problem with the view on the profile page. (mobile)

    Screenshot_20220114-180024.jpg

    .account .cover { . top: calc(var(--panel-offset) + 50px); */ I think it's caused by . }
  • 0 Votes
    8 Posts
    530 Views

    @pitaj great! This is what I am looking for. šŸ˜‰ And you understood it even though I wrote it wrong. šŸ¤¦ Actually I would ask for ./nodebb upgrade --series but a config option is much better. Thank you! šŸ™ It would be great if you could include this option in the documentation.

  • 1 Votes
    4 Posts
    521 Views

    @FrankM said in Probmes with login after upgrading to 1.11.0:

    But in config.json i have http://...... Edit it to https:// solved the problem.
    Before version 1.11.0 i don't have this problem.

    Thanks, that solved the problem for me as well, changing http to https. And as for you, I did not have this problem before 1.11.0

    But then an other problem turned up: "Invalid CSRF Token"

    Pls see this link https://community.nodebb.org/topic/9222/invalid-csrf-token

    My solution for this was what is written in the end (I use Apache2)

    for the record for people finding this via search, for apache2 you have to set this somewhere in your nodebb vhost configuration
    with ssl

    RequestHeader set X-Forwarded-Proto "https"

    without ssl

    RequestHeader set X-Forwarded-Proto "http"

    you might have to enable mod_headers to do so!

    So upgrading to 1.11.0 gave me a problem that had to be solved in 2 steps. First by changing in config.json, then I had to modify Apache2 settings.

  • 0 Votes
    10 Posts
    573 Views

    @baris

    New error, hope it's okay:

    4. Updating NodeBB data store schema... Parsing upgrade scripts... 2018-11-30T15:21:24.425Z [24448] - warn: [upgrade/appendPluginScripts] Unable to read plugin.json for plugin `nodebb-plugin-import-smf-1`. Skipping. OK | 1 script(s) found, 67 skipped ā†’ [2019/1/26] Changing dbsearch mongodb search schema to use _id... 2018-11-30T15:21:24.509Z [24448] - error: ns not found MongoError: ns not found at /var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:581:63 at authenticateStragglers (/var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:504:16) at Connection.messageHandler (/var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:540:5) at emitMessageHandler (/var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:310:10) at Socket.<anonymous> (/var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:453:17) at emitOne (events.js:116:13) at Socket.emit (events.js:211:7) at addChunk (_stream_readable.js:263:12) at readableAddChunk (_stream_readable.js:250:11) at Socket.Readable.push (_stream_readable.js:208:10) {"ok":0,"errmsg":"ns not found","code":26,"codeName":"NamespaceNotFound","name":"MongoError"} 2018-11-30T15:21:24.512Z [24448] - error: ns not found MongoError: ns not found at /var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:581:63 at authenticateStragglers (/var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:504:16) at Connection.messageHandler (/var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:540:5) at emitMessageHandler (/var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:310:10) at Socket.<anonymous> (/var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:453:17) at emitOne (events.js:116:13) at Socket.emit (events.js:211:7) at addChunk (_stream_readable.js:263:12) at readableAddChunk (_stream_readable.js:250:11) at Socket.Readable.push (_stream_readable.js:208:10) {"ok":0,"errmsg":"ns not found","code":26,"codeName":"NamespaceNotFound","name":"MongoError"}

    Thanks for the help BTW.

  • 0 Votes
    1 Posts
    752 Views

    Any know issues with 1.4.6?

    Issues:
    https://github.com/NodeBB/NodeBB/issues/5625 <-- Will this be fixed or do we need to wait for 1.4.7?