Compare a Lightning node's listeners with its advertised addresses
After a reverse proxy or NAT change, local peers may connect successfully while remote peers learn an outdated address. Core Lightning exposes the two address lists separately.
Read binding and announcement records
Run the query on the node whose identity peers should discover. Compare address types as well as ports. A node may listen on a private interface and announce a public endpoint.
lightning-cli getinfo | jq '{id, network, address, binding}'
Check the public path
If the advertised port is stale, inspect the announcement configuration and propagation to remote peers. A wildcard listener can be valid locally but cannot itself identify a public destination. Confirm external reachability from a host on the same transport as the advertised endpoint.