Problem with gRPC #6654

Roalkege · 2022-06-21T20:05:30Z

Roalkege
Jun 21, 2022

Background

Describe your issue here.

Your environment

version of lnd
lnd version 0.15.0-beta.rc6 commit=v0.15.0-beta.rc6-12-g8451d6155
which operating system (uname -a on *Nix)
Linux odroidn2 5.10.110-meson64 Fully integrate Onion Routing (Sphinx) #22.05.1 SMP PREEMPT Sat May 28 07:50:27 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
version of btcd, bitcoind, or other backend
neutrino
any other relevant environment details

Steps to reproduce

My .lnd/lnd.conf

`[Application Options]
alias=RoalsBlitz
debuglevel=info
maxpendingchannels=5

rpclisten=0.0.0.0:10009
restlisten=0.0.0.0:8080

wallet-unlock-password-file=path/to/file
wallet-unlock-allow-create=true

Watchtower

wtclient.active=true

Performance

gc-canceled-invoices-on-startup=true
gc-canceled-invoices-on-the-fly=true
ignore-historical-gossip-filters=1
sync-freelist=true
stagger-initial-reconnect=true
routing.strictgraphpruning=true

tor.active=true
tor.v3=true
tor.dns=nodes.lightning.directory
tor.password=superSecretPassword
listen=localhost`

I'm starting my Node with this command ./go/bin/lnd --bitcoin.active --bitcoin.mainnet --debuglevel=debug --bitcoin.node=neutrino --neutrino.connect=btcd-mainnet.lightning.computer --feeurl=btcd-mainnet.lightning.computer

Now I try to setup lndg and Zeus but I can't connect to my Node. Only Tor works but I want to use the lokal IPv4 in my home network

Expected behaviour

Tell us what should happen
The gRPC und rest port should be open and be usable.

Actual behaviour

Tell us what happens instead
Zeus and lndg are showing me errors...

Error in lndg:
An error has occured!
LNDg cannot reach the gRPC for LND. Make sure LND is running and/or your gRPC settings are correct.
Error Code: StatusCode.UNAVAILABLE

curl localhost:10009 curl: (52) Empty reply from server

guggero · 2022-06-21T20:12:43Z

guggero
Jun 21, 2022
Maintainer

Can you share some of your startup log?

What does openssl s_client -connect localhost:10009 output?

0 replies

Roalkege · 2022-06-21T20:15:43Z

Roalkege
Jun 21, 2022
Author

openssl s_client -connect localhost:10009
CONNECTED(00000003)
Can't use SSL_get_servername
depth=0 O = lnd autogenerated cert, CN = odroidn2
verify error:num=18:self signed certificate
verify return:1
depth=0 O = lnd autogenerated cert, CN = odroidn2
verify return:1
---
Certificate chain
 0 s:O = lnd autogenerated cert, CN = odroidn2
   i:O = lnd autogenerated cert, CN = odroidn2
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIDuTCCA16gAwIBAgIQWJPC2OlDcydTprq2w/c6jzAKBggqhkjOPQQDAjA0MR8w
HQYDVQQKExZsbmQgYXV0b2dlbmVyYXRlZCBjZXJ0MREwDwYDVQQDEwhvZHJvaWRu
MjAeFw0yMjA2MTYyMzM1NDlaFw0yMzA4MTEyMzM1NDlaMDQxHzAdBgNVBAoTFmxu
ZCBhdXRvZ2VuZXJhdGVkIGNlcnQxETAPBgNVBAMTCG9kcm9pZG4yMFkwEwYHKoZI
zj0CAQYIKoZIzj0DAQcDQgAEhLklDOcuqPr9AyOkwkltJtIUwG+OrXCs+q6w4wcC
qN11e+IfIQHteZB88JxSReIB4A9PK648f+wyuV4Ep3yYxaOCAlAwggJMMA4GA1Ud
DwEB/wQEAwICpDATBgNVHSUEDDAKBggrBgEFBQcDATAPBgNVHRMBAf8EBTADAQH/
MB0GA1UdDgQWBBQJFGeJAadjdFbDzaTT6zy1XNPcvjCCAfMGA1UdEQSCAeowggHm
gghvZHJvaWRuMoIJbG9jYWxob3N0ggR1bml4ggp1bml4cGFja2V0ggdidWZjb25u
hwR/AAABhxAAAAAAAAAAAAAAAAAAAAABhwTAqLIuhwSsEQABhwSsHiABhxAqAgkI
6FRyAAByYCxi2/9BhxAqAgkI6FRyAILQmVfb7asjhxAqAgkI6FRyAKNtO5QlgBkF
hxAqAgkI6FRyAIXcbnvmKwkmhxAqAgkI6FRyAK+nJoBbVLK7hxAqAgkI6FRyAIV9
4o3z8kt1hxAqAgkI6FRyAOiKP5iHlvMxhxAqAgkI6FRyAAigHdjh0GSXhxD+gAAA
AAAAAJlfHBmOEHVMhxD+gAAAAAAAAABCXv/+ntNihxD+gAAAAAAAAABC6//+xHJV
hxD+gAAAAAAAAMAs4//+g1ghhxD+gAAAAAAAANjWff/+81mWhxD+gAAAAAAAALgw
+v/+58R2hxD+gAAAAAAAANA0b//+jJ1ghxD+gAAAAAAAANyMLP/+RcGIhxD+gAAA
AAAAAGDs+f/+f/yThxD+gAAAAAAAABgYr//+q0mJhxD+gAAAAAAAAMCiAf/+cp1/
hxD+gAAAAAAAAHwAzv/+91JdhxD+gAAAAAAAALxE6P/+RSMshxD+gAAAAAAAAMyl
3v/+2S/SMAoGCCqGSM49BAMCA0kAMEYCIQDCtFCfVT4yTWDzNB71t1DxD021SOwS
ZnHbN+OFYlErLwIhAP8x1N5yxF8XKeIAq2j4HSbAS5x5UedD2Pfr2TLphiWd
-----END CERTIFICATE-----
subject=O = lnd autogenerated cert, CN = odroidn2

