-
Notifications
You must be signed in to change notification settings - Fork 58
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
Not clear how to configure hashmail when unable to bind to external IP #134
Comments
You're doing everything correctly. I think this might just be a red herring because of the
I tested it with REST but the same should be true for the gRPC interface. So maybe things work? |
I am unable to connect to from my zeus wallet via LNC using my hashmail install, it just says "failed to connect from LNC client to the proxy server". I have verified with wireshark that the connection from my phone with zeus on it is getting through to my aperture and they are having some sort of a conversation. I was wondering about "WS: socket closed: read tcp 172.16.0.10:443->:59661: use of closed network connection" , the 172 address is the local interface on the VM, its not the external interface. Not sure if that is relevant.
|
I realized that in a browser session in which I'm signed into my nodes lightning terminal, I can use my hashmail proxy to connect my node with terminal.lightning.engineering. So it seems like the proxy is working for that use case. But still no luck from my zeus wallet. |
Are you using a self-signed certificate? Maybe Zeus doesn't like that while in the browser you can add an exception and connect anyway? |
As explained here https://docs.lightning.engineering/lightning-network-tools/aperture/mailbox#docs-internal-guid-6f5d734c-7fff-7276-2045-8790bdb8ac96 , it is not possible to bind to the external IP used in many VPS setups. This is because it's behind NAT and the external IP doesn't terminate on the VM.
My question is, is it possible to use the hashmail feature of aperture with this networking setup? Part of the solution is to set
listenaddr: "0.0.0.0:443"
to bind to an externally accessible interface, but when I do this I get the following error when trying to connect via lnc:[DBG] PRXY: No backend service matched request [lightning.brodie.rocks:443/hashmailrpc.HashMail/RecvStream].
I'm guessing the problem is no service is defined for that FQDN because it is bound to 0.0.0.0 ? I looked through how to configure services but it all seems geared towards LSAT configuration, where in this case I'm only interested in setting up a hashmail proxy.
aperture.yaml used:
listenaddr: "0.0.0.0:443" debuglevel: "trace" autocert: false servername: lightning.brodie.rocks authenticator: disable: true hashmail: enabled: true messagerate: 1ms messageburstallowance: 99999999 prometheus: enabled: false
Thanks for any tips/suggestions.
The text was updated successfully, but these errors were encountered: