[Bug]: LNBank and LNDHub (via lnbits extension) Stopped to work #4482
Comments
|
LNbank needs to be upgraded to v1.3.8 — you can do so on the "Manage Plugins" page. For LNDhub via LNbits: We discussed the issue in lnbits/lnbits#1182 and LNbits just doesn't offer full LNDhub API-compatibility, so that we cannot integrate it. |
dennisreimann
added a commit
to dennisreimann/btcpayserver
that referenced
this issue
Jun 17, 2023
The LNDhub-compatible implementation by LNbits does not support the `GetInfo` call for all their funding sources — see lnbits/lnbits#1182. By catching that exception in combination with the `LndHubLightningClient`, we give people the ability to still use their LNbits-based LNDhub as a Lightning node. Fixes btcpayserver#4482.
NicolasDorier
pushed a commit
that referenced
this issue
Jun 20, 2023
* Lightning: Relax GetInfo constraint for LNDhub connections The LNDhub-compatible implementation by LNbits does not support the `GetInfo` call for all their funding sources — see lnbits/lnbits#1182. By catching that exception in combination with the `LndHubLightningClient`, we give people the ability to still use their LNbits-based LNDhub as a Lightning node. Fixes #4482. * Update approach to handling unsupported GetInfo calls
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is your BTCPay version?
I'm running BTCPayServer 1.7.13
How did you deploy BTCPay Server?
Running on MynodeBtc via Docker
What happened?
After upgrade to version 1.7.13 all stores with wallets using LNBits LNDHub Extension or LNBank stopped to work.
How did you encounter this bug?
When you create a store, and setup a lightning wallet to use LNBank wallet or a LNBits wallet (via LNDHUb extension), BTCPayServer shows the node as offline and it can't generate invoices.
No Idea how to fix. I think is a bug!
Any help is welcome!
Relevant log output
No response
What browser do you use?
No response
Additional information
No response
Are you sure this is a bug report?
The text was updated successfully, but these errors were encountered: