Why is my Monero wallet not syncing?

Common causes: (1) Remote node is down or overloaded — try a different node from monero.fail or node.moneroworld.com. (2) Internet connection issues — Monero wallets need sustained connections, try a wired connection. (3) Firewall blocking port 18081 (or 18089 for restricted RPC) — allow outbound connections. (4) Wallet version outdated — download the latest version. (5) Tor connection timing out — try without Tor first to isolate the issue. (6) Blockchain database corrupted — delete and re-sync (monerod only).

Why does my Monero wallet show wrong balance?

The wallet hasn't finished scanning the blockchain. Monero must scan every block from your wallet's creation date (restore height) to find your transactions. Solutions: (1) Wait for sync to complete — check the progress bar or block height. (2) Set correct restore height — if too high, you'll miss older transactions. (3) Rescan blockchain — in Feather: Wallet → Rescan spent outputs. In CLI: 'rescan_bc'. In GUI: Settings → Info → Rescan wallet balance. (4) Check you're connected to a synced node — 'status' in monerod should show current block height.

My Monero transaction is stuck — what do I do?

Monero transactions typically confirm in 2 minutes (1 block). If stuck: (1) Check the transaction on a block explorer (xmrchain.net) using the TX hash. If it shows 'pending' in the mempool, wait — it will be included in the next block. (2) If not in the mempool, the transaction may have been rejected — try resending. (3) Low fee (shouldn't happen with default settings) — wallets auto-calculate fees. (4) If the receiving wallet shows 0, they need to wait for 10 confirmations (~20 min) for the balance to become spendable.

How do I fix Monero connection errors?

Connection errors mean your wallet can't reach a Monero node. Fixes: (1) Try a different remote node — monero.fail lists working nodes with uptime status. (2) Check your internet — can you browse the web? (3) Disable VPN temporarily — some VPNs block crypto traffic. (4) If using Tor: try clearnet first to isolate. Feather Wallet has one-click Tor toggle. (5) If running your own node: check 'monerod status' — is it synced? Is port 18081 open? (6) Firewall: allow outbound TCP to port 18081 (default) or 18089 (restricted).

How do I set the correct restore height?

Restore height tells the wallet which block to start scanning from. Too high = missed transactions (wrong balance). Too low = slower sync (scans unnecessary blocks). Finding it: (1) If you know the date you created the wallet, use a restore height calculator (e.g., on the Monero GUI restore page). (2) If unsure, use 0 — this scans the entire blockchain (slowest but finds everything). (3) Rule of thumb: Monero produces ~720 blocks/day. If wallet was created Jan 2025, use approximately block height from that date. (4) For wallets created after 2020: set height 30 days before your first expected transaction.

Monero Wallet Troubleshooting (2026)

Fix sync problems, wrong balances, and stuck transactions

TL;DR: Most wallet issues are sync problems. Try a different remote node from monero.fail first. If balance is wrong, rescan the blockchain. If a TX is stuck, check xmrchain.net — it's probably just waiting for confirmations. Running your own node eliminates 90% of connection issues.

Quick Diagnosis

Symptom	Likely Cause	Fix
Wallet won't sync	Node down / unreachable	Switch to different node (monero.fail)
Balance shows 0	Sync incomplete or wrong restore height	Wait for sync; set correct restore height
Balance too low	Restore height set too high	Lower restore height, rescan
TX stuck "pending"	Normal — waiting for block	Wait 2-20 min for confirmations
"Connection refused"	Firewall or VPN blocking	Allow port 18081; disable VPN
"Daemon not connected"	Node crashed or unreachable	Restart monerod or switch node
Funds "locked"	Awaiting 10 confirmations	Wait ~20 min after receiving
Wallet opens but hangs	Large wallet file, slow disk	Move to SSD; increase cache

Fix: Wallet Won't Sync

Step 1: Try a different remote node. Go to monero.fail and pick a node with high uptime. In Feather: Settings → Node → Auto-connect. In GUI: Settings → Node → Remote node.

Step 2: Check your internet. Can you load web pages? Monero needs sustained TCP connections — flaky WiFi causes sync failures.

Step 3: Disable VPN temporarily. Some VPN providers block cryptocurrency traffic on certain servers.

Step 4: If using Tor, try clearnet first. Tor nodes can be slow or unreliable. Feather Wallet has a one-click Tor toggle.

Step 5: Update your wallet. Older versions may not support the current network protocol.

Fix: Wrong Balance

Wallet	Rescan Command
Feather	Wallet → Rescan spent outputs
GUI	Settings → Info → Rescan wallet balance
CLI	`rescan_bc` (rescans from restore height)
Cake	Settings → Resynchronize
Monerujo	Long-press wallet → Rescan blockchain

If rescan doesn't fix it: Your restore height may be wrong. Set it to a block before your first transaction. Use 0 as last resort (scans entire chain — slow but guaranteed).

Fix: Stuck Transaction

1. Copy the TX hash from your wallet's transaction history.

2. Check it on xmrchain.net (or any block explorer).

3. If it shows in the mempool: it's waiting for a miner to include it. Normal wait: 2 minutes.

4. If it shows confirmed: the receiving wallet needs to sync. They'll see it once synced.

5. If it doesn't exist: the TX was never broadcast. Close and reopen your wallet. Try sending again.

Wallet-Specific Tips

Wallet	Common Issue	Solution
Feather	Tor connection slow	Toggle Tor off in settings to test clearnet
GUI	"Waiting for daemon"	Start monerod separately; check it's synced
Cake	Balance discrepancy	Settings → Resynchronize; check node region
Monerujo	"Node not responding"	Switch to a .onion node or clearnet node
CLI	Slow scan	Use `set refresh-from-block-height N`

The Nuclear Option

If nothing works: restore from seed phrase. Create a new wallet file using your 25-word seed phrase. Set restore height to the block before your first transaction. Let it sync completely.

This fixes 99% of wallet problems because it rebuilds the wallet database from scratch using the blockchain as the source of truth.

Running your own node eliminates connection problems entirely. Pruned node needs only ~70GB — fits on a 256GB SSD.