Skip to content
  • A place to talk about whatever you want

    4k Topics
    23k Posts
    barisB

    Do we start the NodeBB processes on the machine 2 and have the same redis server in the config so the processes can communicate?

    Yes

    Do we set isCluster to true?

    You don't have to set isCluster: true since you are running more than one process on each machine, nodebb will detect it automatically. You should set jobsDisabled: true on machine 2 so it doesn't run digests and other cronjobs.

    How do we make a MongoDB replica? Do we add the IPs of both mongo instances in the config file of nodebb on both machines?

    You can use the mongo:uri property to define the mongodb replicaset.

  • Stay tuned here to hear more about new releases and features of NodeBB!

    4k Topics
    22k Posts
    sameer aroraS

    No in this feature we wish to post comments / message to user profiles. everyone can do that. for example wishing a user happy birthday on there profile.

  • Discussion regarding NodeBB Plugin development.

    2k Topics
    15k Posts
    sameer aroraS

    This no more works on latest nodebb forums. any alternates for it?

  • A public listing of community themes created by the NodeBB community.
    49 Topics
    1k Posts
    Chad AugurC

    @baris TY. Despite having been a JS developer for more than 10years I had never published my own npm package. Now I have. TY.

  • Need help with installing or configuring NodeBB? Look here.

    5k Topics
    26k Posts
    X

    node app.js continues try to start app. look at this log:

    2024-04-26T13:32:14.000Z [50341/8042] - info: [api] Adding 0 route(s) to `api/v3/plugins` 2024-04-26T13:32:14.019Z [50341/8042] - info: [router] Routes added 2024-04-26T13:32:14.025Z [50341/8042] - info: 🎉 NodeBB Ready 2024-04-26T13:32:14.027Z [50341/8042] - info: 🤝 Enabling 'trust proxy' 2024-04-26T13:32:14.029Z [50341/8042] - error: NodeBB address in use, exiting... Error: listen EADDRINUSE: address already in use 0.0.0.0:50341 at Server.setupListenHandle [as _listen2] (node:net:1817:16) at listenInCluster (node:net:1865:12) at doListen (node:net:2014:7) at process.processTicksAndRejections (node:internal/process/task_queues:83:21) 2024-04-26T13:32:14.032Z [50341/8042] - error: uncaughtException: listen EADDRINUSE: address already in use 0.0.0.0:50341 Error: listen EADDRINUSE: address already in use 0.0.0.0:50341 at Server.setupListenHandle [as _listen2] (node:net:1817:16) at listenInCluster (node:net:1865:12) at doListen (node:net:2014:7) at process.processTicksAndRejections (node:internal/process/task_queues:83:21) {"date":"Fri Apr 26 2024 13:32:14 GMT+0000 (Coordinated Universal Time)","error":{"address":"0.0.0.0","code":"EADDRINUSE","errno":-98,"port":50341,"syscall":"listen"},"exception":true,"os":{"loadavg":[2.13,1.47,0.75],"uptime":2577.37},"process":{"argv":["/usr/bin/node","/home/vWbHoQZUBwUMl3tH/testn8n/public_html/app.js"],"cwd":"/home/vWbHoQZUBwUMl3tH/testn8n/public_html","execPath":"/usr/bin/node","gid":1003,"memoryUsage":{"arrayBuffers":19144223,"external":21614654,"heapTotal":84533248,"heapUsed":70672856,"rss":160268288},"pid":8042,"uid":1001,"version":"v18.20.2"},"stack":"Error: listen EADDRINUSE: address already in use 0.0.0.0:50341\n at Server.setupListenHandle [as _listen2] (node:net:1817:16)\n at listenInCluster (node:net:1865:12)\n at doListen (node:net:2014:7)\n at process.processTicksAndRejections (node:internal/process/task_queues:83:21)","trace":[{"column":16,"file":"node:net","function":"Server.setupListenHandle [as _listen2]","line":1817,"method":"setupListenHandle [as _listen2]","native":false},{"column":12,"file":"node:net","function":"listenInCluster","line":1865,"method":null,"native":false},{"column":7,"file":"node:net","function":"doListen","line":2014,"method":null,"native":false},{"column":21,"file":"node:internal/process/task_queues","function":"process.processTicksAndRejections","line":83,"method":"processTicksAndRejections","native":false}]} 2024-04-26T13:32:14.034Z [50341/8042] - error: Error: listen EADDRINUSE: address already in use 0.0.0.0:50341 at Server.setupListenHandle [as _listen2] (node:net:1817:16) at listenInCluster (node:net:1865:12) at doListen (node:net:2014:7) at process.processTicksAndRejections (node:internal/process/task_queues:83:21) 2024-04-26T13:32:14.035Z [50341/8042] - info: [app] Shutdown (SIGTERM/SIGINT/SIGQUIT) Initialised. 2024-04-26T13:32:14.036Z [50341/8042] - error: Error [ERR_SERVER_NOT_RUNNING]: Server is not running. at new NodeError (node:internal/errors:405:5) at Server.close (node:net:2161:12) at Object.onceWrapper (node:events:631:28) at Server.emit (node:events:529:35) at emitCloseNT (node:net:2221:8) at process.processTicksAndRejections (node:internal/process/task_queues:81:21) 2024-04-26T13:32:14.361Z [50341/8073] - info: Initializing NodeBB vN/A http://localhost:50341 2024-04-26T13:32:16.071Z [50341/8073] - info: [socket.io] Restricting access to origin: http://localhost:* 2024-04-26T13:32:16.240Z [50341/8073] - warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb reset -p PLUGINNAME` to disable it. * nodebb-plugin-composer-default * nodebb-theme-harmony * nodebb-plugin-markdown * nodebb-plugin-mentions * nodebb-widget-essentials * nodebb-rewards-essentials * nodebb-plugin-emoji * nodebb-plugin-emoji-android 2024-04-26T13:32:16.316Z [50341/8073] - info: [api] Adding 0 route(s) to `api/v3/plugins` 2024-04-26T13:32:16.350Z [50341/8073] - info: [router] Routes added 2024-04-26T13:32:16.366Z [50341/8073] - info: 🎉 NodeBB Ready 2024-04-26T13:32:16.368Z [50341/8073] - info: 🤝 Enabling 'trust proxy' 2024-04-26T13:32:16.371Z [50341/8073] - error: NodeBB address in use, exiting... Error: listen EADDRINUSE: address already in use 0.0.0.0:50341 at Server.setupListenHandle [as _listen2] (node:net:1817:16) at listenInCluster (node:net:1865:12) at doListen (node:net:2014:7) at process.processTicksAndRejections (node:internal/process/task_queues:83:21) 2024-04-26T13:32:16.378Z [50341/8073] - error: uncaughtException: listen EADDRINUSE: address already in use 0.0.0.0:50341 Error: listen EADDRINUSE: address already in use 0.0.0.0:50341 at Server.setupListenHandle [as _listen2] (node:net:1817:16) at listenInCluster (node:net:1865:12) at doListen (node:net:2014:7) at process.processTicksAndRejections (node:internal/process/task_queues:83:21) {"date":"Fri Apr 26 2024 13:32:16 GMT+0000 (Coordinated Universal Time)","error":{"address":"0.0.0.0","code":"EADDRINUSE","errno":-98,"port":50341,"syscall":"listen"},"exception":true,"os":{"loadavg":[2.13,1.47,0.75],"uptime":2579.71},"process":{"argv":["/usr/bin/node","/home/vWbHoQZUBwUMl3tH/testn8n/public_html/app.js"],"cwd":"/home/vWbHoQZUBwUMl3tH/testn8n/public_html","execPath":"/usr/bin/node","gid":1003,"memoryUsage":{"arrayBuffers":19144239,"external":21614670,"heapTotal":85057536,"heapUsed":70311760,"rss":161042432},"pid":8073,"uid":1001,"version":"v18.20.2"},"stack":"Error: listen EADDRINUSE: address already in use 0.0.0.0:50341\n at Server.setupListenHandle [as _listen2] (node:net:1817:16)\n at listenInCluster (node:net:1865:12)\n at doListen (node:net:2014:7)\n at process.processTicksAndRejections (node:internal/process/task_queues:83:21)","trace":[{"column":16,"file":"node:net","function":"Server.setupListenHandle [as _listen2]","line":1817,"method":"setupListenHandle [as _listen2]","native":false},{"column":12,"file":"node:net","function":"listenInCluster","line":1865,"method":null,"native":false},{"column":7,"file":"node:net","function":"doListen","line":2014,"method":null,"native":false},{"column":21,"file":"node:internal/process/task_queues","function":"process.processTicksAndRejections","line":83,"method":"processTicksAndRejections","native":false}]} 2024-04-26T13:32:16.385Z [50341/8073] - error: Error: listen EADDRINUSE: address already in use 0.0.0.0:50341 at Server.setupListenHandle [as _listen2] (node:net:1817:16) at listenInCluster (node:net:1865:12) at doListen (node:net:2014:7) at process.processTicksAndRejections (node:internal/process/task_queues:83:21) 2024-04-26T13:32:16.386Z [50341/8073] - info: [app] Shutdown (SIGTERM/SIGINT/SIGQUIT) Initialised. 2024-04-26T13:32:16.391Z [50341/8073] - error: Error [ERR_SERVER_NOT_RUNNING]: Server is not running. at new NodeError (node:internal/errors:405:5) at Server.close (node:net:2161:12) at Object.onceWrapper (node:events:631:28) at Server.emit (node:events:529:35) at emitCloseNT (node:net:2221:8) at process.processTicksAndRejections (node:internal/process/task_queues:81:21) 2024-04-26T13:32:16.705Z [50341/8102] - info: Initializing NodeBB vN/A http://localhost:50341

Online Users

TaLocheT crazycellsC phenomlabP