Forum not starting

youhosi

NodeJS: v11.6.0
NodeBB: latest (master branch)

After updating the forum and nodejs it stopped working, logs lower.

Logs:

[cluster] Child Process (2717) has exited (code: null, signal: SIGTERM)

NodeBB v1.11.1 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 3 process(es).

2019-01-03T22:02:54.722Z [8000/689] - info: Initializing NodeBB v1.11.1 https://oxidepolska.pl
2019-01-03T22:03:01.367Z [8001/690] - info: [socket.io] Restricting access to origin: https://oxidepolska.pl:*
2019-01-03T22:03:01.374Z [8002/692] - info: [socket.io] Restricting access to origin: https://oxidepolska.pl:*
2019-01-03T22:03:01.375Z [8000/689] - info: [socket.io] Restricting access to origin: https://oxidepolska.pl:*
2019-01-03T22:03:03.115Z [8001/690] - info: [plugins/spam-be-gone] Settings loaded
2019-01-03T22:03:03.118Z [8000/689] - info: [plugins/spam-be-gone] Settings loaded
2019-01-03T22:03:03.153Z [8002/692] - info: [plugins/spam-be-gone] Settings loaded
2019-01-03T22:03:03.245Z [8001/690] - info: Routes added
2019-01-03T22:03:03.246Z [8000/689] - info: Routes added
2019-01-03T22:03:03.252Z [8000/689] - info: NodeBB Ready
2019-01-03T22:03:03.259Z [8001/690] - info: NodeBB Ready
2019-01-03T22:03:03.262Z [8000/689] - info: Enabling 'trust proxy'
2019-01-03T22:03:03.267Z [8000/689] - info: NodeBB is now listening on: 0.0.0.0:8000
2019-01-03T22:03:03.269Z [8001/690] - info: Enabling 'trust proxy'
2019-01-03T22:03:03.275Z [8002/692] - info: Routes added
2019-01-03T22:03:03.278Z [8001/690] - info: NodeBB is now listening on: 0.0.0.0:8001
2019-01-03T22:03:03.285Z [8002/692] - info: NodeBB Ready
2019-01-03T22:03:03.289Z [8002/692] - info: Enabling 'trust proxy'
2019-01-03T22:03:03.292Z [8002/692] - info: NodeBB is now listening on: 0.0.0.0:8002

PitaJ

Try downgrading to Node 10, please

youhosi

Fixed, the problem was on the nginx side;