# No debug output in side-bar. Tried lots, stuck, please help

**URL:** <https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418>\
**Category:** General\
**Created:** [20 June 2019 07:18 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418 "2019-06-20T07:18:20Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![EnigmaHQ](https://avatars.discourse-cdn.com/v4/letter/e/bc8723/32.png) [@EnigmaHQ](https://discourse.nodered.org/u/EnigmaHQ)\
**Post date:** [30 June 2019 06:14 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/41 "2019-06-30T06:14:12Z")

</div>

> [@Steve-Mcl](#):
>
> Have you tried other browsers? **Tried on Firefox - same issue.**  
> Have you tried running node-red on another machine? **No.**  
> Is there a firewall between your browser and the node-red installation? **No.**  
> Is this a corporate environment (with all the crappy policies in place that just make a devs life harder) or personal machine(s)? **Personal Machine**
> 
> Also, please state the nodejs version and the OS where node-red is installed / running. **Windows and I don't which node.js it is.**

**Clicked inject before screenshot.**

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [30 June 2019 07:18 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/42 "2019-06-30T07:18:08Z")

</div>

What have you tried yourself or are you just waiting for input here ?

`node -v`  
`npm -v`

How did you install node-red ?

---

<div class="post-metadata">

**Author:** ![EnigmaHQ](https://avatars.discourse-cdn.com/v4/letter/e/bc8723/32.png) [@EnigmaHQ](https://discourse.nodered.org/u/EnigmaHQ)\
**Post date:** [30 June 2019 07:24 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/43 "2019-06-30T07:24:17Z")

</div>

v10.16.0  
6.9.0

Installed it using " ```  
npm install -g --unsafe-perm node-red

```auto

```

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [30 June 2019 07:25 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/44 "2019-06-30T07:25:41Z")

</div>

> [@EnigmaHQ](#):
>
> 6.9.0

There is your problem. Upgrade npm.

---

<div class="post-metadata">

**Author:** ![EnigmaHQ](https://avatars.discourse-cdn.com/v4/letter/e/bc8723/32.png) [@EnigmaHQ](https://discourse.nodered.org/u/EnigmaHQ)\
**Post date:** [30 June 2019 07:32 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/45 "2019-06-30T07:32:38Z")

</div>

I downloaded [node-v10.16.0-x64.msi](https://nodejs.org/dist/v10.16.0/node-v10.16.0-x64.msi) and installed it - npm - v still shows 6.9.0

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [30 June 2019 07:36 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/46 "2019-06-30T07:36:28Z")

</div>

node is not npm.

[Did you google](https://www.npmjs.com/package/npm-windows-upgrade) how to update npm ?

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [30 June 2019 07:39 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/47 "2019-06-30T07:39:37Z")

</div>

@bakman2 the version of npm is fine. That is not the problem.

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [30 June 2019 07:41 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/48 "2019-06-30T07:41:20Z")

</div>

shoot you're right, i misread 6.0 😕

---

<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:** [30 June 2019 07:53 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/49 "2019-06-30T07:53:05Z")

</div>

Hmmmm.  
Nothing out of the ordinary.

Only thing I can suggest is re-run the node-red install from an elevated CMD prompt.

---

<div class="post-metadata">

**Author:** ![EnigmaHQ](https://avatars.discourse-cdn.com/v4/letter/e/bc8723/32.png) [@EnigmaHQ](https://discourse.nodered.org/u/EnigmaHQ)\
**Post date:** [30 June 2019 09:22 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/50 "2019-06-30T09:22:51Z")

</div>

Tried it. No luck.

---

<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:** [30 June 2019 09:34 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/51 "2019-06-30T09:34:07Z")

</div>

What URL do you use?

Have you tried

- [http://localhost:1880](http://localhost:1880)
- [http://127.0.0.1:1880](http://127.0.0.1:1880)
- [http://computerIP:1880](http://computerIP:1880)
- [http://computerName:1880](http://computerName:1880)

Ps, at a `cmd` prompt....

- you will get computer IP from `ipconfig`
- You will get computer name from `set`

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [30 June 2019 13:46 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/52 "2019-06-30T13:46:06Z")

</div>

Can this be caused by a websockets issue? OK on http but not on websockets.

---

<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:** [30 June 2019 21:16 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/53 "2019-06-30T21:16:50Z")

</div>

I've seen this problem long time ago but can't for the life of me remember what I did. I do suspect its to do with web sockets & that's why I wanted to see devtools console.

Not sure what in Windows will be blocking? I'm unfamiliar with how web sockets work. I guess it's TCP? And a specific port? Perhaps it's firewall related?

@EnigmaHQ could you temporarily turn off the windows firewall (or Norton or whatever firewall you have installed) and try once more?

---

<div class="post-metadata">

**Author:** ![EnigmaHQ](https://avatars.discourse-cdn.com/v4/letter/e/bc8723/32.png) [@EnigmaHQ](https://discourse.nodered.org/u/EnigmaHQ)\
**Post date:** [30 June 2019 23:09 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/54 "2019-06-30T23:09:47Z")

</div>

Tried all the above urls and turning off firewall. No avail.

---

<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:** [1 July 2019 08:53 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/55 "2019-07-01T08:53:53Z")

</div>

Stumped.  
2 last options...

1. If you can find out what port the websockets run on, perhaps you have an application or service running that blocks or uses that port? Using netstat or other tools to list open ports you might be able to find it and close the offending application.

2. Last ditch attempt... You ain't gonna like it... But it will work...  
2a. Reinstall windows  
Or  
2b. Move to Linux

I can tell you this much, I've ran node-red on about 6 different windows versions from 7 ~ server 2019 and 3 flavours of linux. None have had this issue. My money is on something external like AV / firewall / other application.

Good luck.

---

<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:** [1 July 2019 08:56 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/56 "2019-07-01T08:56:41Z")

</div>

Can I suggest you you change the title of this to ....  
"No debug output in side-bar. Tried lots, stuck, please help"

It will draw the attention of more capable forum members. (Better than newbie question which suggests it's a silly coding thing)

---

<div class="post-metadata">

**Author:** ![kabonker](https://avatars.discourse-cdn.com/v4/letter/k/85f322/32.png) [@kabonker](https://discourse.nodered.org/u/kabonker)\
**Post date:** [1 November 2019 15:55 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/57 "2019-11-01T15:55:33Z")

</div>

same issue. Debug side window just stopped working even for the simple hello world?

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [1 November 2019 16:10 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/58 "2019-11-01T16:10:12Z")

</div>

Without details of your environment, it would be difficult for anyone to offer any advice.

Where are you running node-red?  
What versions of node-red and nodejs

What browser?  
Are there any errors in the console of the browser?

---

<div class="post-metadata">

**Author:** ![kabonker](https://avatars.discourse-cdn.com/v4/letter/k/85f322/32.png) [@kabonker](https://discourse.nodered.org/u/kabonker)\
**Post date:** [1 November 2019 16:28 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/59 "2019-11-01T16:28:28Z")

</div>

I am running Node Red via the IBM Cloud. I am just using the Firefox Browser latest release. The failures have been intermittent today. I just do hello world and nothing, nothing, nothing. Then I try to refresh close the browser re open about 5 xs and then it works for a bit, then stops. It is like a failure in the general service around debug... I have not seen this issue until today.

---

<div class="post-metadata">

**Author:** ![kabonker](https://avatars.discourse-cdn.com/v4/letter/k/85f322/32.png) [@kabonker](https://discourse.nodered.org/u/kabonker)\
**Post date:** [1 November 2019 16:29 UTC](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418/60 "2019-11-01T16:29:08Z")

</div>

70.0.1 (64-bit) Firefox version

[Previous page](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418.md?page=2)

[Next page](https://discourse.nodered.org/t/no-debug-output-in-side-bar-tried-lots-stuck-please-help/12418.md?page=4)