Environment:
Servy 2025, latest Servy, nginx.exe
Issue:
When restarting or stopping a service in Servy that runs nginx, only one of the nginx processes is terminated. The remaining nginx process stays running, causing orphaned master/worker processes.
Steps to reproduce:
-
Start nginx via Servy
-
Restart or stop the service in Servy
-
Check processes:
Expected behavior:
All nginx processes (master + workers) should be fully terminated on stop/restart.
Actual behavior:
One nginx process remains running after stop/restart, requiring manual termination.
Impact:
- Orphan nginx process continues running
- Port 443 may stay bound
- New nginx instance may not fully apply updated config
- Leads to inconsistent routing/reverse proxy behavior
Workaround:
Manually kill remaining process:
Environment:
Servy 2025, latest Servy, nginx.exe
Issue:
When restarting or stopping a service in Servy that runs nginx, only one of the nginx processes is terminated. The remaining nginx process stays running, causing orphaned master/worker processes.
Steps to reproduce:
Start nginx via Servy
Restart or stop the service in Servy
Check processes:
Expected behavior:
All nginx processes (master + workers) should be fully terminated on stop/restart.
Actual behavior:
One nginx process remains running after stop/restart, requiring manual termination.
Impact:
Workaround:
Manually kill remaining process: