# Umbrel died updating to umbrel v. 0.4.16 **URL:** \ **Category:** Support and Troubleshooting\ **Created:** [March 16, 2022, 2:37am UTC](https://community.umbrel.com/t/umbrel-died-updating-to-umbrel-v-0-4-16/6787 "2022-03-16T02:37:41Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Shittysocialcredit](https://avatars.discourse-cdn.com/v4/letter/s/6bbea6/32.png) [@Shittysocialcredit](https://community.umbrel.com/u/Shittysocialcredit)\ **Post date:** [March 16, 2022, 2:37am UTC](https://community.umbrel.com/t/umbrel-died-updating-to-umbrel-v-0-4-16/6787/1 "2022-03-16T02:37:41Z")
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. ---
**Author:** ![Shittysocialcredit](https://avatars.discourse-cdn.com/v4/letter/s/6bbea6/32.png) [@Shittysocialcredit](https://community.umbrel.com/u/Shittysocialcredit)\ **Post date:** [March 16, 2022, 4:04am UTC](https://community.umbrel.com/t/umbrel-died-updating-to-umbrel-v-0-4-16/6787/2 "2022-03-16T04:04:10Z")
Flased new OS. Did not help. Bought new Samsung microSD card. Flased new OS. Did not help. Now what? ---
**Author:** ![n080dy](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/n080dy/32/2207_2.png) [@n080dy](https://community.umbrel.com/u/n080dy)\ **Post date:** [March 16, 2022, 5:52am UTC](https://community.umbrel.com/t/umbrel-died-updating-to-umbrel-v-0-4-16/6787/3 "2022-03-16T05:52:08Z")
Posting your debug log will help better to understand what’s going on. Upload it on [0bin](http://0bin.net) and share the link here You are also [not the first one having this issue](http://community.umbrel.com/t/umbrel-node-stuck-in-restart-screen/3698), nor you’ll be the last… However, I’ll suggest having a look at the [Troubleshoot Guide](http://community.umbrel.com/t/umbrel-troubleshooting-guide/3632) it will probably help ---
**Author:** ![Shittysocialcredit](https://avatars.discourse-cdn.com/v4/letter/s/6bbea6/32.png) [@Shittysocialcredit](https://community.umbrel.com/u/Shittysocialcredit)\ **Post date:** [March 16, 2022, 3:38pm UTC](https://community.umbrel.com/t/umbrel-died-updating-to-umbrel-v-0-4-16/6787/4 "2022-03-16T15:38:25Z")
Thanks for the help! Here are the debug logs. [https://0bin.net/paste/BvEPOioa#1x10nmfuQ78DWCBPnK0aUHx87NRBPAlHIieDAJsUMJY](https://0bin.net/paste/BvEPOioa#1x10nmfuQ78DWCBPnK0aUHx87NRBPAlHIieDAJsUMJY) ---
**Author:** ![Doctore](https://avatars.discourse-cdn.com/v4/letter/d/977dab/32.png) [@Doctore](https://community.umbrel.com/u/Doctore)\ **Post date:** [March 17, 2022, 2:43pm UTC](https://community.umbrel.com/t/umbrel-died-updating-to-umbrel-v-0-4-16/6787/5 "2022-03-17T14:43:51Z")
This is the problem: [ERR] LTND: unable to create partial chain control: status code: 401 See someone with a similar problem below > > > \### 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? ---
**Author:** ![DarthCoin](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/darthcoin/32/1628_2.png) [@DarthCoin](https://community.umbrel.com/u/DarthCoin)\ **Post date:** [March 17, 2022, 3:02pm UTC](https://community.umbrel.com/t/umbrel-died-updating-to-umbrel-v-0-4-16/6787/6 "2022-03-17T15:02:34Z")
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](http://community.umbrel.com/t/umbrel-troubleshooting-guide/3632/) but that takes time.