Lightning terminal Error code: EAI_AGAIN

Upon restarting my node lightning terminal fails to start with the following error:

There was an error connecting to Lightning Terminal. Error code: EAI_AGAIN

I have two questions, If a Loop out was initiated and was stuck in “initiated” state (the reason i restarted node) will the loop fail if so how long before the funds return to either my on chain or lightning balance.

If i uninstall and reinstall lightning terminal upon reinstalling will the previous loop out still be visible or is this state stored on the instance running on the node if this makes sense, im a little worried ive lost some sats here…

after a while the error changed to the following?

There was an error connecting to Lightning Terminal. Error code: ENOTFOUND

Stuck here with the same error ENOTFOUND

I’m dealing with it also, keep having to reinstall it every few weeks, which is a PITA to reconfig everything. Connecting via Onion after a reboot (multiple ones).

Oops, there was an error

There was an error connecting to Lightning Terminal. Error code: ETIMEDOUT

LOGS:
Docker container for lightning terminal keeps restarting:
lightning-terminal_web_1 Restarting (1) 53 seconds ago

lightning-terminal

Attaching to lightning-terminal_web_1, lightning-terminal_tor_server_1, lightning-terminal_app_proxy_1
web_1 | 2023-07-29 23:32:06.081 [INF] LNDC: lnd version: v0.16.4-beta, build tags ‘autopilotrpc,signrpc,walletrpc,chainrpc,invoicesrpc,watchtowerrpc,neutrinorpc,monitoring,peersrpc,kvdb_postgres,kvdb_etcd,kvdb_sqlite’
web_1 | 2023-07-29 23:32:06.085 [INF] LNDC: Using network mainnet
web_1 | 2023-07-29 23:32:06.087 [INF] LNDC: Waiting for lnd to be fully synced to its chain backend, this might take a while
web_1 | 2023-07-29 23:32:06.121 [INF] LNDC: lnd is now fully synced to its chain backend
web_1 | 2023-07-29 23:32:06.372 [INF] LOOPD: Protocol version: MuSig2
web_1 | 2023-07-29 23:32:06.372 [INF] LOOPD: Swap server address: swap.lightning.today:11010
web_1 | 2023-07-29 23:32:06.372 [INF] LOOPD: Opening sqlite3 database at: /data/.loop/mainnet/loop_sqlite.db
web_1 | 2023-07-29 23:32:06.662 [WRN] GRPC: [core] grpc: addrConn.createTransport failed to connect to {swap.lightning.today:11010 swap.lightning.today:11010 0 }. Err: connection error: desc = “transport: Error while dialing dial tcp: lookup swap.lightning.today: operation was canceled”. Reconnecting…
web_1 | 2023-07-29 23:32:06.671 [ERR] LITD: Error starting Lightning Terminal: could not start subservers: unable to start loop in integrated mode: sql: Scan error on column index 20, name “publication_deadline”: unsupported Scan, storing driver.Value type string into type *time.Time
web_1 | could not start subservers: unable to start loop in integrated mode: sql: Scan error on column index 20, name “publication_deadline”: unsupported Scan, storing driver.Value type string into type *time.Time
app_proxy_1 | yarn run v1.22.19
app_proxy_1 | $ node ./bin/www
app_proxy_1 | [HPM] Proxy created: / → http://lightning-terminal_web_1:3004
app_proxy_1 | Waiting for lightning-terminal_web_1:3004 to open…
app_proxy_1 | Lightning Terminal is now ready…
app_proxy_1 | Listening on port: 3004
app_proxy_1 | Validating token: dbdd00974941 …
app_proxy_1 | Validating token: dbdd00974941 …

per umbrel store, app is up to date.