Potential issue with local LNURLp extension

[n-e-t-d-i-v-e-r]

Hi there, not sure if it’s an issue or only a bad configuration of my local LNbits environment.

But if I install the extension LNURLp on any local server (raspibolt) and cofigure and generate an invoice QR-code, i’ll always get following error message, if I will spend some sats over any lightning wallet:

«Error: Failed to decode invoice, please try again» or «This dosen’t do be a lightning invoice»

in the meantime i have compared the LNURLp QR code with a legend LNbits invoice. it is all the same except for one exception. with the legend invoice the wallet ID is a number, with my local LNbits wallet the ID consists of letters. as i understand it, this could be the problem that triggers the error message.

and if yes, how can I fix that?

@arcbtc

Rest of my config seems to be right and working. I used this manual: https://raspibolt.org/guide/bonus/lightning/lnbits.html

[dni]

i think its fine, numbers are the legacy. it was numbers before the migrations to small id's. both should work? but you can try to delte it and create a new one and it should be all IDs

[n-e-t-d-i-v-e-r]

delete what? the LNURLp-code and generate a new one? I tried this since many times, with always the same result.

also uninstalled and reinstalled the LNURLp extension, same error ...

but all the rest is working fine. strange ...

[dni]

the ID: 1231 < was the old IDs for lnurlp links created before 6 months ago the ID: xfdsa < id created since then

[n-e-t-d-i-v-e-r]

OK, thanks for clarification. but why i’ll get an error-message, with this QR from my local server, when scanning with phoenix-wallet? maybe, because LNURLp is behind tor?

[n-e-t-d-i-v-e-r]

the issue was and is, that phoenix wallet can’t handle LNurl. tests with blueWallet were successful.