I’ve never had any issues with updating my umbrel. The updating screen got “stuck” during the update. I waited an hour and no changes. I’ve restared umbrel. Unplugged and plugged back in and now I cannot get into the umbrel home page. I get the red error page.
Any help about what to do next is much appreciated.
Flased new OS. Did not help.
Bought new Samsung microSD card. Flased new OS. Did not help.
Now what?
n080dy
March 16, 2022, 5:52am
3
Posting your debug log will help better to understand what’s going on. Upload it on 0bin and share the link here
You are also not the first one having this issue , nor you’ll be the last…
However, I’ll suggest having a look at the Troubleshoot Guide it will probably help
1 Like
This is the problem:
[ERR] LTND: unable to create partial chain control: status code: 401
See someone with a similar problem below
opened 03:35PM - 19 Dec 21 UTC
closed 09:26AM - 20 Dec 21 UTC
### Background
i was attempting to runn lightning on my node but dont know, a… nd cant find a solution, to fix the issues the terminal tells me it has..
- [ERR] LTND: unable to create partial chain control: status code: 401, response: ""
- [ERR] LTND: Shutting down because error in main method: error creating wallet config: unable to create partial chain control: status code: 401, response: ""
### Your environment
* LND version 0.14.1-beta
* ubuntu server 20.04.3 LTS 64-bit amd64 aarch64
uname-a --> Linux ubuntu 5.4.0-1047-raspi #52-Ubuntu SMP PREEMPT aarch64 aarch64 aarch64 GNU/Linux
* bitcoin core V22.0
* raspberry pi 4 8GB.ram
### Steps to reproduce
dont know how to show u guys this.
butt if i do in the first terminal "$lnd" and in the second "$lncli unlock"
then the second terminal will say: "lnd successfully unlocked!"
but the first terminal will say
[INF] LTND: Version: 0.14.1-beta commit=v0.14.1-beta, build=production, logging=default, debuglevel=info
[INF] LTND: Active chain: Bitcoin (network=mainnet)
[INF] RPCS: RPC server listening on 0.0.0.0:10009
[INF] RPCS: gRPC proxy started at 0.0.0.0:8080
[INF] LTND: Opening the main database, this might take a few minutes...
[INF] LTND: Opening bbolt database, sync_freelist=false, auto_compact=false
[INF] LTND: Creating local graph and channel state DB instances
[INF] CHDB: Checking for schema update: latest_version=24, db_version=24
[INF] LTND: Database(s) now open (time_to_open=60.728977ms)!
[INF] LTND: We're not running within systemd
[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.
[INF] LNWL: Opened wallet
[INF] CHRE: Primary chain is set to: bitcoin
[ERR] LTND: unable to create partial chain control: status code: 401, response: ""
[ERR] LTND: Shutting down because error in main method: error creating wallet config: unable to create partial chain control: status code: 401, response: ""
[INF] LTND: Shutdown complete
error creating wallet config: unable to create partial chain control: status code: 401, response: ""
-----------------------------------------------------------------
also some of the settings
~/.lnd/lnd.conf
[Application Options]
tlsautorefresh=true
restlisten=0.0.0.0:8080
rpclisten=0.0.0.0:10009
listen=127.0.0.1:9735
maxpendingchannels=5
color=XXXXXX
alias=XXXXXX
[Tor]
tor.active=true
tor.v3=true
tor.streamisolation=true
[Bitcoin]
bitcoin.active=true
bitcoin.mainnet=true
bitcoin.node=bitcoind
[bitcoind]
bitcoind.dir=/home/ubuntu/.bitcoin
bitcoind.rpcuser=XXXXXX
bitcoind.rpcpass=XXXXXX
bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332
bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333
--------------------------------------------------------------------------
~/.bitcoin/bitcoin.conf
server=1
daemon=1
listen=1
txindex=1
blockfilterindex=1
disablewallet=0
dbcache=3000
onlynet=onion
proxy=127.0.0.1:9050
bind=127.0.0.1
zmqpubrawblock=tcp://127.0.0.1:28332
zmqpubrawtx=tcp://127.0.0.1:28333
rpcauth=XXXXXXX
### Expected behaviour
i was expecting lnd to start syncing
### Actual behaviour
lnd automatically closed..
Perhaps someone else can chime in with a solution other than a restart. Did you change anything in your lnd.conf?
Yeah I read that issue. Is really strange.
What could try is to do a rescan blocks at restart node. I wrote the instructions in the Umbrel troubleshooting manual but that takes time.