SSH using Putty

I downloaded Putty to SSH into my Umbrel node that is running on a RaspPi4. When I open Putty I input my nodes IP, it opens the window with the prompt asking for Login ID which I input, then I get to the enter password line but when I try to type in my password the cursor doesn’t move when I start typing in the password. Then after about 60 seconds I get a pop up with an error message Remote side unexpectedly closed the network connection. Confused as to whats going on.

  1. for RPi users the user is umbrel and your regular password to enter into your Umbrel dashboard
  2. for non-RPi users (standard linux OS) is your machine user/password you set
  3. the password on SSH screen is NOT visible (securrity reasons) so you just type it and hit ENTER
1 Like

That’s not working for some reason, I get access denied. Hmmmm!

Ok, it was my error. I wasn’t typing my password in correctly, duhhh! I got in. Thanks Darth!

One more question now that I can get in via Putty. Since the update to version .04.15 my Lightning channels are showing offline thought my wallet was locked, followed the instructions to unlock wallet and it said my wallet was unlocked, but in Umbrel it stills shows the same do these debug logs tell you anything,

Bitcoin Core logs

Attaching to bitcoin
bitcoin | 2022-03-20T18:53:44Z Socks5() connect to 2607:fea8:44e0:ec56::b:8333 failed: general failure
bitcoin | 2022-03-20T19:00:30Z UpdateTip: new best=00000000000000000000ed461b593bb080dab69263d73bd3bedf91d3cc8850f8 height=728247 version=0x3fffe004 log2_work=93.413051 tx=719119532 date=‘2022-03-20T18:57:33Z’ progress=0.999999 cache=90.3MiB(666986txo)
bitcoin | 2022-03-20T19:02:26Z UpdateTip: new best=000000000000000000050b04fa1c40615ea8417a2761ec762fb8e513caf97a52 height=728248 version=0x24446000 log2_work=93.413064 tx=719120618 date=‘2022-03-20T19:02:15Z’ progress=1.000000 cache=90.5MiB(668709txo)
bitcoin | 2022-03-20T19:03:44Z UpdateTip: new best=00000000000000000001234dab0c2706330a4f4ca1431e8b29de393c0ffab732 height=728249 version=0x3fffe004 log2_work=93.413077 tx=719120666 date=‘2022-03-20T19:02:28Z’ progress=1.000000 cache=90.5MiB(669008txo)
bitcoin | 2022-03-20T19:06:28Z UpdateTip: new best=00000000000000000002892032b9929e072ab70d2a0ef397d5f9107868304b18 height=728250 version=0x20800004 log2_work=93.413090 tx=719121438 date=‘2022-03-20T19:05:55Z’ progress=1.000000 cache=90.6MiB(669755txo)
bitcoin | 2022-03-20T19:06:28Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
bitcoin | 2022-03-20T19:06:28Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
bitcoin | 2022-03-20T19:06:28Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
bitcoin | 2022-03-20T19:06:28Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
bitcoin | 2022-03-20T19:10:20Z Socks5() connect to 143.198.119.108:8333 failed: general failure
bitcoin | 2022-03-20T19:12:13Z Socks5() connect to 193.138.218.210:8333 failed: general failure
bitcoin | 2022-03-20T19:16:26Z New outbound peer connected: version: 70015, blocks=728250, peer=1516 (block-relay-only)
bitcoin | 2022-03-20T19:16:31Z UpdateTip: new best=0000000000000000000a00d92e442a69f22ced1471adb3fe746620ce1bc7f289 height=728251 version=0x20200000 log2_work=93.413103 tx=719123246 date=‘2022-03-20T19:15:54Z’ progress=1.000000 cache=91.0MiB(672636txo)
bitcoin | 2022-03-20T19:23:32Z UpdateTip: new best=000000000000000000090170066ae6e8856e59b105d80999421b744ab8e3572f height=728252 version=0x20800004 log2_work=93.413116 tx=719124701 date=‘2022-03-20T19:23:02Z’ progress=1.000000 cache=91.4MiB(675604txo)
bitcoin | 2022-03-20T19:29:00Z Socks5() connect to 89.45.90.22:8333 failed: general failure
bitcoin | 2022-03-20T19:29:04Z Socks5() connect to 94.114.208.185:8333 failed: general failure
bitcoin | 2022-03-20T19:43:51Z UpdateTip: new best=000000000000000000038d5962a77eab321ebee61a43a7dd288ff8e34ff92cd2 height=728253 version=0x20000000 log2_work=93.413129 tx=719128131 date=‘2022-03-20T19:43:37Z’ progress=1.000000 cache=92.6MiB(685599txo)
bitcoin | 2022-03-20T19:48:27Z Socks5() connect to 141.105.133.46:8333 failed: general failure
bitcoin | 2022-03-20T19:51:17Z New outbound peer connected: version: 70016, blocks=728253, peer=1522 (block-relay-only)
bitcoin | 2022-03-20T19:59:01Z UpdateTip: new best=00000000000000000000deec0683190ef56c7b9a844f5864b956ae822908cedd height=728254 version=0x333b6000 log2_work=93.413142 tx=719131023 date=‘2022-03-20T19:58:38Z’ progress=1.000000 cache=93.4MiB(692227txo)
bitcoin | 2022-03-20T20:05:24Z New outbound peer connected: version: 70016, blocks=728254, peer=1525 (block-relay-only)
bitcoin | 2022-03-20T20:06:53Z Socks5() connect to 2600:3c00::f03c:91ff:fe73:48b3:8333 failed: general failure
bitcoin | 2022-03-20T20:10:36Z Socks5() connect to 2605:a601:a0ca:4800:3d70:7eaf:30fe:fcf5:8333 failed: general failure
bitcoin | 2022-03-20T20:19:19Z Socks5() connect to 91.65.197.122:8333 failed: general failure
bitcoin | 2022-03-20T20:20:46Z New outbound peer connected: version: 70015, blocks=728254, peer=1527 (block-relay-only)
bitcoin | 2022-03-20T20:26:26Z Socks5() connect to 38.70.11.163:8333 failed: connection refused
bitcoin | 2022-03-20T20:29:02Z Socks5() connect to 2a0b:f4c0:16c:3::1:8333 failed: general failure
bitcoin | 2022-03-20T20:34:17Z UpdateTip: new best=00000000000000000001d16b73a56c056bcaeeea46b3a0434191ba37c5c7f187 height=728255 version=0x20c00004 log2_work=93.413154 tx=719134099 date=‘2022-03-20T20:33:45Z’ progress=1.000000 cache=95.0MiB(705507txo)
bitcoin | 2022-03-20T20:36:02Z Socks5() connect to 194.110.112.10:8333 failed: general failure

