pull down to refresh
0 sats \ 11 replies \ @justin_shocknet 25 Sep \ parent \ on: SN release: CLINK wallet, recent search order, improve related posts, bug fixes meta
The bigger problem would be both trying to use LND, the script installs LND as well which is probably the conflict
Alby hub is using LDK. Would there still be a conflict with LND then?
reply
Ah, LDK must be using 9735, that's the standard lightning P2P port... Maybe I can add a switch to change the default...
reply
reply
Testing this now but can't reproduce it with 9735, can you show me the error exactly?
reply
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 portAfter its up if you
cat ./lnd/lnd.conf you should see what port is is listening on, it increments so likely 9736reply
Thanks for your efforts here. This is what I got:
Have to head back out. Will try again later. I went from Lightning.Pub to Alby Hub, so previous Lightning.Pub files were still around. Seems like the install may have worked? I'll have to figure out how to get the nprofile to pop up again. I have the nprofile saved from the last time I was running Lightning.Pub but that isn't working as a source in Shockwallet. I get a "Cannot connect to source. error enrolling admin token. Nostr connection timeout" error in Shockwallet . Maybe wiping Lightning.Pub and starting from scratch with a fresh nprofile is the way to go. LND is also hanging around from the previous Shockwallet install. Wiping that and reinstalling might also help.
reply
Doh, I mistyped the cat for lnd.conf:
cat ~/.lnd/lnd.confBut yea if you installed with the old script though there may be some issues with autostart/restart of the services since that used
sudo, would want to clean those out:Stop existing services:
sudo systemctl stop lnd lightning_pub
Disable services: sudo systemctl disable lnd lightning_pub
Remove old systemd units: sudo rm /etc/systemd/system/lnd.service /etc/systemd/system/lightning_pub.service
Reload systemd: sudo systemctl daemon-reloadYou can reset the admin credentials with
rm ~/lightning_pub/admin.pub and that will create a new connect string cat ~/lightning_pub/admin.connectIf you no attachments then yea could instead
rm -rf ~/lightning_pub ~/.lnd ~/lnd to be fully clean to be sure the script makes fresh autostart services like from scratchreply