[Windows] nginx does not stop after Ctrl+C

[horvoje@…]

After latest Windows 11 update (22H2), nginx won't stop after pressing Ctrl+C.
If I close command prompt window, nginx continues to run as a background process.
Tried with Windows Command Prompt and also with Git Bash Shell.
Tried with nginx versions 1.21.6 and 1.23.1

[Maxim Dounin]

Could you please clarify nginx configuration you are using?

With ​daemon on; (the default), nginx starts as a daemon, so it detaches from the console and cannot be stopped by pressing Ctrl-C and/or closing the terminal window. To avoid confusion, it might be a good idea to start it with start nginx, so there will be no window from the start, see ​here. To stop running nginx instance, use nginx -s stop.

With daemon off; nginx listens for console events and should stop on Ctrl-C just fine, logging something like Ctrl-C pressed, exiting at the "notice" level. Are you seeing issues with daemon off; on Windows 11?

(Note well that MinGW/MSYS shell might incorrectly kill nginx master process on Ctrl-C, see ​here. It is generally a good idea to test from the native terminal instead.)

[horvoje@…]

I'm using nginx in Windows so I'm not sure what would be 'natural terminal' in Windows.
So far I found two options to start it as a process, not a service: a) from Windows Command Prompt and b) from Git Bash shell.
Both options are working the same way with only difference that Git Bash shell pops up a alert (please see attachment in original post) about processes running when I click close icon on shell window.

Regarding nginx installation and configuration, I did it many months ago and it was working fine without even knowing about daemon option.
My wish is to use it as a process from command prompt / shell to be able to start it only when needed. If I install it as a Windows serivce, then things get complicated for me. I cannot say it can't be done but for sure starting it as a process from command line is far better in my case.

Regarding 'daemon on' and 'daemon off' - I never did that kind of configurataion and if "on" is a default value, then there was a mystery on my computer because Ctrl+C was stopping it until last Windows update.

Here is the script I used to use to start it and it's the same many months, no changes applied ever. The script is called from Git Bash shell:

File: run-nginx-windows.sh

echo Starting nginx...
echo e:/app/nginx
echo Press Ctrl+C for abort
cd /e/app/nginx
./nginx.exe

Today I changed my script and added 'daemon off' directive and now it's possible to stop it with Ctrl+C;

./nginx -g 'daemon off;'

To be honest, I don't know what happened but I know nothing changed in my dev environment except already mentioned Windows update.
Prior to this update I was able to stop it without having 'daemon off' in start script.

Thanks a lot for your info!

P.S. At the production level I'm using Ubuntu LTS and, of course, nginx is installed as a service.

[Maxim Dounin]

Replying to horvoje@…:

I'm using nginx in Windows so I'm not sure what would be 'natural terminal' in Windows.
So far I found two options to start it as a process, not a service: a) from Windows Command Prompt and b) from Git Bash shell.
Both options are working the same way with only difference that Git Bash shell pops up a alert (please see attachment in original post) about processes running when I click close icon on shell window.

By native terminal on Windows I of course mean "Command Prompt", cmd.exe.

With daemon on;, it is not expected to be possible to stop nginx with Ctrl-C. If this previously worked for you, most likely it's because your shell handled it for you somehow. It is certainly not possible with native command prompt, cmd.exe, at least with Windows 10 21H1.

Either way, thanks for the details. As previously suggested, if you want to be able to stop nginx with Ctrl-C, using daemon off; is the proper way to go. Alternatively, you can use nginx -s stop to stop nginx if it's started as a daemon.