curl result is similar to Nginx
$ curl localhost:8081
Cannot GET /
Connection refused error that I have posted before, from Nginx Error logs.
Considering the situation, currently, I'm not messing with dependencies or configs that would work without any issues. I did not touch NPM Modules, did not try to remap port.
By the way,
curl localhost:8081 for NodeBB that I run in Dev mode
./nodebb dev returns HTML, i.e. forum functions
What so special happens with the production start of the NodeBB that could stop working in such a fashion?
@omega interesting theory, I will see if any suspicious users were created last couple of days. But I'm the only admin.
@PitaJ thank you for brainstorming the potential issues. Here are full logs from NodeBB Start:
NodeBB v1.0.2 Copyright (C) 2013-2014 NodeBB Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it under certain conditions.
For the full license, please visit: http://www.gnu.org/copyleft/gpl.html
Clustering enabled: Spinning up 1 process(es).
3/3 23:36  - info: Time: Wed Mar 03 2021 23:36:57 GMT+0000 (UTC)
3/3 23:36  - info: Initializing NodeBB v1.0.2
3/3 23:36  - info: [database] Checking database indices.
3/3 23:36  - warn: [socket.io] Clustering detected, you are advised to configure Redis as a websocket store.
3/3 23:36  - 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.
3/3 23:37  - info: NodeBB Ready
3/3 23:37  - info: Enabling 'trust proxy'
3/3 23:37  - info: NodeBB is now listening on: 0.0.0.0:8081
Warning for Dev mode is the same, and it works...