Upgrade to StartOS 0.4.0 and Lightning Terminal

[swow]

LITD won’t start up again after upgrading the service to the latest version and then performing the StartOS 0.4.0 upgrade from 0.3.5.1:

2026-07-25T23:15:52+01:00  2026-07-25 22:15:52.018 [INF] LITD: LiT version: 0.17.0-alpha commit=v0.17.0-alpha commit_hash=08934deeefe306d99e402c6c683bac3171fff88f
2026-07-25T23:15:52+01:00  error starting main proxy HTTP server: unable to listen on 0.0.0.0:8443: listen tcp 0.0.0.0:8443: bind: address already in use
2026-07-25T23:15:52+01:00  2026-07-25 22:15:52.019 [INF] LITD: Listening for http_tls on: 127.0.0.1:8443
2026-07-25T23:15:52+01:00  Error: /bin/litd exited with code 1
2026-07-25T23:15:52+01:00   at ChildProcess.<anonymous> (/usr/lib/startos/package/index.js:4521:39)
2026-07-25T23:15:52+01:00   at ChildProcess.emit (node:events:524:28)
2026-07-25T23:15:52+01:00   at ChildProcess._handle.onexit (node:internal/child_process:293:12)
2026-07-25T23:15:52+01:00  Health Check lit failed: lit daemon crashed

I’ve tried rebuilding the Lightning Terminal service, but it didn’t seem to help - same error. Any ideas?

Thanks

Billy

[StuPleb]

Give me a few hours and I’ll look into it. You might not need LiT on StartOS v040 though, since connection options of LND are greatly expanded.

[swow]

This might be be an OK answer IF (and I don’t know if this is true or not) LiT is not in control of any funds (or assets, but I don’t have any non-bitcoin trash ). I’m pretty sure I haven’t messed around with Pool either. Thx, will let you ruminate on it.

[StuPleb]

LiT has nothing to do with holding your funds. It’s primarily a means of connecting to LND in StartOS v0351, and pretty redundant in v040

[StuPleb]

OK, looks like I’ve been able to fix it. Check for updates.

[lakesurfer]

same issue here too lit daemon crashed

[swow]

The latest update of the LiT service did fix it for me