A node that will not sync or cannot find peers is almost always suffering from one of a small handful of fixable problems. Work through these steps in order and you will find the cause without guesswork. Stay calm; a stuck node rarely means lost data.
Step 1: Confirm the node is actually running
Check that the node process is alive and that you are reading current output, not a stale window. It sounds obvious, but a node that silently exited will of course make no progress. Restart it and watch the fresh startup messages.
Step 2: Check your internet connection
Verify the machine itself can reach the internet by loading any website or pinging a known host. If the machine has no connectivity, the node cannot find peers. Fix the underlying network before blaming the node.
Step 3: Look at the peer count
Inspect how many peers the node has. Zero peers points to a connectivity or discovery problem. A few peers but no progress points to something else. The peer count is your single most useful diagnostic.
Step 4: Rule out a firewall or blocked outbound
Some restrictive networks block the outbound connections a node needs. If you are on such a network, the node may fail to reach any peers. Test on a different network if you suspect this, or adjust the local firewall to allow the node outbound.
Step 5: Check free disk space
A drive with no free space halts the sync immediately. Confirm the data drive still has room. If it is full, free space or move the data directory to a larger drive, then restart.
Step 6: Verify the system clock
A badly wrong system clock can cause a node to reject blocks or behave oddly, since timestamps matter to validation. Make sure the machine time is accurate and syncing automatically.
Step 7: Restart from the last good state
If everything checks out, stop the node cleanly and start it again. It resumes from the last verified block. If the data directory is corrupted - usually from a power loss or a full disk - you may need to clear it and resync, which is a last resort, not a first move.