# Node-RED 0.20.7 released

**URL:** <https://discourse.nodered.org/t/node-red-0-20-7-released/12955>\
**Category:** News\
**Created:** [5 July 2019 14:43 UTC](https://discourse.nodered.org/t/node-red-0-20-7-released/12955 "2019-07-05T14:43:38Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [16 July 2019 13:50 UTC](https://discourse.nodered.org/t/node-red-0-20-7-released/12955/21 "2019-07-16T13:50:43Z")

</div>

Could it be some firewall/security settings that Windows has defaulted to after the upgrade to prevent applications listening on ports they haven't been explicitly allowed to?

---

<div class="post-metadata">

**Author:** ![juzam](https://avatars.discourse-cdn.com/v4/letter/j/839c29/32.png) [@juzam](https://discourse.nodered.org/u/juzam)\
**Post date:** [16 July 2019 14:10 UTC](https://discourse.nodered.org/t/node-red-0-20-7-released/12955/22 "2019-07-16T14:10:11Z")

</div>

I've checked and manually disabled windows firewall for the purpose of a test but no luck. but this command `netsh interface ipv4 show excludedportrange protocol=tcp`  
revealed that port `1880` got included in a list of "reserved" port range:

```auto
Porta iniziale Porta finale
---------- --------
        80 80
      1571 1670
      1671 1770
      1771 1870
      1871 1970
      1971 2070
      2180 2279
      2280 2379
      2380 2479
      2480 2579
      2680 2779
      2780 2879
      3207 3306
      3390 3489
      3545 3644
      5357 5357
      5700 5700
      8884 8884
     19443 19443
     50000 50059 *

```

After changing local port to anything not in those ranges, voilà! Node-Red is happliy running again.  
I still can't figure out what exactly modified that list, but at least NR is ok now.

thanks to everybody who chimed in 🙂

---

<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:** [16 July 2019 19:31 UTC](https://discourse.nodered.org/t/node-red-0-20-7-released/12955/23 "2019-07-16T19:31:23Z")

</div>

OK, there is something odd there - is this a corporate machine?

Here is my response to that command:

```auto
> netsh interface ipv4 show excludedportrange protocol=tcp

Protocol tcp Port Exclusion Ranges

Start Port End Port
---------- --------
        80 80
      5357 5357
     50000 50059 *

* - Administered port exclusions.

```

Rather significantly different - something must have set those exclusions.

---

<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:** [16 July 2019 19:34 UTC](https://discourse.nodered.org/t/node-red-0-20-7-released/12955/24 "2019-07-16T19:34:26Z")

</div>

In fact, try running:

```auto
netsh interface ipv4 show excludedportrange protocol=tcp store=persistent

```

To see whether those are persistent exclusions or not. If not, then something that is running is excluding them. Either some kind of corporate setting or, more likely, some kind of anti-malware tool being rather too intrusive.

---

<div class="post-metadata">

**Author:** ![juzam](https://avatars.discourse-cdn.com/v4/letter/j/839c29/32.png) [@juzam](https://discourse.nodered.org/u/juzam)\
**Post date:** [17 July 2019 06:28 UTC](https://discourse.nodered.org/t/node-red-0-20-7-released/12955/25 "2019-07-17T06:28:28Z")

</div>

It turns out that it was Hyper-V reserving those ports. It got re-installed by the update (I had it disabled prior to that). Manually deselected the feature again and the excludedportrange is sane again 🙂

Thank you!

---

<div class="post-metadata">

**Author:** ![mu3](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mu3/32/4332_2.png) [@mu3](https://discourse.nodered.org/u/mu3)\
**Post date:** [21 July 2019 05:58 UTC](https://discourse.nodered.org/t/node-red-0-20-7-released/12955/26 "2019-07-21T05:58:30Z")

</div>

In my case the problem was with `sessionExpiryTime`:

```
adminAuth: {... sessionExpiryTime: 3*30*24*60*60}

```

Probably, it's calculated in microseconds so I was getting:  
`3*30*24*60*60*1000 > 2147483647`

The problem solved by changing sessionExpiryTime to 20 days and removing the `.sessions.json`

Should we really use 32-bit signed integer for this comparison?

[Previous page](https://discourse.nodered.org/t/node-red-0-20-7-released/12955.md?page=1)