LNbits: LNURLp not working

[rene78]

I have set up a LNURLp link in LNbits but somehow I am not able to send any funds to this link. Tried to send with BlueWallet, Zeus and RaspiBlitz WebUI. The invoice format seems to be wrong.

v1.8.0 over Tor

[rene78]

Maybe somehow related to https://github.com/rootzoll/raspiblitz/issues/3129?

[rootzoll]

@fusion44 can you take a look for the LNbits team whats the problem here?

[callebtc]

Hey @rene78, please paste the LNURL here so we can check.

[rene78]

Sure! LNURL1DP68GURN8GHJ7VFEXGHRZD3C9CCZUDFC8G6NQVP39AKXUATJD3CZ7CTSDYHHVVF0D3H82UNV9UCSFF4YH7 Those are my settings, if it matters at all:

[callebtc]

The LNURL decodes to a local address which can't be reached from outside: https://192.168.0.58:5001/lnurlp/api/v1/lnurl/1

How was this usually solved with the RaspiBlitz @rootzoll or @fusion44? Should this be an onion address?

@rene78 do you use any DNS service to reach your node from the internet?

[rene78]

@rene78 do you use any DNS service to reach your node from the internet?

No DNS, I use TOR to access apps like "Ride The Lightning".

[rootzoll]

How was this usually solved with the RaspiBlitz @rootzoll or @fusion44? Should this be an onion address?

This is normally solved by adding a IP2Tor service with LNbits - so that it can be a Letsencrypt-HTTPS reachable from the outside. To retest & improve those options will get more focus again with v1.8.2 release.

[ChuckNorrison]

Found this error in my lnbits journal if i try to create a new lnurlp link.

sqlite3.OperationalError: table lnurlp.pay_links has no column named fiat_base_multiplier

Iam not using TOR, clearnet only. This looks like a version incompatibility with my existent database.

Fixed my outdated sqlite database here https://github.com/lnbits/lnbits/issues/1047

[Dehumanizer77]

I have the same problem. I have my node running on an internal network and I have a reverse proxy set up on my router which listens on clearnet IP and proxies it to lnbits on raspiblitz. However when creating a LNURL, it encodes the internal IP address into the LNURL, thus making the lnurl invalid for the outside world. If there was a way how to specify the base URL for lnurl, it would solve the problem, but I'm not sure if that is possible...

[Dehumanizer77]

Ok, for anyone with the similar problem, just use

  RequestHeader set "X-Forwarded-Proto" expr=%{REQUEST_SCHEME}
  RequestHeader set "X-Forwarded-SSL" expr=%{HTTPS}
  ProxyPreserveHost On

in the reverse proxy config for apache, or

    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-Proto $scheme;

for nginx. Then it works.

[rootzoll]

@fusion44 check if still relevent

[geco91]

recommend to push to v1.11.2