I'm encountering an issue on aaPanel where, after stopping or restarting a Node project, the panel shows the project as "Stopped." However, in reality, the process continues running in the background, and it even listens on the designated port. Evidence: Process Check : When running ps aux | grep node , it shows that the Node project process is still active: www 87872 0.0 2.8 21685856 52592 ? Sl Oct21 0:30 node .output/server/index.mjs if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Port Check : Using netstat -tuln | grep 3000 , I confirmed that the project is still listening on port 3000: tcp6 0 0 :::3000 :::* LISTEN if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Due to this issue, it is impossible to restart the project manually within the panel, as aaPanel incorrectly shows it as stopped. The only way to fully stop and restart the project is by rebooting the server. This issue was observed in version 7.0.10 and persists in 7.0.11. Has anyone else experienced this bug, or is there a workaround? Thank you!

[Bug] Node Project Shows as Stopped, But Process Still Running

aaP_style0092

I'm encountering an issue on aaPanel where, after stopping or restarting a Node project, the panel shows the project as "Stopped." However, in reality, the process continues running in the background, and it even listens on the designated port.

Evidence:

Process Check: When running ps aux | grep node, it shows that the Node project process is still active:

   www        87872  0.0  2.8 21685856 52592 ?      Sl   Oct21   0:30 node .output/server/index.mjs

Port Check: Using netstat -tuln | grep 3000, I confirmed that the project is still listening on port 3000:

   tcp6       0      0 :::3000                 :::*                    LISTEN

Due to this issue, it is impossible to restart the project manually within the panel, as aaPanel incorrectly shows it as stopped. The only way to fully stop and restart the project is by rebooting the server.

This issue was observed in version 7.0.10 and persists in 7.0.11.

Has anyone else experienced this bug, or is there a workaround?

Thank you!

aaPanel_Kern

Hello, thank you for your feedback, this is a known issue
It is recommended that you kill the relevant processes manually first, or use Supervisor to manage the processes

aaP_style0092

aaPanel_Kern

Thank you for your response. I'll be waiting for the fix, as this bug is particularly inconvenient in scenarios where we need to build and restart the project using GitHub Actions. In the meantime, I'll implement a workaround while awaiting the update.