Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to use gRPC from external and REST from same machine at the same time #2801

Closed
turcane opened this issue Mar 19, 2019 · 1 comment
Closed

Comments

@turcane
Copy link
Contributor

turcane commented Mar 19, 2019

Background

When trying to use gRPC from outside and REST from the same machine at the same time REST calls does not work.

Your environment

  • lnd version 0.5.2-beta commit=v0.5.2-beta
  • Linux rv1025 3.13.0-108-generic Update format of lncli getinfo response #155-Ubuntu SMP Wed Jan 11 16:58:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  • Ubuntu 16.04.6 LTS
  • Bitcoin Core Daemon version v0.17.1 (bitcoind)

Steps to reproduce

  1. Configure lnd.conf
restlisten=localhost:19925
rpclisten=0.0.0.0:10009
tlsextraip=a.b.c.d
externalip=a.b.c.d
  1. Delete certificate
  2. Restart lnd to create new certificate
  3. Use external application/wallet to connect to lnd via gRPC with admin.macaroon and tls.cert
  4. Use internal (running on the same machine like lnd) application/wallet to connect to lnd via REST
  • external client can be a wallet like zap, pebble, shango, etc.
  • for internal client RTL was used (Ride The Lightning)

Expected behaviour

Step 4 and 5 should work.

Actual behaviour

Step 5 does not work.

All Subconns Are In Transientfailure, Latest Connection Error: Connection Error: Desc = "Transport: Authentication Handshake Failed: X509: Certificate Is Valid For 127.0.0.1, ::1, a.b.c.d, 172.17.0.1, xxx::xxxx:xxxx:xxxx:xxxx, Not 0.0.0.0"

RTL is running on the same machine like lnd and it's configured to access it via https://localhost:19925/v1

@wpaulino
Copy link
Contributor

This has been fixed in master (#2247) and will be included in the next release. See #1567 (comment) for a temporary workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants