xiyohag273
Posts
-
Basic Authentication (Nginx) on NodeBB -
Basic Authentication (Nginx) on NodeBBHave you ever set up Basic Authentication on NodeBB?
I'm talking about basic authentication provided by the web server itself.
I implemented that basic authentication but when I try to login it's always says "We were unable to log you in, likely due to an expired session. Please try again".
How can I solve it?
-
What is Best Option for Running Nodebb forever?node app.js
continues try to start app. look at this log:2024-04-26T13:32:14.000Z [50341/8042] - [32minfo[39m: [api] Adding 0 route(s) to `api/v3/plugins` 2024-04-26T13:32:14.019Z [50341/8042] - [32minfo[39m: [router] Routes added 2024-04-26T13:32:14.025Z [50341/8042] - [32minfo[39m: 🎉 NodeBB Ready 2024-04-26T13:32:14.027Z [50341/8042] - [32minfo[39m: 🤝 Enabling 'trust proxy' 2024-04-26T13:32:14.029Z [50341/8042] - [31merror[39m: 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] - [31merror[39m: 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] - [31merror[39m: 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] - [32minfo[39m: [app] Shutdown (SIGTERM/SIGINT/SIGQUIT) Initialised. 2024-04-26T13:32:14.036Z [50341/8042] - [31merror[39m: 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] - [32minfo[39m: Initializing NodeBB vN/A http://localhost:50341 2024-04-26T13:32:16.071Z [50341/8073] - [32minfo[39m: [socket.io] Restricting access to origin: http://localhost:* 2024-04-26T13:32:16.240Z [50341/8073] - [33mwarn[39m: [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] - [32minfo[39m: [api] Adding 0 route(s) to `api/v3/plugins` 2024-04-26T13:32:16.350Z [50341/8073] - [32minfo[39m: [router] Routes added 2024-04-26T13:32:16.366Z [50341/8073] - [32minfo[39m: 🎉 NodeBB Ready 2024-04-26T13:32:16.368Z [50341/8073] - [32minfo[39m: 🤝 Enabling 'trust proxy' 2024-04-26T13:32:16.371Z [50341/8073] - [31merror[39m: 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] - [31merror[39m: 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] - [31merror[39m: 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] - [32minfo[39m: [app] Shutdown (SIGTERM/SIGINT/SIGQUIT) Initialised. 2024-04-26T13:32:16.391Z [50341/8073] - [31merror[39m: 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] - [32minfo[39m: Initializing NodeBB vN/A http://localhost:50341
-
What is Best Option for Running Nodebb forever?I think its good to go with Systemd.
-
What is Best Option for Running Nodebb forever?I was use
./nodebb start
to pm2. -
What is Best Option for Running Nodebb forever?But with systemd it's working fine i think.
-
What is Best Option for Running Nodebb forever?When i'm using PM2 its continue try to starting app that server load going high.
-
What is Best Option for Running Nodebb forever?What is Best Option for Running Nodebb forever?
- PM2
- Systemd
-
Give Example of config.json for Setup Nodebbthanks @nhl.pl for your help brother!
-
Give Example of config.json for Setup Nodebb{ "url": "http://localhost:4571", "secret": "27b3b80b-5bcb-4bcb-bd81-da24bbfd7bsddaa", "database": "mongo", "mongo:host": "127.0.0.1", "mongo:port": "27017", "mongo:username": "2olpE5MZDNxRVBUO", "mongo:password": "4zuwX94UIX78UxFY", "mongo:database": "nodebb5", "port": "4571", "admin:username": "nodebb3", "admin:password": "qswaefrd", "admin:password:confirm": "qswaefrd", "admin:email": "[email protected]" }
Its working with this config.
-
Give Example of config.json for Setup NodebbSometime i got "command createIndexes requires authentication" even I'm passing correct credentials.
-
Give Example of config.json for Setup NodebbI found a solution.
Its working with this command:
./nodebb setup '{ "url": "http://localhost:4568", "secret": "27b3b80b-5bcb-4bcb-bd81-da24bbfd7bzz", "database": "mongo", "mongo": { "host": "127.0.0.1", "port": "27017", "username": "bXSJ3bA23V9uX7ZD", "password": "3qQ5NRsxwaHk8DIt", "database": "nodebb2", "uri": "" }, "port": "4568", "admin:username": "admin", "admin:password": "qswaefrd", "admin:password:confirm": "qswaefrd", "admin:email": "[email protected]" }'
-
Give Example of config.json for Setup Nodebb2024-04-17T07:09:34.846Z [85865] - info: [install/checkSetupFlagEnv] checking env vars for setup info...
2024-04-17T07:09:34.847Z [85865] - error: [install/checkSetupFlagEnv] required values are missing for automated setup:
2024-04-17T07:09:34.847Z [85865] - error: admin:username
2024-04-17T07:09:34.848Z [85865] - error: admin:password
2024-04-17T07:09:34.848Z [85865] - error: admin:password:confirm
2024-04-17T07:09:34.848Z [85865] - error: admin:email -
Give Example of config.json for Setup NodebbThen how can i create automated script that's deploy NodeBB in Single Click?
-
Give Example of config.json for Setup Nodebb{ "url": "http://localhost:4568", "secret": "27b3b80b-5bcb-4bcb-bd81-da24bbfd7bzz", "database": "mongo", "mongo": { "host": "127.0.0.1", "port": "27017", "username": "BX5x92b9Di5UdhUz", "password": "cuqppzQXMiDOV6uE", "database": "nodebb", "uri": "" }, "port": "4568" }
How can i define admin credentials into config.json?
-
Give Example of config.json for Setup Nodebbi want to setup nodebb via config.json
-
Give Example of config.json for Setup NodebbBut there is a no example for admin configuration like username password email
-
Give Example of config.json for Setup NodebbI'm going to setup automated Nodebb on Different Server. I need example of config.json.