My Wallet Won't Sync

You open your wallet and the balance is missing, the progress bar is crawling, or a message says the wallet is "out of sync." It is one of the most common Monero support questions — and one of the least dangerous. Your funds are not affected by a sync problem; the wallet simply cannot see them clearly yet. This lesson explains how syncing works and walks through the usual causes and fixes so you can get back to a green, up-to-date wallet.

What Syncing Actually Does

Your Monero wallet does not store your balance as a number sitting on a server. Instead, it scans the blockchain, block by block, looking for outputs that belong to you. Only after it has scanned up to the latest block can it show your correct balance and full history. "Syncing" is this scanning process. When your wallet is behind the current block height, it is still working through blocks it has not checked yet.

Where the Blocks Come From: Node vs Own Node

To scan, your wallet needs blockchain data from a node (the daemon software). You have two options:

• A remote node — someone else's node your wallet connects to over the internet. Fast to start, but you depend on that node being online and responsive.
• Your own node — you run the daemon yourself. It must first download and verify the whole blockchain, which takes time, but afterwards syncing wallets is fast and fully private.

Which one you use strongly affects the sync experience. See Running or Choosing a Node to decide what suits you.

Connection and Daemon Issues

If the wallet will not sync at all, the problem is usually the connection to the node rather than the wallet itself. Common culprits:

• The remote node is offline or overloaded, so your wallet cannot fetch blocks.
• Your own daemon is not fully synced yet, so it has no recent blocks to give the wallet.
• A firewall, VPN, or network filter is blocking the connection.
• The wallet is pointed at the wrong address or port for the node.

"Daemon Is Busy" and Similar Messages

A message like daemon is busy or no connection to daemon usually means the node you are talking to is not ready to answer — often a fresh remote node still catching up, or your own daemon still verifying blocks. This is typically temporary. Wait a little, then retry. If it persists on a remote node, the node itself may be struggling, and switching nodes is the quickest fix.

Switching Nodes

If a remote node is slow or unresponsive, changing to a different one often solves the problem instantly. In your wallet's settings, look for the node or daemon configuration and either select a different node from the list or enter a new one. After switching, give the wallet a moment to reconnect and resume scanning. Trying two or three nodes is a normal, healthy troubleshooting step.

Why the First Sync Can Be Slow

The very first sync of a new or restored wallet is the slowest, because there may be a large range of blocks to scan. Things that make it faster:

• A correct restore height so the wallet skips blocks from before the wallet existed — a wrong height is a frequent cause of both slow scans and confusing balances, covered in I Restored My Wallet but the Balance Is Zero.
• A fast, well-connected node, ideally your own on the same machine.
• Leaving the device awake and connected rather than repeatedly closing the app.

A Calm Troubleshooting Order

1. Wait a few minutes. Short delays and small gaps close on their own.
2. Check your internet and any VPN or firewall that might block the node.
3. Switch to a different node if the current one is slow or unreachable.
4. If you run your own node, confirm the daemon is fully synced before expecting the wallet to be.
5. Restart the wallet to force a fresh connection and resume scanning.

Throughout all of this, remember: your coins live on the blockchain, not in the app, so a sync hiccup never puts them at risk. Once your wallet is synced and reading balances correctly, a good next step is learning why a freshly received amount may still show as locked, which we explore in Locked vs Unlocked Balance.