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.

Payment failed: UNIMPLEMENTED HTTP status code 404

See original GitHub issue

I could not pay an invoice on the app.

Description

UNIMPLEMENTED: HTTP status 404 invalid content-type: null
trailers:
Metadata(:status=404,server=nginx,content-length=0,referrer-policy=same-origin,x-xss-protection=1;mode=block;x-content-type-options=DENY,strict-transport-security=max-age=31536000)

Steps to Reproduce

  1. Access BTCPayServer via IPV4.
  2. Services > LND (gRPC server).
  3. Scan the QR Code on ZapWallet.
  4. Attempt to pay an invoice.

image

Environment

  • Zap version: 0.4.0-beta, build: 3027
  • Android version: Android 11 API 30
  • Device: Mi A3
  • LND Version: 0.11.0-beta
  • BTCPayServer version: 1.0.7.1

Issue Analytics

  • State:open
  • Created 2 years ago
  • Comments:9

github_iconTop GitHub Comments

1reaction
michaelWuenschcommented, Oct 5, 2021

Hey guys, now that 3 of you are affected, I can at least see a pattern. It seems to be definetly related to using Zap with BTCPAYServer. But unfortunately I still have no clue so far why this happens.

1reaction
michaelWuenschcommented, Apr 3, 2021

Hm, okay this means, the UNIMPLEMENTED error is caused by the SendPaymentV2 RPC call. “UNIMPLEMENTED” normally comes if the RPC call is not available/implemented on the lnd node you are running. The strange thing is that lnd 0.11.0-beta includes the SendPaymentV2. I tested it on regtest with 0.11.0 nodes and it worked. I do not have (or ever used) a BTCPay setup though.

The change for the payment flow was made in the last update (Zap Android 0.4.0-beta) where I replaced the deprecated functions.

Updating your LND node might help. If you don’t want to do that, I would suggest to downgrade to Zap Android v0.3.8-beta version from the github releases in the meantime. (https://github.com/LN-Zap/zap-android/releases) Once you have updated your lnd, you can give the newest version of Zap Android a try again.

So far I have only heard of this issue with LND v0.11.0. If anyone with a newer version has the same issue, please write a comment here.

Read more comments on GitHub >

github_iconTop Results From Across the Web

HTTP Status Code 404 or 501 when Operation is not ...
A 501 means the HTTP server itself has a particular feature not implemented that is require to fulfill the request - i.e. it...
Read more >
This is not the HTTP method you're looking for, HTTP status ...
The 404 (Not Found) status code indicates that the origin server did not find a current representation for the target resource or is...
Read more >
10 Error Status Codes When Building APIs For The First Time ...
404 Not Found​​ This is by far the most common HTTP status code you can get. It indicates that the URL you used...
Read more >
GRPC Core: Status codes and their use in gRPC
Code Number Description OK 0 Not an error; returned on success. FAILED_PRECONDITION 9 OUT_OF_RANGE 11
Read more >
501 Not Implemented - HTTP - MDN Web Docs
The HyperText Transfer Protocol (HTTP) 501 Not Implemented server error response code means that the server does not support the ...
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