391 sats \ 5 replies \ @sudocarlos 24 Sep \ on: How to Connect your LN node to SEND/RECEIVE sats to/from SN via NWC with AlbyHub lightning
One more suggestion - open a channel to @sn.
Node > open channel > advanced options > channel peer (dropdown) select custom > in peer text box, copy paste the pubkey at the bottom of @sn and remove "@52.5.194.83:9735" > click next > follow instructions for funding the channel.
Enjoy minimum fees when sending/receiving with sn and your alby hub.
write
preview
42 sats \ 4 replies \ @eroc1990 24 Sep
When you created your channel, did you need to provide a host:port? Do we just use the @ info that we removed for the pubkey?
reply
0 sats \ 3 replies \ @sudocarlos 24 Sep
Just the pubkey. ip:port arent necessary. The connect textbox/copy string at the bottom of @sn includes the ip address and port and those should be removed.
When you first copy/paste the string it will reveal another text box for ip:port because it cant automatically parse the string in the pubkey field, but this disappears once the pubkey field is only a recognized pubkey.
reply
100 sats \ 2 replies \ @eroc1990 24 Sep
I must be doing something wrong, then. Not only does my Hub (ver. 1.9.0) want me to provide that port, but it keeps spinning when I do try to open a channel. Any channel, not just w/ @sn.
Thank you, though. I'll keep digging.
EDIT: Figured it out. My Pihole was blocking mempool.space from one of the blocklists I have configured. Unblocked that and all is well with the world.
reply
0 sats \ 1 reply \ @sudocarlos 24 Sep
The guys at alby are pretty helpful in their discord channel. Hit them up if you want their support
reply
100 sats \ 0 replies \ @eroc1990 24 Sep
I'll 100% hop in if I get stuck (I might be already and just don't remember tbh lol). But yeah, this time it was DNS. It's always DNS.
reply