pull down to refresh

17 sats \ 6 replies \ @ACYK 14h \ parent \ on: SN release: CLINK wallet, recent search order, improve related posts, bug fixes meta
I meant to circle back and try Lightning.Pub to see how it was progressing, but the easiest device to do that on is an Ubuntu machine that is already running Alby Hub. With the one line install there are port conflicts. Since running Alby Hub is fairly common, is there any way to get a one line install that uses alternate ports and doesn’t interfere with Alby Hub?
write
preview
0 sats \ 5 replies \ @justin_shocknet 13h
The bigger problem would be both trying to use LND, the script installs LND as well which is probably the conflict
reply
17 sats \ 4 replies \ @ACYK 13h
Alby hub is using LDK. Would there still be a conflict with LND then?
reply
100 sats \ 3 replies \ @justin_shocknet 13h
Ah, LDK must be using 9735, that's the standard lightning P2P port... Maybe I can add a switch to change the default...
reply
17 sats \ 2 replies \ @ACYK 12h
That’d be great
reply
0 sats \ 1 reply \ @justin_shocknet 9h
Testing this now but can't reproduce it with 9735, can you show me the error exactly?
reply
0 sats \ 0 replies \ @justin_shocknet 7h
I think I got it, merging now...
The new change will check if the port is occupied before installing LND and then bump it
Take it for another spin, should work over the existing failed install, but if not just stop the hung lnd first systemctl --user stop lnd so the script can confirm its not lnd hogging the port
After its up if you cat ./lnd/lnd.conf you should see what port is is listening on, it increments so likely 9736
reply