Umbrel Web‑UI flow to recover LND using a Lightning seed + Static Channel Backup (SCB)

58edc6ae61f49115...

npub1trkudtnp7jg3tmy4sz8mepmgs5wdxk9x2esgts25mgkyecrse7js6ptss5

hex

5de7224c3dc0bfb7481befa396aa8123dfebc10d66df6a4a97c227bc67d17fb6

nevent

nevent1qqs9meezfs7up0ahfqd7lguk42qj8hltcyxkdhm2f2tuyfauvlghldsprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgs93mwx4eslfyg4aj2cprausa5g28xntzn9vcy9c92d5tzvupcvlfgmam5a9

naddr

naddr1qpf82mtzwfjkctthv43826fdvekx7aedw3hj6un9vdhhvetj94kxuepdw4ekjmn894sj6mrfva58gmnfdenj6um9v4jz6ttnw3shg6tr943ksctwdejkcttzv93kkats94ekxcsprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgs93mwx4eslfyg4aj2cprausa5g28xntzn9vcy9c92d5tzvupcvlfgrqsqqqa28guzqv3

Kind-30023 (Article)

2026-04-19T09:09:26Z

(Written as if you are sitting at the browser, clicking through Umbrel, with no SSH and no guesswork.)

This manual covers two cases:

1. Normal failure recovery (most common)

2. Full re‑install / new device (clean slate)

What you must have before you start

✅ Lightning seed (24 words)

channel.backup file

✅ Access to Umbrel UI umbrel.local or IP)

If you are missing either the seed or SCB, stop — recovery cannot be done safely.

CASE 1 — Umbrel is running, LND data is lost or broken

(This includes corrupted Lightning DB, failed updates, or stuck LND.)

Step 1 — Open Umbrel dashboard

  • Go to: http://umbrel.local

  • Log in

You should see the main app grid.

Step 2 — Open Lightning (LND) app

Click Lightning (or LND if named explicitly)

If LND detects missing data, you may immediately see a *recovery prompt

If not, continue manually.

Step 3 — Trigger recovery mode

Click Settings ⚙️ inside the Lightning app

Choose Restore Wallet or Recover Wallet

  • Wording may vary by Umbrel version

  • This option appears only when LND is uninitialised or reset

Umbrel now switches into Lightning wallet setup mode.

Step 4 — Choose Restore existing wallet

When prompted:

Select Restore existing Lightning wallet”*

* NOT “Create new wallet”

Step 5 — Enter your Lightning seed

You will see a seed entry screen.

Do the following:

Enter all 24 Lightning words

  • Ensure correct order

  • Confirm spelling carefully

Click Continue.

✅ At this moment:

  • Your Lightning node identity is restored

  • No channels are restored yet

  • Funds are not touched

Step 6 — Import channel backup (SCB)

Next screen:

  • Upload channel.backup

  • Choose the SCB file you previously saved

Click Import.

✅ Umbrel will confirm:

  • Backup imported successfully

  • Number of channels detected

Step 7 — Confirm force‑close recovery

Umbrel now warns you (wording varies):

> “Channels will be force‑closed and funds recovered on‑chain”

You must:

✅ Acknowledge this

✅ Confirm recovery

Click Start Recovery / Confirm.

There is no alternative path — this is intentional.

Step 8 — LND restarts automatically

Umbrel will:

  • Restart Lightning

  • Begin peer recovery connections

You may see:

  • “Recovering channels”

  • “Waiting for force‑closes”

This phase:

  • May take minutes to hours

  • Requires Bitcoin node connectivity

Step 9 — Monitor recovery

Inside Lightning app:

  • Channels appear as pending close

  • Status messages update automatically

Nothing else to click.

Step 10 — Funds return on‑chain (after timelocks)

After force‑closes confirm:

  • Funds appear in the on‑chain wallet used to fund channels (Bitcoin Core on Umbrel, or whatever external wallet originally funded the channels)

  • Timelock period applies (often \~1–2 weeks)

✅ Recovery complete

❌ Channels are permanently gone (expected)

CASE 2 — Full Umbrel reinstall or new device

(This is the more common true disaster scenario.)

Step 1 — Install fresh Umbrel

  • Install Umbrel on new disk/device

  • Complete initial setup

  • Log into the dashboard

Do not install apps yet.

Step 2 — Install Lightning (LND) app

  • Open App Store

  • Install *Lightning

Umbrel launches Lightning in uninitialised mode.

Step 3 — Choose Restore wallet

You will be prompted:

Select Restore existing wallet

NOT “Create new wallet”

Step 4 — Enter Lightning seed

Same as Case 1, Step 5:

  • Enter all seed words

  • Confirm order

Step 5 — Import channel backup

Same as Case 1, Step 6:

  • Upload channel.backup

  • Confirm import

Step 6 — Confirm recovery + force‑close

Same as Case 1, Step 7.

Umbrel/LND now:

  • Connects to former peers

  • Requests force‑close of all channels

