question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

lnurl-pay returns error 400 for both Phoenix and Breez

See original GitHub issue

Describe the bug When testing LNURL-pay with the same instance as in #3054 it returns error code 400. While it is likely it’s related to the problem there, if that is the case, the error code should be 5xy not 400 because it’s a server problem. It is possible that it’s unrelated, so I suggest to resolve #3054 first to find out. There are also no relevant logs after it fails.

To Reproduce the bug Steps to reproduce the reported bug:

  1. Setup LNURL-pay with comment allowed (other settings are default)
  2. Create an invoice
  3. Try to pay the invoice from Breez/Phoenix, enter Hello world into comment
  4. See error

Expected behavior

Either the transaction succeeds or, if there’s actually a problem with LN implementation, error 5xy is returned. 500 seems to be the most reasonable. The details of the problem are logged.

Your BTCPay Environment (please complete the following information):

  • BTCPay Server Version: 1.3.1
  • Deployment Method: Debian package
  • Browser: irrelevant (not a browser)

Logs (if applicable)

None/missing

Setup Parameters

LN node: Eclair Store Lightning settings: Enable LNURL: true LNURL Classic Mode: true LNURL enabled for standard invoices: true Do not offer BOLT11 for standard invoices: false Allow payee to pass a comment: true

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
Kixunilcommented, Jan 9, 2022

Don’t have much time lately but will try to check in upcoming days.

0reactions
Kixunilcommented, Feb 3, 2022

Sorry for it taking such a long time. I do NOT have shitcoins enabled, nevertheless I tested with 1.3.7 and still same error. Unfortunately I can’t upgrade to 1.4.* because of build issue. Looks like Microsoft messed up something in their official dotnet packages. Going to investigate.

Figured out their funny versioning, will test newest version and report.

Read more comments on GitHub >

github_iconTop Results From Across the Web

LNURL does not work with c-lightning v0.11.0 · Issue #3720
When attempting to pay a LNURL invoice using Phoenix, BTCPay displays a QR code, Phoenix will scan it and show the amount, but...
Read more >
400 BAD request HTTP error code meaning?
A 400 means that the request was malformed. In other words, the data stream sent by the client to the server didn't follow...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found