pull down to refresh
I got it working. I was hesitant to stop the AlbyHub LDK node as I wanted to avoid downtime there, but I decided to bite the bullet and do that.
After that, Lightning.Pub installed fine.
Afterwards, I couldn't start AlbyHub again as I got the following error:
{"error":"listen tcp :8080: bind: address already in use","level":"error","msg":"echo server failed to start"}
My guess is this is the conflict which was preventing Lightning.Pub from starting properly when AlbyHub was already running.
If I again start AlbyHub first, and try the fresh Lightning.Pub install, I get the same result. "Can't retrieve wallet status". Screenshot at bottom. It did have the "Port 9735 is in use. Checking next port..." line, but, that must not have been the only issue.
Heading back to AlbyHub for now as I have other family members using it, but, I'll get another machine going at some point to test out Lightning.Pub. Or, if you have other ideas how to make them both work without wasting too much of your time, we could take that offline as well. Thanks for your help!
reply
ah.. 8080... that's a REST port for LND, either LDK or Alby must also use it...
I think adding a line to lnd.conf should be enough to remedy that though
restlisten=localhost:8080then restart services
systemctl --user restart lnd && systemctl --user restart lightning_pubFor testing things on this same machine more generally though, you may want to look into using VMs for isolation. Assuming you've got memory to spare you can boot up full operating systems with virt-manager:
That's actually how I test/dev across OS's/Architectures
If resources are a little more scarce there's also linux containers, sort of like docker in that it's lightweight, but a little easier to use like a VM. Ubuntu actually maintains the tooling for these:
reply
systemctl --user status lnd