issuer=O = lnd autogenerated cert, CN = odroidn2

---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: ECDSA
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 1311 bytes and written 347 bytes
Verification error: self signed certificate
---
New, TLSv1.3, Cipher is TLS_AES_128_GCM_SHA256
Server public key is 256 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 18 (self signed certificate)
---
---
Post-Handshake New Session Ticket arrived:
SSL-Session:
    Protocol  : TLSv1.3
    Cipher    : TLS_AES_128_GCM_SHA256
    Session-ID: 37FB9FCA54B455D1EC321BB3099843EF0DEEB2C3EC2CBCEFBD86AFC3883F70AB
    Session-ID-ctx: 
    Resumption PSK: 4AD64D7504A16A9C3F09EA10B4F63E013A0BEF3BA354408E494DC1C6B5D7E78D
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    TLS session ticket lifetime hint: 604800 (seconds)
    TLS session ticket:
    0000 - d8 5f 91 ed c0 21 d3 6f-4d 25 d3 e4 c7 a3 c4 a1   ._...!.oM%......
    0010 - 21 16 21 af 8f 46 be 00-ff fb a6 fa ab 57 56 a6   !.!..F.......WV.
    0020 - 52 99 12 12 8b 9c 3d 4b-d6 f3 09 27 9a 28 21 88   R.....=K...'.(!.
    0030 - b4 a7 a7 97 a8 20 2b 9f-c2 2b 38 11 3f c2 23 fd   ..... +..+8.?.#.
    0040 - 39 7f 60 2b 84 4b 0e 72-98 27 3b be 42 e1 6f 15   9.`+.K.r.';.B.o.
    0050 - 99 ca e3 49 4b 09 3c c5-d8 7b d9 a0 9a 49 2e 2b   ...IK.<..{...I.+
    0060 - 1c a1 15 2d 18 83 5b 39-dd 55 f9 9c 67 50 09 6a   ...-..[9.U..gP.j
    0070 - 8d                                                .

    Start Time: 1655842414
    Timeout   : 7200 (sec)
    Verify return code: 18 (self signed certificate)
    Extended master secret: no
    Max Early Data: 0
---
read R BLOCK
@

And the startup log. Is this enough?

2022-06-21 22:14:54.312 [INF] LTND: Version: 0.15.0-beta.rc6 commit=v0.15.0-beta.rc6-12-g8451d6155, build=production, logging=default, debuglevel=debug
2022-06-21 22:14:54.312 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2022-06-21 22:14:54.313 [DBG] NTFR: ChainNotifier RPC server successfully register with root gRPC server
2022-06-21 22:14:54.313 [DBG] IRPC: Invoices RPC server successfully registered with root gRPC server
2022-06-21 22:14:54.313 [DBG] NRPC: Neutrino RPC server successfully register with root gRPC server
2022-06-21 22:14:54.313 [DBG] VRPC: Versioner RPC server successfully registered with root gRPC server
2022-06-21 22:14:54.313 [DBG] SGNR: Signer RPC server successfully register with root gRPC server
2022-06-21 22:14:54.313 [DBG] WLKT: WalletKit RPC server successfully registered with root gRPC server
2022-06-21 22:14:54.313 [DBG] RRPC: Router RPC server successfully register with root gRPC server
2022-06-21 22:14:54.313 [INF] RPCS: RPC server listening on 0.0.0.0:10009
2022-06-21 22:14:54.323 [DBG] NTFR: ChainNotifier REST server successfully registered with root REST server
2022-06-21 22:14:54.325 [DBG] IRPC: Invoices REST server successfully registered with root REST server
2022-06-21 22:14:54.325 [DBG] NRPC: Neutrino REST server successfully registered with root REST server
2022-06-21 22:14:54.325 [DBG] VRPC: Versioner REST server successfully registered with root REST server
2022-06-21 22:14:54.326 [DBG] SGNR: Signer REST server successfully registered with root REST server
2022-06-21 22:14:54.327 [DBG] WLKT: WalletKit REST server successfully registered with root REST server
2022-06-21 22:14:54.329 [DBG] RRPC: Router REST server successfully registered with root REST server
2022-06-21 22:14:54.330 [INF] RPCS: gRPC proxy started at 0.0.0.0:8080
2022-06-21 22:14:54.330 [INF] LTND: Opening the main database, this might take a few minutes...
2022-06-21 22:14:54.330 [INF] LTND: Opening bbolt database, sync_freelist=true, auto_compact=false
2022-06-21 22:14:54.352 [INF] LTND: Creating local graph and channel state DB instances
2022-06-21 22:14:54.377 [DBG] CHDB: Populating in-memory channel graph, this might take a while...

0 replies

guggero · 2022-06-21T20:18:25Z

guggero
Jun 21, 2022
Maintainer

Looks like lnd's gRPC server is fully up and serves the correct cert. So it sounds like a problem between LNDg and lnd. Is there a firewall inbetween?

EDIT: Also, what IP do you use when connecting from LNDg?

0 replies

Roalkege · 2022-06-21T20:21:14Z

Roalkege
Jun 21, 2022
Author

There is no firewall inbetween and everything is on the same device.

To open LNDg in my browser I open http://192.168.178.46:8889/

0 replies

guggero · 2022-06-21T20:23:19Z

guggero
Jun 21, 2022
Maintainer

No, I mean what IP/port do you configure in LNDg to reach lnd?

Moving this over to a discussion, doesn't look like a problem with lnd. Please also consider using our Slack channel for troubleshooting.

3 replies

Roalkege Jun 21, 2022
Author

Ohh the link is dead.

guggero Jun 21, 2022
Maintainer

Argh... The links expire after a certain time. We'll create a new one, sorry about that.

guggero Jun 21, 2022
Maintainer

Here's one that will expire in 30 days: https://join.slack.com/t/lightningcommunity/shared_invite/zt-1b92krgus-w60t9rZ7bnFdy0~4acj~ew

Roalkege · 2022-06-21T21:13:36Z

Roalkege
Jun 21, 2022
Author

No, I mean what IP/port do you configure in LNDg to reach lnd?

Moving this over to a discussion, doesn't look like a problem with lnd. Please also consider using our Slack channel for troubleshooting.

python initialize.py -net 'mainnet' -server 'localhost:10009' -d && supervisord && python manage.py runserver 0.0.0.0:8000

So I use localhost and 10009... I also tried 127.0.0.1

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Problem with gRPC #6654

{{title}}

Replies: 6 comments 3 replies

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Problem with gRPC #6654

Roalkege Jun 21, 2022

Background

Your environment

Steps to reproduce

Channel settings

Watchtower

Performance

Expected behaviour

Actual behaviour

Replies: 6 comments · 3 replies

guggero Jun 21, 2022 Maintainer

Roalkege Jun 21, 2022 Author

guggero Jun 21, 2022 Maintainer

Roalkege Jun 21, 2022 Author

guggero Jun 21, 2022 Maintainer

Roalkege Jun 21, 2022 Author

guggero Jun 21, 2022 Maintainer

guggero Jun 21, 2022 Maintainer

Roalkege Jun 21, 2022 Author

Roalkege
Jun 21, 2022

Replies: 6 comments 3 replies

guggero
Jun 21, 2022
Maintainer

Roalkege
Jun 21, 2022
Author

guggero
Jun 21, 2022
Maintainer

Roalkege
Jun 21, 2022
Author

guggero
Jun 21, 2022
Maintainer

Roalkege Jun 21, 2022
Author

guggero Jun 21, 2022
Maintainer

guggero Jun 21, 2022
Maintainer

Roalkege
Jun 21, 2022
Author