LND node stuck on synced_graph: false, anyone know why?

So first things first, I finished the full Bitcoin Core sync by joining NotATethers [CHALLENGE] Run A Bitcoin Node, completed all 14 days, Bitcoin Core is fully synced no issues there. Then I moved on to NotATethers GingerWallet.io | LN Quest. When you first fire up LND it shows synced_graph: false, which is normal, and it's supposed to flip to synced_graph: true after running for a while. Mine never did. Kept it running for a long time and it just stayed false the whole time. I reached out to Satofan44 and went through the LND Node tutorial, Mahiyammahi's Windows LND Node guide was also super helpful, got the node up and running fine. But when the synced_graph thing wouldn't budge I went back to Satofan44's tutorial thread to ask about it and didn't get a fix. I even added peers thinking that might sort it out. Got 3 peers connected, still nothing changed. When I run "lncli listpeers" the synced_type shows as passive and that part looks fine, but synced_graph: true just refuses to show up. Bitcoin Core is running in the background no problem, everything looks like it's working on the surface. So what's actually going on here and what should I do to get synced_graph: true? I genuinely can't figure out what's wrong when everything else seems to be running ok.

1. Try connceting multiple peers 4-5 peers at once. But in your case you did try to connect peers manually. 2. Try to run the node On Tor , and connect with some to public node. 3. You can try by connecting VPN , if your ISP firewall blocking then it will bypass it. 4. Creating a channel makes these steps faster , cause no nodes stay connected with your lnd. cause your node has no active channel.

To the best of my knowledge about the outputs you shared, your node actually looks fine Bitcoin Core is fully synced and LND is correctly synced to chain. The confusion here is around synced_to_graph which isn’t a general node health flag. It only turns true once LND has fully synced the Lightning gossip graph. For nodes with no open channels this often happens very slowly or not at all. Seeing PASSIVE_SYNC in listpeers is normal and means that gossip is flowing just passively. I’ve seen nodes stay like this indefinitely until a channel is opened after which synced_to_graph flips quickly. So from what I'm seeing, nothing here suggests a broken setup. If you need that flag to turn true (e.g. for a quest) opening a small channel is usually the fastest way.

The simplest and most effective solution is to download full Bitcoin Core node . In Pruned node dose not have old block data. Therefore, the graph is not synchronized TRUE. you will need a total of 750+gb of storage for downloading full node.   Then multiple peers will automatically connect without any hassle. It will also help easily to open channel. edited

As far as I know , it's not dependent for storage . If you check the Log files on LND , they are trying to sync the graph using the "Gossip" protocol not reading the whole blockchain. In real case scenerio what happens is The peer you're connected, they reach out to your node , if they do not find any valid channel created by your node, they do not stay connected with your node. Cause they don't send back any gossip cause you don't have any actuve channel to create any payment. So they don't interest to send you any more gossip to your node , eventually it's disconnected auto. If you wants to Bypass this and force to make your graph true try these tricks 1. Try to connect your node using Tor ( Tor peers are usually user friendly with begin with) 2. Tor provides you the anonymity 3. Try to connect multiple times with  your peer , peers are gets disconnected when they see there is no active channel on your node. 4. It's better if you open a close channel with low sats , 20k+ sats needed. 20k sats for channel and some extra sats for the txn fees.

I tried connecting with tor. I tried manually connecting . I tried different ways outside of that and even used vpn but I couldn't. It is true that it connects with tor, I saw in the challenge thread that it connected and the graph is true. But I found the easiest and most hassle-free way to do these tasks easily after running a full node. And it takes 750+gb to download full block data, I shared this as information. If he wants to run a full node, then he must have enough storage.