That would depend upon what you are using to start node-red, so the log directory should be configured in NSSM somewhere. But at this point I would remove NSSM and set up a Scheduled Task like Julian suggested. There you can also see the output directory, task run history, and log entries (if i recall correctly).
I think log output may depend on how/when you are starting the task. If you start manually, you will see the console which contains the log. You will most likely want to dump the log to a file. To do that, you need to create a wrapper cmd or powershell script and redirect the output. You might also want to improve that file by putting in log rotation logic.
PM2 will do all that for you of course.
@dedynobre,
I pulled my hair out for the same problem....
You need to use the -u argument in the AppParameters
nssm set Node-RED AppParameters "-u c:\Users\\"%USERNAME%"\.node-red > c:\temp\node-red.log"
Thank you.
Now, is running correctly.
Very good.
1 Like
That's odd -- if you don't specify the -u xxx option, it should use the current working dir, which is the same Startup directory...
If that didn't work, then I would also try -u . to force it to use the current dir -- that would avoid all the USERNAME substitution stuff.
On my system it referenced C:\Windows\System32\config\systemprofile.node-red