LND logs

Attaching to lnd
lnd | 2022-03-20 20:38:19.892 [ERR] RPCS: [/lnrpc.Lightning/WalletBalance]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:19.900 [ERR] RPCS: [/lnrpc.Lightning/GetTransactions]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:19.919 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:19.973 [ERR] RPCS: [/lnrpc.Lightning/ListInvoices]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:19.975 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:19.976 [ERR] RPCS: [/lnrpc.Lightning/PendingChannels]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:20.033 [ERR] RPCS: [/lnrpc.Lightning/ListPayments]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:21.182 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:24.320 [ERR] RPCS: [/routerrpc.Router/SubscribeHtlcEvents]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:29.583 [INF] LTND: Creating local graph and channel state DB instances
lnd | 2022-03-20 20:38:30.374 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:31.547 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:31.549 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:31.550 [ERR] RPCS: [/lnrpc.Lightning/SubscribeInvoices]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:31.550 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:32.238 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:38.327 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:38.462 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:39.955 [ERR] RPCS: [/lnrpc.Lightning/GetTransactions]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:39.965 [ERR] RPCS: [/lnrpc.Lightning/WalletBalance]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:40.007 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:40.009 [ERR] RPCS: [/lnrpc.Lightning/PendingChannels]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:40.010 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:40.014 [ERR] RPCS: [/lnrpc.Lightning/ListInvoices]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:40.262 [ERR] RPCS: [/lnrpc.Lightning/ListPayments]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:41.816 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: waiting to start, RPC services not available
lnd | 2022-03-20 20:38:41.873 [INF] CHDB: Checking for schema update: latest_version=24, db_version=24
lnd | 2022-03-20 20:38:41.874 [INF] LTND: Database(s) now open (time_to_open=52.718945734s)!
lnd | 2022-03-20 20:38:41.880 [INF] LTND: We’re not running within systemd
lnd | 2022-03-20 20:38:41.891 [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.

Just have patience and first thing is to login into Umbrel dashboard. That will unlock it.

Waited a day after running the wallet unlock command, logged back into Umbrel and used the reboot command under settings, Umbrel rebooted. All my Lightning channels still showing offline with the correct balances in them. Not sure what my issue is, or what the next step would be to correct my situation. Also when I try to generate a deposit address in Bitcoin core I get the QR code but nothing shows up in the copy/paste box below it.

And when I try to open Thunderhub I get “Unable to connect to this node” response if thats any help. Basically it seems my Lightning node is not connecting anymore.

Try SSH command “top”, see if any process has high activity (around 100%). Channels won´t return online if indexes are being updated, shown by high activity.

It shows lnd running anywhere from 60 to 114% on CPU. They’ve been offline for a month now ever since the 0.4.15 update. Something f’ed up with that update. On 1ML it shows 2 of my 5 channels closed, so I’ve lost those sats I imagine. 3 channels it still shows open, I want to get those sats back before I lose them too if I haven’t lost them yet. Very frustrated, but trying to keep my patience! If I can get this rectified I think I’m taking a pause on the Lightning network.

Seems your LND wallet is still locked. Unlock it, as in @DarthCoin guide:
http://community.umbrel.com/t/umbrel-troubleshooting-guide/3632/2
don´t jump the step to reset lnd.conf, as may be something wrong in it.
Never restart your node after this until you see cpu load is low, or you will damage indexes and be in trouble again!

Forgive me, but when I look at the wallet unlock line in the troubleshoot manual I don’t see that “reset lnd.conf” mentioned. Could you point me more directly to that…

BTW thanks so much for your help!

Sorry I get what your saying now, alittle slow tonite. I see where it was you were directing me. Thanks again Lobo!

Ran thru the second version of the LND wallet unlock, and it appears that my wallet is indeed unlocked. The debug log reads different now. RPC running again and such. But I’m starting to believe my node itself is locked, is that possible?

I don´t know, i never had those problems. By the way, remove Mempool and any other auto-rebalancer app you have, they eat cpu time, and slow things a lot. A normal reindex takes 2 days or more.
Observe cpu load of bitcoind and electrs processes, their load keep changing a lot, but should not stay high most time.
If you may post logs (also dmesg) is nice. Use www.pastebin.com if you don´t have permission to upload files here.

1 Like

Here’s the debug log Lobo.