# Tracking Node-Red issues in Windows

**URL:** <https://discourse.nodered.org/t/tracking-node-red-issues-in-windows/26047>\
**Category:** General\
**Created:** [4 May 2020 07:35 UTC](https://discourse.nodered.org/t/tracking-node-red-issues-in-windows/26047 "2020-05-04T07:35:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nygma2004](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nygma2004/32/1308_2.png) [@nygma2004](https://discourse.nodered.org/u/nygma2004)\
**Post date:** [4 May 2020 07:35 UTC](https://discourse.nodered.org/t/tracking-node-red-issues-in-windows/26047/1 "2020-05-04T07:35:57Z")

</div>

Hi Experts,

I am running Node-Red in Windows. I followed the guide of installing and setting up the Task Scheduler and all seemed to have worked. But I noticed that after some time the server is just not working. I had to got to Task Scheduler, stop the task and start again. But it would keep stopping.  
On the raspberry I used to look into /var/log to see logs, but I am not sure where to look in Windows. I tried looking around in Event Viewer but could not find anything.

Today, I logged onto the server and was running NR in the a command prompt and looking the screen messages whilst working on my flow. All looks fine, but now I press inject on my flow and Node-Red just stops. The server exits and I get back to the prompt in the Command Prompt on the server. There are no errors on the screen.

How can I view the logs in Windows? Or there is no default logging like there is in Linux?

Best Regards,  
Csongor

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [4 May 2020 08:46 UTC](https://discourse.nodered.org/t/tracking-node-red-issues-in-windows/26047/2 "2020-05-04T08:46:01Z")

</div>

You can redirect to a file

E.g. `node-red > nr.log`

Normally, on windows, I run node-red as a service (using nssm search this forum for nssm for more info)

But when I have an issue, I open a CMD window then run node-red. This way, if it crashes the CMD window stays open

Ps, it's likely you have a loop or bad node (i.e. it's not crashing till you inject & a msg starts traveling).

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [4 May 2020 16:43 UTC](https://discourse.nodered.org/t/tracking-node-red-issues-in-windows/26047/3 "2020-05-04T16:43:55Z")

</div>

Agreed though I tend to use pm2 or nodemon to run a development version of NR on Windows just because it helps manage things.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [3 July 2020 16:43 UTC](https://discourse.nodered.org/t/tracking-node-red-issues-in-windows/26047/4 "2020-07-03T16:43:55Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.