Apps stuck on “starting…”
Error wating for port: “The address ‘App_web_1’ cannot be found”
Here is the log for one app as an example:
ride-the-lightning
ride-the-lightning-app_proxy-1 | Error wating for port: “The address ‘ride-the-lightning_web_1’ cannot be found”
ride-the-lightning-app_proxy-1 | Retrying…
ride-the-lightning-app_proxy-1 | Error wating for port: “The address ‘ride-the-lightning_web_1’ cannot be found”
ride-the-lightning-app_proxy-1 | Retrying…
ride-the-lightning-app_proxy-1 | Error wating for port: “The address ‘ride-the-lightning_web_1’ cannot be found”
ride-the-lightning-app_proxy-1 | Retrying…
ride-the-lightning-app_proxy-1 | Error wating for port: “The address ‘ride-the-lightning_web_1’ cannot be found”
ride-the-lightning-app_proxy-1 | Retrying…
ride-the-lightning-app_proxy-1 | Error wating for port: “The address ‘ride-the-lightning_web_1’ cannot be found”
ride-the-lightning-app_proxy-1 | Retrying…
ride-the-lightning-web-1 | [9/29/2023, 1:11:00 PM] INFO: RTL => Server is up and running, please open the UI at http://localhost:3001 or your proxy configured url.
ride-the-lightning-web-1 |
ride-the-lightning-boltz-1 | INFO : 2023/09/29 13:11:04 Recovering pending Reverse Swaps
ride-the-lightning-boltz-1 | WARN : 2023/09/29 13:11:04 Could not find TLS certificate or key
ride-the-lightning-boltz-1 | INFO : 2023/09/29 13:11:04 Generating new TLS certificate and key
ride-the-lightning-boltz-1 | INFO : 2023/09/29 13:11:04 Connected to LND block epoch stream
ride-the-lightning-boltz-1 | INFO : 2023/09/29 13:11:04 Loaded TLS certificate and key
ride-the-lightning-boltz-1 | INFO : 2023/09/29 13:11:04 Enabling Macaroon authentication
ride-the-lightning-boltz-1 | WARN : 2023/09/29 13:11:04 Could not find Macaroons
ride-the-lightning-boltz-1 | INFO : 2023/09/29 13:11:04 Generating new Macaroons
ride-the-lightning-boltz-1 | INFO : 2023/09/29 13:11:04 Starting REST server on: 0.0.0.0:9003
ride-the-lightning-boltz-1 | INFO : 2023/09/29 13:11:04 Starting RPC server on: 127.0.0.1:9002
I have seen a few entries like this and tried all but no luck.
This started after a maintenance upgrade to the OS Debian 11 to Debian 12
Any help and ideas would be great.