Hello my fellow bitcoiners, I have recently installed bitcoin core and am running a full node with both in/outbound connections. It was a pain getting inbound traffic to come through port 8333 but eventually got it to work. I am now attempting to run a lightning node (LND) on top of core with standard port 9735 connectivity, but am running into issues with "canyouseeme.org" not seeing port 9735 available for inbound traffic. It has no issues seeing 8333, just not 9735. I run lnd.exe and lncli.exe and can only connect to peers for a few seconds before they drop me. Probably due to not getting their response at where they are trying to reach me back at..which is 9735..connection initiates with the peer since outbound traffic works fine but I cannot get anything back from my peer. I have allowed port 9735 in my router(that worked for 8333) but still cannot be seen by canyouseeme.org..I ran the netstat -ano | findstr 9735 command and I can see 0.0.0.0:9735 LISTENING while lnd is running and if I close lnd and lncli.exe nothing is listening to that port and so nothing is tying it up so what gives? ISP said they can see that 9735 is set up for inbound traffic, so this is something local on my side. Maybe an issue with my config file..? I've been at it for hours and definitely need some advice. Thanks to anyone willing to help!
pull down to refresh
related posts
looks you are running those on windows. ok
did you check firewall on that windows machine?, did you open port 9735? I assume you done it for port 8333.
is that machine behind nat router? did you port forward both ports?
as @DarthCoin mentioned configuring external ip ...
if your machine is behind NAT then you should set your public IP instead local ip of your server.
bitcoinds has same config for external ip ...
Thank you for taking the time to read my post and offer assistance, I went back to my router and deleted the config allowing inbound traffic for 9735, restarted my router, then set the config back up with 9735 and reset the router one last time. I ran LND and peers auto connected to me and the same peers have been connected to me for 1hr+. I manually connected to a peer 20 minutes ago and the connection seems stable and I have not dropped. I can use lnd getnodeinfo <peerid> on the peer i manually connected too and can see their channels and even channel capacity. I believe I have fixed the issue with simply resetting the config in my router even though it was correctly set the first time(checked a hundred times pulling my hair out) I think I am good at this point, but will attempt to open a channel with my stable peer here shortly. Although I have read how lightning works I am a bit nervous to open my first channel with liquidity. I am running this on my windows 11 PC, using LND daemon cmd prompt style, no virtual machine here although I touched up on Linux in college. Do you run a lightning node, any advice for beginner opening first channel?
sorry for later response, yes I am running full btc node with lnd.
there are several options to open channel. you can use LSP - buy a channel, e.g. you pay XX sats to LSP and they open channel with you with YY sats capacity for defined time period. OR you can open channel with your sats with olympus by zeus [1] , megalithic.me
for beginning open private channel, that means that channel is not publicly visible and will be used only by you.
[1] https://amboss.space/node/031b301307574bbe9b9ac7b79cbe1700e31e544513eae0b5d7497483083f99e581
Why just for a defined time period? I though keeping a public channel open for as much time as possible helps increase trust within the network peers. Is that not true then? Does it works different for private channels?
do you have set this?
https://github.com/lightningnetwork/lnd/blob/master/sample-lnd.conf#L216
This, right?
; Adding an external IP will advertise your node to the network. This signals ; that your node is available to accept incoming channels. If you don't wish to ; advertise your node, this value doesn't need to be set. Unless specified ; (with host:port notation), the default port (9735) will be added to the ; address. ; ; NOTE: If you previously set one or more `externalip` entries and later ; remove `externalip` entirely from the config, lnd will continue to advertise ; the last known addresses from the previous run (they are stored with your node ; information). To stop advertising them, remove those addresses explicitly ; using the peers RPC/CLI, for example: ; `lncli peers updatenodeannouncement --address_remove=1.2.3.4:9735` ; A restart is not required, a new node announcement will be broadcasted.externalip=Two separate things need to be open on Windows — router and OS firewall. Port forwarding on the router is not enough.
lnd.conf settings to verify:
Without , LND won't advertise itself correctly to peers even if the port is open.
Windows Firewall (often missed):
Verify it's working:
Look for and check — your node's URI should show your public IP:9735. If that field is empty or shows , the line in lnd.conf isn't set.
The fact that 8333 works but 9735 doesn't usually means the firewall rule exists for Bitcoin Core but wasn't added for LND.