Skip to content

LND Account: UI Navigation loosing basepath #1058

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
iBobik opened this issue May 5, 2025 · 4 comments
Open

LND Account: UI Navigation loosing basepath #1058

iBobik opened this issue May 5, 2025 · 4 comments
Labels
bug Something isn't working

Comments

@iBobik
Copy link

iBobik commented May 5, 2025

Expected behavior

I can create LND account in the UI

Actual behavior

When navigation in the UI and having litd behind the proxy in the subpath, it does not follow this basepath (/lit) and sometimes navigates to the path without the prefix.

To reproduce

  1. Install litd e.g. in the btcpayserver-docker, so it will be in the /lit path.
  2. Open /lit/connect, select Custom and click Next
  3. Blank screen on the /connect/custom
  4. Rewrote URL to the /lit/connect/custom and I can see the Custom Permissions screen
  5. Selected Custodial account, clicked Submit and dialog with some seed appeared (no idea what to do with it)
  6. Clicked OK and redirected to the /connect with blank screen
  7. Rewrote URL to the /lit/connect and I see the page with just created account (but not when I tried it first time)

System information

Using this fragment in the BtcPay Server Docker stack:
https://github.com/btcpayserver/btcpayserver-docker/blob/master/docker-compose-generator/docker-fragments/opt-add-lightning-terminal.yml

So the image: lightninglabs/lightning-terminal:v0.14.1-alpha-path-prefix

@iBobik iBobik added the bug Something isn't working label May 5, 2025
@iBobik
Copy link
Author

iBobik commented May 5, 2025

Btw I scanned the QR code of the account and it opened page like this:

Image

URL is like this, so it seems like a bug in the web app not catching the pairing request.
https://terminal.lightning.engineering/#/connect/pair/xxx

@ViktorTigerstrom
Copy link
Contributor

Hi @iBobik,

First of all, I should probably mention that I don't fully grasp the "blank screen" issues that your experiencing, as I don't experience the same issues myself when navigating through the "Custodial account" creation process with the litd UI.

But I think your main confusion comes from this step:

  1. Selected Custodial account, clicked Submit and dialog with some seed appeared (no idea what to do with it)

If you managed to get the pairing phrase to be generated, that means that you successfully created the account 🎉! I think your confusion comes with what you're supposed to do with the pairing phrase itself. I'd recommend you to read through this guide that details how accounts feature works:
https://docs.lightning.engineering/lightning-network-tools/lightning-terminal/accounts

But in a nutshell, for your usecase, this feature allows you to connect to your node over LNC, and restrict how much initial balance that LNC session should have access to. To connect to the node with the account restrictions over LNC, I suggest you pass that pairing phrase you generated in step 5. to a wallet like Alby or Zeus that allows you to connect to the node over LNC (just like the docs above suggests).

Finally I agree that it's a bit confusing that the QR code for the account session takes you to terminal.lightning.engineering, as we do not currently support connecting to accounts sessions through Terminal Web. Perhaps @jamaljsr or @jbrill could look into not showing that QR code for accounts sessions :)?

@iBobik
Copy link
Author

iBobik commented May 6, 2025

First of all, I should probably mention that I don't fully grasp the "blank screen" issues that your experiencing, as I don't experience the same issues myself when navigating through the "Custodial account" creation process with the litd UI.

Hi, lets focus on this issue, other is only about usability.

Do you run your litd with a prefixed path like it is configured in the btcpayserver-docker stack?

@jamaljsr
Copy link
Member

jamaljsr commented May 6, 2025

This appears to be a bug on the frontend side. I'll investigate and put up a fix PR if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants