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.

Connect to remote BTCPayServer lnd instance

See original GitHub issue

I followed the instructions to connect to a remote lnd instance but continuously got the following:

2021-05-16 13:18:35.399 [INF] LITD: Dialing lnd gRPC server at btcpay.xyz.xyz:443
2021-05-16 13:18:35.501 [INF] LITD: Listening for http_tls on: 127.0.0.1:8443
2021-05-16 13:18:35.837 [WRN] GRPC: grpc: addrConn.createTransport failed to connect to {btcpay.litservices.app:443  <nil> 0 <nil>}. Err: connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority". Reconnecting...
2021-05-16 13:18:35.837 [INF] SGNL: Received shutdown request.
error displaying startup info: error querying remote node : rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority"
2021-05-16 13:18:35.837 [INF] SGNL: Shutting down...

Expected behavior It connects successfully.

Actual behavior 2021-05-16 13:18:35.837 [INF] SGNL: Received shutdown request. error displaying startup info: error querying remote node : rpc error: code = Unavailable desc = connection error: desc = “transport: authentication handshake failed: x509: certificate signed by unknown authority”

System information

Running Lightning Terminal standalone on Mac version 11.2.3.

lnd-mode=remote

LiT v0.41-alpha from https://github.com/lightninglabs/lightning-terminal/releases

Issue Analytics

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

github_iconTop GitHub Comments

1reaction
AryanJ-NYCcommented, May 17, 2021

Ah, you’re right. The nginx reverse proxy listens on that port. So probably that just uses its own certificate that you have to specify instead of lnd’s?

This sounds right. I’ll hunt down that cert, give that a shot and get back to you. Thanks!

0reactions
jamaljsrcommented, Jul 16, 2021

Going to close this now as there hasn’t been any updates. Based on the last comment, it appears there isn’t anything here fr us to do on our end. @AryanJ-NYC feel free to reply if you are still facing this issue.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Lightning Network FAQ - BTCPay Server
How to change from c-lightning to LND or vice-versa? ... How to display my Lightning Node information so that others can connect to...
Read more >
Connecting to a lightning node remotely
BTCPayserver ; LND via the REST proxy: type=lnd-rest;server=https://mylnd:8080/;macaroon=abef263adfe... ; macaroon. xxd -plain /root/.lnd/data/chain/bitcoin/ ...
Read more >
Get started with BTCPay Server, LND and Zap Wallet - YouTube
This video is a step by step tutorial on how to get your lightning node online via BTCPay and connect to it via...
Read more >
AC# library for Lightning Network clients - GitHub
BTCPayServer.Lightning.All contains LightningClientFactory which can convert a connection string to an instance of ILightningClient .
Read more >
Is it possible to connect to BTCPay server remote c-lightning ...
Port 9735 is the lightning port. What BTCPay wants is the API. C-Lightning does not support TCP natively, but one can use socat...
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