I hope this is the appropriate place to ask this.
I’m building a web app that is using an lnd instance to facilitate payments via the lightning network. When I run my node app on my laptop that is connected to the same network as my rpi4 running Umbrel i am able to access my node via
umbrel.local:10009
. However, since my web app is deployed in the cloud I need to access my node from outside via <my-public-ip>:10009
. In other words I need to publicly expose my lnd’s gPRC port.im using alexbosworth's ln-service
The problem is i am unable to reach my node…
-
my router does forward
:10009
to my rpi4’s static ip -
telnet
<my-public-ip>:10009
DOES yield a response -
my deployments domain IS listed as an entry the
tlsextradomain
-
rpclisten
IS configured as0.0.0.0
-
externalip
IS set to<my-public-ip>
-
im starting to suspect that this issue has to do with dockers default network and it is not letting any traffic outside the default network reach any container.
i provided a little sketch to make it really clear:
![](https://i.ibb.co/SVdqR0t/Untitled-11.png)
tlsextradomain
in thelnd.conf
file, you need to regenerate thetls.cert
so it has the latest values included. Restarting LND should do the trick (I believe there also might be an LND command for this)-p <external-ip>:10009:10009
to expose it externallytelnet <public-ip>:10009
can i assume that this is actually reaching my lnd? Is A response the RIGHT response or is there a RIGHT response apart from A response or NO response?tlsextraip
andtlsextradomain
supposed to be listed in the decoded dataset somewhere?tlsextraip
andtlsextradomain
config entries should appear in the 'SAN' subject in the certificate. If they are not there, your app will not be able to perform the necessary SSL handshake.lnd.conf
entries when generating the cert. waiting for the reply...