# NodeRED stop working -- Docker Container - Docker compose (Stack)

**URL:** <https://discourse.nodered.org/t/nodered-stop-working-docker-container-docker-compose-stack/59307>\
**Category:** General\
**Created:** [3 March 2022 12:46 UTC](https://discourse.nodered.org/t/nodered-stop-working-docker-container-docker-compose-stack/59307 "2022-03-03T12:46:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jose](https://avatars.discourse-cdn.com/v4/letter/j/e274bd/32.png) [@jose](https://discourse.nodered.org/u/jose)\
**Post date:** [3 March 2022 12:46 UTC](https://discourse.nodered.org/t/nodered-stop-working-docker-container-docker-compose-stack/59307/1 "2022-03-03T12:46:11Z")

</div>

Hello,

I have NodeRed installed in docker with Docker compose (Stack).

I was configuring a node (MODBUS Flex Server) and then appear the message "Lost connection", waiting for reconnecting.

I stop the container, kill it, remove it... and restart the machine.. but all time is the same.

I paste the bug code, for if someone can help me: CODE:

**Welcome to Node-RED**  
**===================**

**3 Mar 13:23:24 - [info] Node-RED version: v2.2.0**  
**3 Mar 13:23:24 - [info] Node.js version: v14.18.2**  
**3 Mar 13:23:24 - [info] Linux 5.10.16.3-microsoft-standard-WSL2 x64 LE**  
**3 Mar 13:23:24 - [info] Loading palette nodes**  
**3 Mar 13:23:26 - [info] Dashboard version 3.1.6 started at /ui**  
**3 Mar 13:23:26 - [info] Settings file : /data/settings.js**  
**3 Mar 13:23:26 - [info] Context store : 'default' [module=memory]**  
**3 Mar 13:23:26 - [info] User directory : /data**  
**3 Mar 13:23:26 - [warn] Projects disabled : editorTheme.projects.enabled=false**  
**3 Mar 13:23:26 - [info] Flows file : /data/flows.json**  
**3 Mar 13:23:27 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/)**  
\*\*3 Mar 13:23:27 - [warn] \*\*

**---------------------------------------------------------------------**  
**Your flow credentials file is encrypted using a system-generated key.**

**If the system-generated key is lost for any reason, your credentials**  
**file will not be recoverable, you will have to delete it and re-enter**  
**your credentials.**

**You should set your own key using the 'credentialSecret' option in**  
**your settings file. Node-RED will then re-encrypt your credentials**  
**file using your chosen key the next time you deploy a change.**  
**---------------------------------------------------------------------**

**3 Mar 13:23:27 - [info] Starting flows**  
**3 Mar 13:23:27 - [info] [OpcUa-Client:OPC UA Prosys] Local 'own' certificate is NOT used.**  
**3 Mar 13:23:27 - [info] Started flows**  
**3 Mar 13:23:27 - [red] Uncaught Exception:**  
**3 Mar 13:23:27 - [error] Error: listen EADDRNOTAVAIL: address not available 10.19.19.191:11502**  
\*\* at Server.setupListenHandle [as \_listen2] (net.js:1314:21)\*\*  
\*\* at listenInCluster (net.js:1379:12)\*\*  
\*\* at doListen (net.js:1516:7)\*\*  
\*\* at processTicksAndRejections (internal/process/task\_queues.js:83:21)\*\*  
**npm ERR! code ELIFECYCLE**  
**npm ERR! errno 1**  
**npm ERR! node-red-docker@2.2.0 start: `node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"`**  
**npm ERR! Exit status 1**  
\*\* \*\*

* * *

**npm ERR! Failed at the node-red-docker@2.2.0 start script.**  
**npm ERR! This is probably not a problem with npm. There is likely additional logging output above.**

**npm ERR! A complete log of this run can be found in:**  
**npm ERR! /data/.npm/\_logs/2022-03-03T12\_23\_27\_337Z-debug.log**

**\> node-red-docker@2.2.0 start /usr/src/node-red**  
**\> node $NODE\_OPTIONS node\_modules/node-red/red.js $FLOWS "--userDir" "/data"**

**3 Mar 13:24:29 - [info]**

THANKS SO MUCH  
Jose

---

<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:** [2 May 2022 12:46 UTC](https://discourse.nodered.org/t/nodered-stop-working-docker-container-docker-compose-stack/59307/2 "2022-05-02T12:46:12Z")

</div>

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