Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode . Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

nm v9.2.0
node v18.13.0

I couldn't connect via browser, and at least thought it was started, but browser was not resolving to x.x.x.x:4567, so I ran ./nodebb dev start, saw this:

error: MongoServerSelectionError: connect ECONNREFUSED 127.0.0.1:27017
I'm a'gunna guess this is my problem and I'm having the same issue as logged below on github, as usual this is a bit above my pay grade (no mongo troubleshooting experience), but it may be a bug - Has anyone else hit this?
Nodejs v18 gives: MongooseServerSelectionError: connect ECONNREFUSED ::1:27017 · Issue #12134 · Automattic/mongoose
Prerequisites I have written a descriptive issue title I have searched existing issues to ensure the bug has not already been reported Mongoose version 6.4.6 Node.js version 81.x MongoDB server version 6.0 Description If I'm using NodeJS...
Here is the full dev output:
Clustering enabled: Spinning up 1 process(es).
2023-11-13T11:04:42.470Z [4567/2944] - verbose: * using configuration stored in: /home/nodebb/config.json
2023-11-13T11:04:42.475Z [4567/2944] - info: Initializing NodeBB v3.5.0 http://x.x.x.x:4567
2023-11-13T11:04:42.476Z [4567/2944] - verbose: * using mongo store at 127.0.0.1:27017
2023-11-13T11:04:42.476Z [4567/2944] - verbose: * using themes stored in: /home/nodebb/node_modules
2023-11-13T11:05:12.902Z [4567/2944] - error: MongoServerSelectionError: connect ECONNREFUSED 127.0.0.1:27017
    at EventTarget.<anonymous> (/home/nodebb/node_modules/mongodb/lib/sdam/topology.js:276:34)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:735:20)
    at EventTarget.dispatchEvent (node:internal/event_target:677:26)
    at abortSignal (node:internal/abort_controller:308:10)
    at TimeoutController.abort (node:internal/abort_controller:338:5)
    at Timeout.<anonymous> (/home/nodebb/node_modules/mongodb/lib/utils.js:1010:92)
    at listOnTimeout (node:internal/timers:564:17)
    at process.processTimers (node:internal/timers:507:7)
[cluster] Child Process (2944) has exited (code: 0, signal: null)
@omega This error tends to lean itself towards the MongoDB service not being started
error: MongoServerSelectionError: connect ECONNREFUSED 127.0.0.1:27017
Can you confirm that the MongoDB service is running?
@phenomlab
sudo systemctl status mongod
Loaded: loaded (/lib/systemd/system/mongod.service; disabled; preset: enabled)
   Active: inactive (dead)
     Docs: https://docs.mongodb.org/manual