After updating the Lightning app. Umbrel apps doesn't work

Support and Troubleshooting
1

Hi,

I updated my lightning app on umbrel. After that my LND doesn’t start and the last entry in the logs:
2022-08-24 23:35:51.632 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.
After unlocking most of the apps including Thunderhub and Lightning app doesn’t work.
I can see this in the thunderhub log:

LITD: Could not start subservers: error subscribing to lnd wallet state: lnd version incompatible, need at least v0.13.0-beta, got error on state subscription: rpc error: code = Unavailable desc = connection error: desc = “transport: authentication handshake failed: x509: certificate is valid for 127.0.0.1, ::1, not 10.21.21.9”

Lightning terminal:

web_1 | 2022-08-25 07:20:04.906 [INF] LNDC: Creating lnd connection to 10.21.21.9:10009
web_1 | 2022-08-25 07:20:04.906 [INF] LNDC: Connected to lnd
web_1 | 2022-08-25 07:20:04.906 [WRN] GRPC: [core] grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 10.21.21.9:10009 0 }. Err: connection error: desc = “transport: authentication handshake failed: x509: certificate is valid for 127.0.0.1, ::1, not 10.21.21.9”. Reconnecting…
web_1 | 2022-08-25 07:20:04.907 [WRN] GRPC: [core] grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 10.21.21.9:10009 0 }. Err: connection error: desc = “transport: authentication handshake failed: x509: certificate is valid for 127.0.0.1, ::1, not 10.21.21.9”. Reconnecting…
web_1 | 2022-08-25 07:20:04.907 [ERR] LITD: Could not start subservers: error subscribing to lnd wallet state: lnd version incompatible, need at least v0.13.0-beta, got error on state subscription: rpc error: code = Unavailable desc = connection error: desc = “transport: authentication handshake failed: x509: certificate is valid for 127.0.0.1, ::1, not 10.21.21.9”
web_1 | 2022-08-25 07:20:04.907 [INF] SGNL: Received shutdown request.
web_1 | 2022-08-25 07:20:04.907 [INF] SGNL: Shutting down…
web_1 | error subscribing to lnd wallet state: lnd version incompatible, need at least v0.13.0-beta, got error on state subscription: rpc error: code = Unavailable desc = connection error: desc = “transport: authentication handshake failed: x509: certificate is valid for 127.0.0.1, ::1, not 10.21.21.9”

Every time I restart umbrel I need to unlock my wallet manually.

1 Like
3
  • Lnd is running: lnd version 0.15.0-beta commit=v0.15.0-beta
  • Bitcoin 100% synced
  • I can access lnd through ssh. Node is up and running.
  • Wallet needs to be unlocked manually after every start.
  • Lightning App, Thunderhub, Lightning terminal does not work
  • This all worked correctly before clicking the update Lightning app button on umbrel

Lightning terminal:

web_1 | 2022-08-25 07:54:33.093 [ERR] LITD: Could not start subservers: error subscribing to lnd wallet state: lnd version incompatible, need at least v0.13.0-beta, got error on state subscription: rpc error: code = Unavailable desc = connection error: desc = “transport: authentication handshake failed: x509: certificate is valid for 127.0.0.1, ::1, not 10.21.21.9”
web_1 | 2022-08-25 07:54:33.093 [INF] SGNL: Received shutdown request.
web_1 | 2022-08-25 07:54:33.093 [INF] SGNL: Shutting down…
web_1 | error subscribing to lnd wallet state: lnd version incompatible, need at least v0.13.0-beta, got error on state subscription: rpc error: code = Unavailable desc = connection error: desc = “transport: authentication handshake failed: x509: certificate is valid for 127.0.0.1, ::1, not 10.21.21.9”
web_1 | 2022-08-25 07:55:33.628 [INF] LITD: LiT version: 0.7.0-alpha commit=v0.7.0-alpha
web_1 | 2022-08-25 07:55:33.642 [INF] SESS: Checking for schema update: latest_version=0, db_version=0
web_1 | 2022-08-25 07:55:33.642 [INF] LITD: Dialing lnd gRPC server at 10.21.21.9:10009
web_1 | 2022-08-25 07:55:33.643 [INF] LITD: Listening for http_tls on: 127.0.0.1:8443
web_1 | 2022-08-25 07:55:33.643 [INF] LITD: Listening for http on: [::]:3004
web_1 | 2022-08-25 07:55:33.643 [WRN] GRPC: [core] grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 10.21.21.9:10009 0 }. Err: connection error: desc = “transport: authentication handshake failed: x509: certificate is valid for 127.0.0.1, ::1, not 10.21.21.9”. Reconnecting…
web_1 | 2022-08-25 07:55:33.644 [WRN] GRPC: [core] grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 10.21.21.9:10009 0 }. Err: connection error: desc = “transport: authentication handshake failed: x509: certificate is valid for 127.0.0.1, ::1, not 10.21.21.9”. Reconnecting…
web_1 | ----------------------------------------------------------
web_1 | Lightning Terminal (LiT) by Lightning Labs
web_1 |
web_1 | LND Operating mode remote
web_1 | LND Node status locked
web_1 | LND Alias ??? (node is locked)
web_1 | LND Version ??? (node is locked)
web_1 | LiT Version 0.7.0-alpha commit=v0.7.0-alpha
web_1 | Web interface 127.0.0.1:8443, 0.0.0.0:3004 (open https://127.0.0.1:8443 or http://localhost:3004 in your browser)
web_1 | ----------------------------------------------------------
web_1 | 2022-08-25 07:55:33.845 [INF] LNDC: Creating lnd connection to 10.21.21.9:10009
web_1 | 2022-08-25 07:55:33.845 [INF] LNDC: Connected to lnd
web_1 | 2022-08-25 07:55:33.846 [WRN] GRPC: [core] grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 10.21.21.9:10009 0 }. Err: connection error: desc = “transport: authentication handshake failed: x509: certificate is valid for 127.0.0.1, ::1, not 10.21.21.9”. Reconnecting…
web_1 | 2022-08-25 07:55:33.847 [WRN] GRPC: [core] grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 10.21.21.9:10009 0 }. Err: connection error: desc = “transport: authentication handshake failed: x509: certificate is valid for 127.0.0.1, ::1, not 10.21.21.9”. Reconnecting…
web_1 | 2022-08-25 07:55:33.847 [ERR] LITD: Could not start subservers: error subscribing to lnd wallet state: lnd version incompatible, need at least v0.13.0-beta, got error on state subscription: rpc error: code = Unavailable desc = connection error: desc = “transport: authentication handshake failed: x509: certificate is valid for 127.0.0.1, ::1, not 10.21.21.9”
web_1 | 2022-08-25 07:55:33.847 [INF] SGNL: Received shutdown request.
web_1 | 2022-08-25 07:55:33.847 [INF] SGNL: Shutting down…
web_1 | 2022-08-25 07:55:33.847 [INF] SGNL: Gracefully shutting down.
web_1 | error subscribing to lnd wallet state: lnd version incompatible, need at least v0.13.0-beta, got error on state subscription: rpc error: code = Unavailable desc = connection error: desc = “transport: authentication handshake failed: x509: certificate is valid for 127.0.0.1, ::1, not 10.21.21.9”

