Fixing LNURL Errors in LNBits on Umbrel: “LNURLs need to delivered over a publicly accessible https domain or Tor onion. 426”

Guides
1

Hey folks, running LNBits on Umbrel and getting the 426 LNURL error? It requires public HTTPS or Tor—local setups fail. Fix it with these Docker tweaks (assumes your domain proxies to Umbrel).

Assumptions: SSH access to Umbrel; public HTTPS domain set up; basic terminal skills.

Step 1: Navigate and Backup

SSH in and go to the config:

cd ~/umbrel/app-data/lnbits
cp docker-compose.yml docker-compose.yml.backup

Step 2: Edit docker-compose.yml

nano docker-compose.yml

Add (6-space indent):

  • Under app_proxy > environment (after PROXY_AUTH_ADD):

          PROXY_TRUST_UPSTREAM: 'true'

  • Under web > environment (at end):

          HOST: 'yourdomain.com'  # No https://
      FORWARDED_ALLOW_IPS: '*'

  • Optional: Change LNBITS_ADMIN_UI: 'true' to 'false' (helps env vars stick for some).

Save: Ctrl+O > Enter > Ctrl+X.

Step 3: Restart

CLI:

docker compose down && docker compose up -d

Or Umbrel UI: Go to http://umbrel.local, right-click LNBits > Stop > Start. Wait 1-2 min.

Step 4: Verify

  • Status: docker compose ps (both “Up”).
  • Env: docker compose exec web env | grep -E "(HOST|FORWARDED_ALLOW_IPS)" (shows your domain/*).
  • Logs: docker compose logs --tail=20 web (no errors).

Step 5: Test

Access https://yourdomain.com, create LNURL (e.g., pay link), validate in Zeus/BlueWallet—no 426.

Fixed mine quick—credit Umbrel threads. Questions? Comment! :high_voltage:

Posted October 7, 2025