You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have experienced an issue where the money receives in the lnbits but the switch is not triggered. This seem to be happening based on the Wallet which is sending the funds. In each case it worked if a wallet from the same lnbits instance is used. It also used to work but than stopped working.
A similiar case which @Mathias-U1F596 experienced on Ben's legend instance, Phoenix worked but not Wallet of satoshi.
I'm aware that this is not yet a proper bug-report. I'll continue to collect data on the phenomen but at least we have now a place to track such issues.
The text was updated successfully, but these errors were encountered:
Just adding to this, as I've encountered a similar issue.
I posted this in the maker bits chat as well.
The web socket is triggered fine if I pay with an internal lnbits wallet. Doesn’t work with any external wallet.
Watching the logs, I get one api call that’s the same: “GET /lnurldevice/api/v2/lnurl/chXxxxxxxxxxx?pin=26&amount=10.0&duration=3000 HTTP/1.1" 200
The line that follows “lnurlscan”
GET /api/v1/lnurlscan/lnurlxxxxxxxxxxx HTTP/1.1" 200
Only shows up if the request came from an internal wallet. I presume this is the error, but not sure why it would only be running the lnurlscan from an internal request and not firing when the lnurl is hit by an external wallet.
I have experienced an issue where the money receives in the lnbits but the switch is not triggered. This seem to be happening based on the Wallet which is sending the funds. In each case it worked if a wallet from the same lnbits instance is used. It also used to work but than stopped working.
A similiar case which @Mathias-U1F596 experienced on Ben's legend instance, Phoenix worked but not Wallet of satoshi.
I'm aware that this is not yet a proper bug-report. I'll continue to collect data on the phenomen but at least we have now a place to track such issues.
The text was updated successfully, but these errors were encountered: