Desktop App Troubleshooting
Cannot connect to node (NET_001)
The desktop app talks to Zebrad over JSON-RPC using zebra_url in your wallet config.
- Confirm Zebrad is running (local machine, WSL, or remote VPS).
- Settings → Network — check the URL and click Test Connection.
- From a terminal:
nozy test-zebra(same config the CLI uses).
If CLI succeeds but the browser tab at http://localhost:5173 fails, you opened the Vite dev server — use the NozyWallet taskbar window instead.
Full Zebrad ↔ NozyWallet guide (WSL, Windows ports, config paths): connectivity reference.
Sync says success but send is blocked
Scan height at tip does not guarantee witness freshness. Check the sync status on Home (blocks behind, witness lag). Run Sync again and wait until witness lag is within the send guard (≤ 50 blocks).
Sync / blocks not moving
- Verify the node tip is advancing:
nozy test-zebraor rawgetblockcount. - WSL IP may change after reboot — update
zebra_urlif Zebrad runs in WSL. - Run
.\scripts\test-zebrad-nozywallet.ps1from the repo for a consolidated check (Windows).