Thunderhub:

web_1 | error: Error: FailedToConnectToDaemon
web_1 | at /app/dist/modules/node/lnd/lnd.helpers.js:8:15
web_1 | at processTicksAndRejections (node:internal/process/task_queues:96:5)
web_1 | at async AuthResolver.getSessionToken (/app/dist/modules/api/auth/auth.resolver.js:206:31)
web_1 | at async target (/app/node_modules/@nestjs/core/helpers/external-context-creator.js:77:28)
web_1 | at async Object.getSessionToken (/app/node_modules/@nestjs/core/helpers/external-proxy.js:9:24),
web_1 | level: ‘error’,
web_1 | message: ‘Unable to connect to this node’,
web_1 | timestamp: ‘2022-08-25T07:53:27.716Z’
web_1 | }
web_1 | {
web_1 | context: ‘ExceptionsHandler’,
web_1 | stack: [
web_1 | ‘Error: UnableToConnectToThisNode\n’ +
web_1 | ’ at AuthResolver.getSessionToken (/app/dist/modules/api/auth/auth.resolver.js:209:19)\n’ +
web_1 | ’ at processTicksAndRejections (node:internal/process/task_queues:96:5)\n’ +
web_1 | ’ at async target (/app/node_modules/@nestjs/core/helpers/external-context-creator.js:77:28)\n’ +
web_1 | ’ at async Object.getSessionToken (/app/node_modules/@nestjs/core/helpers/external-proxy.js:9:24)’
web_1 | ],
web_1 | level: ‘error’,
web_1 | message: ‘UnableToConnectToThisNode’,
web_1 | timestamp: ‘2022-08-25T07:53:27.716Z’
web_1 | }

4

I am having the same issue.

5

Bunch of people having the same issue. Haven’t received any help from Umbrel.

6

So far, I have concluded that the issue likely has to do with lnd.conf:

failed to load config: /data/.lnd/lnd.conf:2: malformed key=value (Reply in our Messenger[Application Options])
Perhaps there is something in the update that creates a syntax error to occur regarding lnd.conf.

7

Yes, When I remove my lnd.conf file umbrel starts but I lose all my config including my alias and everything else. I still haven’t figure out what’s wrong with it.

8

Hey guys! Could you please share your LND config file (in DM if there are details you don’t want to expose like your node alias)?

9

Reply in our Messenger[Application Options]
maxpendingchannels=3
minchansize=10000
accept-keysend=true
alias=
[Bitcoin]
bitcoin.defaultchanconfs=2

[wtclient]
wtclient.active=true
wtclient.sweep-fee-rate=10

[watchtower]
watchtower.active=true

10

Hey, for me the solution was to delete this line for lnd.conf:
tlsdisableautofill=1

For you that “alias=” is likely to be the problem. Unless you just removed you alias for sharing the config.
Other than that I don’t have the “wtclient.sweep-fee-rate=10”, you can try to delete that.
For “[Watchtower]”, “[Wtclient]” the first letter uppercase for me, not sure if that helps

Everything else is the same for me.

11

Unfortunately, nothing that you mentioned worked for me. Thank you for the help though; I really appreciate it.

12

By the way, I did remove my alias for sharing the config, which is why there is only “alias=”

13

I’m having same problem, my conf file as follows:

[Application Options]
maxpendingchannels=3
minchansize=10000
accept-keysend=true
alias=X
color=#404080
protocol.wumbo-channels=true

[Bitcoin]
bitcoin.defaultchanconfs=2
bitcoin.basefee=0
bitcoin.feerate=0

14

I removed alias, color, base fee and feerate and it then worked. Added back alias & color and it still worked. So seemingly something to do with fee settings?

15

Hey, sorry for the delayed response. I have also tried to remove not-vital information from the lnd.conf file, but that hasn’t worked for me yet…please let me know if anyone knows or figures out an alterative solution.