How to completely kill a node.js process

[y-river]

In the Linux operating system, the Node.js process may not be shut down or killed normally. This is usually related to process management, port occupation and exception handling. When we run a node.js process on a vps with full commands and permissions, we can use the ps and kill commands to find and end them, but in an virtual environment where only allows npm using, we have no way to end it. Even if we use disable node.js to end it, the node.js will still continue to run in the background.

[wolstech]

If you enable Node through Plesk and let Passenger handle it, the server should start it when needed and kill it when it has no traffic. This only works for apps that receive HTTP traffic though. Passenger launches the app when the traffic comes in, and kills it after a period of inactivity.

If you start it manually with npm run start or similar, you have to contact support and ask for your processes to be killed. There is no way to kill a manually started node process, and as a result, our typical recommendation is to never start a node process manually.

We do offer VPS service with full SSH root access if you want total control over the app: https://heliohost.org/vps/ Those start at $4/month and come as an empty linux VM. You'll need to install node and anything else you need.