Technical Support

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

FreeBSD your solution!

With the current codebase, making a group hidden also removes it from the badge selection.

Yes, it's working now, not sure why it wasn't earlier but thanks everyone!

You can change it to 5 minutes in the ACP using the online cutoff setting.

Is there a way to enable registration queue but make it so that user's registering with admin invites are able to register bypassing registration queue and admin approval? Since it would only make sense since the admins are the ones who invited the user.

Many thanks!

Quill 2.0 has been released.
https://slab.com/blog/announcing-quill-2-0/

Link Preview Image Announcing Quill 2.0 - Knock Down Silos by Slab

Running weekly updates of every small improvement and bugfix to Slab that miss the headlines.

favicon

(slab.com)

Word that from would bee messed up. Can you try undoing your change and console.loging those values to see what they end up being?

@baris Yes, I test develop branch and it's really worked now. But community still loaded slow and shows from time to time 503 error

@crazycells yes, just like normal topics.

@Renan-Birlem-Deves make sure you're not using some other way to send a config in, otherwise config.json may not be read (or its values overridden).

@baris thanks!

@schwach I have two installations dependent on this image and I am stuck as there are no updates for a while, i wouldn't advise using it.

I'm still looking for an efficient way to setup a docker-compose file that can be used to update with new release (both nodebb and mongodb). I wish updating nodebb was much simpler, i have an old forum started from 1.7, it has been such a pain keeping it up to date because of the need of dependencies.

Found the issue!!

You must use the main account API key and secret and not a subaccount key for everything to work.

Getting emails now through both the Cloudron side and NodeBB

@tchesley85 when creating a category you can always clone the settings (that includes privileges) of an existing category.

Yes, the errors are still there with v3.x.

I even deleted the build/ and node_modules/ directories because I thought there might be outdated files in there. But that didn't help.

However, since the MongoDB schema upgrades were successful during the ./nodebb upgrade runs, I was able to complete the upgrade by doing a fresh git install and copying back the old config.json before running the setup routine. I then manually restored all the static files in public/uploads via rsync.

Not sure how that will be implemented since Tag1 and tag1 would end up being two different tags. Lowercasing solves that problem.

@crazycells Agree - you can have as many or as few as you'd like though.

@julian - Done! Thank you for the quick responses.

Yeah I think having a folder under public/uploads/profile for each user would make deleting easier. We can get rid of the glob and delete that folder on user deletion. But we would have to write an upgrade script to move all files and update the path in the user object since they are stored as "/assets/uploads/profile/1-profileavatar-1709738685611.jpeg"