5100 sats \ 7 replies \ @lnvisualizer 10 Oct 2022 \ parent \ on: lnd cant sync to chain due to taproot bug bitcoin
Yeah this won't work for that. You'll have to update to 0.5.X or manually fix it.
For umbrel 0.4.x you'll have to edit the ./umbrel/docker-compose.yml file manually.
In that file you'll see a list of services.
If you scroll down to the lnd section
    ...
                networks:
                    default:
                        ipv4_address: $BITCOIN_IP
        lnd:
                container_name: lnd
                image: lightninglabs/lnd:v0.14.1-beta
you should be able to manually edit the container (on line 7 here) to
lightninglabs/lnd:v0.15.2-beta
and then restart the node, or run
sudo ./umbrel/script/start
to just apply the update
write
preview
15 sats \ 0 replies \ @BlokchainB 10 Oct 2022
Thank you so much!!! I don’t want to upgrade my umbrel to 0.5.X will try this manual update for my node
reply
10 sats \ 2 replies \ @BlokchainB 11 Oct 2022
it worked!! Node went down this morning did this fix after restarting and about 10 mins wait all my peers and channels came back. For your assistance I tipped 5k sats.
reply
1000 sats \ 1 reply \ @lnvisualizer 11 Oct 2022
Wow thank you so much! Really appreciate it. Happy your node is fixed.
reply
0 sats \ 0 replies \ @BlokchainB 21 Oct 2022
Curious with LND going to 15.3 how do I find the image file on the GitHub to manually update my node? One of my channels is not working and my node isn’t routing any payments anymore.
reply
10 sats \ 1 reply \ @pillar 10 Oct 2022
Thanks a lot. This is exactly what I did a few hours ago and it worked fine. No further steps were needed.
reply
0 sats \ 0 replies \ @lnvisualizer 11 Oct 2022
Awesome! Glad to hear the fix worked
reply
0 sats \ 0 replies \ @lnvisualizer 10 Oct 2022
As or upgrading to 0.5.X, you should be able to go to the settings menu and click the update button if you are on 0.4.18. https://github.com/getumbrel/umbrel/issues/1422
If not, then I'm not then in all honesty not sure what the procedure is. It might let you update to 0.4.18 and then after 0.5.X.
If not, you may need to manually apply the fix or reinstall 0.5.X.
reply