Step 7 — Wait for on‑chain settlement

Nothing else to do in the UI.

Lightning app will show:

  • Recovering → Closed channels

  • After timelock: zero channels, full balance on‑chain

What you should never see in Umbrel UI (by design)

The following actions are intentionally impossible in Umbrel, because they would be unsafe if channel state has been lost:

❌ “Restore channel balances”

❌ “Resume channels”

❌ “Undo force‑close”

❌ “Restore Lightning DB”

If you ever see claims suggesting otherwise, something is wrong.

Quick visual checklist (mental)

Correct recovery flow always looks like:

Install LND

→ Restore wallet

→→ Enter Lightning seed

→→→ Import channel.backup

→→→→ Confirm force‑close

→→→→→ Wait

→→→→→→ Funds on‑chain

If any step is skipped, recovery is unsafe.

Why Umbrel UI is intentionally strict

Umbrel intentionally:

  • Forces seed first

  • Forces SCB second

  • Forces destructive recovery

This prevents:

  • Accidental stale‑state broadcasts

  • Channel penalty loss

  • User‑error recoveries

Safety > convenience.

原始 JSON

{
  "kind": 30023,
  "id": "5de7224c3dc0bfb7481befa396aa8123dfebc10d66df6a4a97c227bc67d17fb6",
  "pubkey": "58edc6ae61f49115ec95808fbc8768851cd358a6566085c154da2c4ce070cfa5",
  "created_at": 1776597471,
  "tags": [
    [
      "title",
      "Umbrel Web‑UI flow to recover LND using a Lightning seed + Static Channel Backup (SCB)"
    ],
    [
      "summary",
      "In Umbrel, LND recovery is a guided, destructive‑by‑design UI flow: restore Lightning seed → import SCB → force‑close → wait → funds recovered on‑chain."
    ],
    [
      "image",
      "https://blossom.primal.net/b0a73ef0d714db5dbbae162df433652431877c3b92a877c2273410636f64425d.png"
    ],
    [
      "d",
      "umbrel-webui-flow-to-recover-lnd-using-a-lightning-seed--static-channel-backup-scb"
    ],
    [
      "t",
      "Umbrel"
    ],
    [
      "t",
      "Backup"
    ],
    [
      "t",
      "Recovery"
    ],
    [
      "r",
      "wss://relay.dwadziesciajeden.pl/"
    ],
    [
      "r",
      "wss://nos.lol/"
    ],
    [
      "r",
      "wss://relay.getalby.com/v1"
    ],
    [
      "r",
      "wss://relay.primal.net/"
    ],
    [
      "r",
      "wss://purplepag.es/"
    ],
    [
      "r",
      "wss://eden.nostr.land/"
    ],
    [
      "r",
      "wss://relay.damus.io/"
    ],
    [
      "r",
      "wss://nostr.wine/"
    ],
    [
      "r",
      "wss://nostr.bitcoiner.social/"
    ],
    [
      "r",
      "wss://nostr-pub.wellorder.net/"
    ],
    [
      "r",
      "wss://nostr-01.yakihonne.com/"
    ],
    [
      "r",
      "wss://nostr-02.yakihonne.com/"
    ],
    [
      "client",
      "Primal Web"
    ],
    [
      "published_at",
      "1776589766"
    ]
  ],
  "content": "(Written as if you are sitting at the browser, clicking through Umbrel, with **no SSH** and **no guesswork**.)\n\n#### This manual covers two cases:\n\n1\\. Normal failure recovery (most common)\n\n2\\. Full re‑install / new device (clean slate)\n\n#### What you must have **before you start**\n\n✅ Lightning seed (24 words)\n\n✅ `channel.backup` file\n\n✅ Access to Umbrel UI `umbrel.local` or IP)\n\nIf you are missing **either the seed or SCB**, stop — recovery cannot be done safely.\n\n### CASE 1 — Umbrel is running, LND data is lost or broken\n\n(This includes corrupted Lightning DB, failed updates, or stuck LND.)\n\n#### Step 1 — Open Umbrel dashboard\n\n* Go to: `http://umbrel.local`\n\n* Log in\n\nYou should see the main app grid.\n\n#### Step 2 — Open **Lightning (LND)** app\n\nClick **Lightning** (or **LND** if named explicitly)\n\nIf LND detects missing data, you may immediately see a \\***recovery prompt**\n\nIf not, continue manually.\n\n#### Step 3 — Trigger recovery mode\n\n*Click* **Settings** ⚙️ inside the Lightning app\n\nChoose **Restore Wallet** or **Recover Wallet**\n\n* Wording may vary by Umbrel version\n\n* This option appears only when LND is uninitialised or reset\n\nUmbrel now switches into **Lightning wallet setup mode**.\n\n#### Step 4 — Choose **Restore existing wallet**\n\nWhen prompted:\n\n*Select\u0026#x20;*“**Restore existing Lightning wallet**”\\*\n\n\\* NOT “Create new wallet”\n\n##### Step 5 — Enter your **Lightning seed**\n\nYou will see a seed entry screen.\n\nDo the following:\n\nEnter all **24 Lightning words**\n\n* Ensure correct order\n\n* Confirm spelling carefully\n\nClick **Continue**.\n\n✅ At this moment:\n\n* Your Lightning node identity is restored\n\n* No channels are restored yet\n\n* Funds are not touched\n\n###### Step 6 — Import **channel backup (SCB)**\n\nNext screen:\n\n* **Upload channel.backup**\n\n* Choose the SCB file you previously saved\n\nClick **Import**.\n\n✅ Umbrel will confirm:\n\n* Backup imported successfully\n\n* Number of channels detected\n\n#### Step 7 — Confirm force‑close recovery\n\nUmbrel now warns you (wording varies):\n\n\\\u0026gt; “Channels will be force‑closed and funds recovered on‑chain”\n\nYou must:\n\n✅ Acknowledge this\n\n✅ Confirm recovery\n\nClick **Start Recovery** / **Confirm**.\n\nThere is no alternative path — this is intentional.\n\n#### Step 8 — LND restarts automatically\n\nUmbrel will:\n\n* Restart Lightning\n\n* Begin peer recovery connections\n\nYou may see:\n\n* “Recovering channels”\n\n* “Waiting for force‑closes”\n\nThis phase:\n\n* May take minutes to hours\n\n* Requires Bitcoin node connectivity\n\n#### Step 9 — Monitor recovery\n\nInside Lightning app:\n\n* Channels appear as `pending close`\n\n* Status messages update automatically\n\nNothing else to click.\n\n#### Step 10 — Funds return on‑chain (after timelocks)\n\nAfter force‑closes confirm:\n\n* Funds appear in the on‑chain wallet used to fund channels (Bitcoin Core on Umbrel, or whatever external wallet originally funded the channels)\n\n* Timelock period applies (often \\\\\\~1–2 weeks)\n\n✅ Recovery complete\n\n❌ Channels are permanently gone (expected)\n\n### CASE 2 — Full Umbrel reinstall or new device\n\n(This is the more common true disaster scenario.)\n\n#### Step 1 — Install fresh Umbrel\n\n* Install Umbrel on new disk/device\n\n* Complete initial setup\n\n* Log into the dashboard\n\nDo **not** install apps yet.\n\n#### Step 2 — Install **Lightning (LND)** app\n\n* Open **App Store**\n\n* Install \\***Lightning**\n\nUmbrel launches Lightning in **uninitialised mode**.\n\n#### Step 3 — Choose **Restore wallet**\n\nYou will be prompted:\n\nSelect **Restore existing wallet**\n\n**NOT** “Create new wallet”\n\n#### Step 4 — Enter Lightning seed\n\nSame as Case 1, Step 5:\n\n* Enter all seed words\n\n* Confirm order\n\n#### Step 5 — Import channel backup\n\nSame as Case 1, Step 6:\n\n* Upload `channel.backup`\n\n* Confirm import\n\n#### Step 6 — Confirm recovery + force‑close\n\nSame as Case 1, Step 7.\n\nUmbrel/LND now:\n\n* Connects to former peers\n\n* Requests force‑close of all channels\n\n#### Step 7 — Wait for on‑chain settlement\n\nNothing else to do in the UI.\n\nLightning app will show:\n\n* Recovering → Closed channels\n\n* After timelock: zero channels, full balance on‑chain\n\n##### What you should **never** see in Umbrel UI (by design)\n\nThe following actions are intentionally impossible in Umbrel, because they would be unsafe if channel state has been lost:\n\n❌ “Restore channel balances”\n\n❌ “Resume channels”\n\n❌ “Undo force‑close”\n\n❌ “Restore Lightning DB”\n\nIf you ever see claims suggesting otherwise, something is wrong.\n\n#### Quick visual checklist (mental)\n\n**Correct recovery flow always looks like:**\n\n###### Install LND\n\n→ Restore wallet\n\n→→ Enter Lightning seed\n\n→→→ Import channel.backup\n\n→→→→ Confirm force‑close\n\n→→→→→ Wait\n\n→→→→→→ Funds on‑chain\n\nIf **any step is skipped**, recovery is unsafe.\n\n#### Why Umbrel UI is intentionally strict\n\nUmbrel intentionally:\n\n* Forces seed first\n\n* Forces SCB second\n\n* Forces destructive recovery\n\nThis prevents:\n\n* Accidental stale‑state broadcasts\n\n* Channel penalty loss\n\n* User‑error recoveries\n\n###### Safety \u003e convenience.\n",
  "sig": "09f8dfd392a1e3c9da2da8465fc97d13dfcbb17600634920264770f2941fd538139fd0ba957ecf17d46a0846f1f58125ee2f153df9f27dac53270dc84a9b99ed"
}