# Error \[ERR\_STREAM\_DESTROYED\]

**URL:** <https://discourse.nodered.org/t/error-err-stream-destroyed/37276>\
**Category:** General\
**Created:** [9 December 2020 22:07 UTC](https://discourse.nodered.org/t/error-err-stream-destroyed/37276 "2020-12-09T22:07:33Z")\
**Posts on this page:** 1\
**Showing post:** 8

<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:** [10 December 2020 11:39 UTC](https://discourse.nodered.org/t/error-err-stream-destroyed/37276/8 "2020-12-10T11:39:17Z")

</div>

> [@davenrea](#):
>
> Error [ERR\_STREAM\_DESTROYED]

Seems the developers are aware of [this issue](https://github.com/victronenergy/node-red-contrib-victron/issues/45). Seems to me they are not so interested in fixing it as they dont see this problem on thier own OS! I would (if I were you) post a follow up reply in that issue stating you too are having the issue - just to let the developer know the issue still exists & is probably affecting more people than they realise (they may not be aware of how common this is as people tend not to bother reporting issues and generate workarounds - much like yourself)

In the mean time, there are several threads on this forum related to restarting node-red  
[this one](https://discourse.nodered.org/t/restart-flows-using-node-red-api/34632) _MIGHT_ work for you (it restarts your flows via the API - import the last flow under "solution 2" in that link)

---

_[View the full topic](https://discourse.nodered.org/t/error-err-stream-destroyed/37276)._