I'm having a very weird issue and I'm not sure exactly where/what is the cause, I have a public LND node in a rpi and an digital ocean droplet connected to the rpi by rpc, it's always working perfect by lncli in the remote digital ocean box, also I have configured another linux box on the same local network where the rpi is located.
In the remote digital ocean linux droplet I have an nodejs app that connects to the LND node by lnd-async package and it's make successful connections with the node perfectly and very fast but each period of time it stops working, I created an specific api endpoint that make a getInfo call to monitorize it when the problem starts again, I'm testing with curl directly from the command line and after 2 minutes I just get this message
curl: (52) Empty reply from server
The same nodejs app I have it on my workstation in the same local network where the LND is located, and it never get connection issues with the LND node, always is working fine, even when the digital ocean stop receiving response.
As I mention before this problems "solves" after some period of time, I still don't know why, and if I restarted the nodejs app.
rpi:
lnd version 0.4.2-beta commit=7cf5ebe2650b6798182e10be198c7ffc1f1d6e19
lnd-async 1.3.1
nodejs v10.6.0 (on both linux clients)
Do you know how I can find this root cause? any ideas?
I'm having a very weird issue and I'm not sure exactly where/what is the cause, I have a public LND node in a rpi and an digital ocean droplet connected to the rpi by rpc, it's always working perfect by lncli in the remote digital ocean box, also I have configured another linux box on the same local network where the rpi is located.
In the remote digital ocean linux droplet I have an nodejs app that connects to the LND node by lnd-async package and it's make successful connections with the node perfectly and very fast but each period of time it stops working, I created an specific api endpoint that make a getInfo call to monitorize it when the problem starts again, I'm testing with curl directly from the command line and after 2 minutes I just get this message
curl: (52) Empty reply from server
The same nodejs app I have it on my workstation in the same local network where the LND is located, and it never get connection issues with the LND node, always is working fine, even when the digital ocean stop receiving response.
As I mention before this problems "solves" after some period of time, I still don't know why, and if I restarted the nodejs app.
rpi: lnd version 0.4.2-beta commit=7cf5ebe2650b6798182e10be198c7ffc1f1d6e19 lnd-async 1.3.1
nodejs v10.6.0 (on both linux clients)
Do you know how I can find this root cause? any ideas?