Hey there, sorry to hear your DappNode mainnet sync got stuck at 18% with that unchanging snapshot progress—let’s walk through practical troubleshooting steps to get things moving again:

1. Start with Basic System Health Checks #

Syncing snapshots eats up resources, so first rule out hardware/resource bottlenecks:

• Log into your DappNode terminal (or use SSH) and run htop to check CPU/memory usage. If your Ethereum client (like Geth, Erigon, or Nethermind) is maxing out CPU or hitting memory limits, that could be the bottleneck. Close unused DApps to free up resources if needed.
• Check disk space with df -h. Ensure the DappNode data partition has at least 50GB of free space—snapshot processing needs temporary room, and a full disk will halt progress immediately. Delete old/unused DApp data if you’re tight on space.

2. Fix Snapshot Download/Integrity Issues #

That "Syncing snapshot" message means your client is downloading or verifying a pre-built snapshot. Stuck counts often point to corrupted files or interrupted downloads:

• Restart the client: Head to your DappNode dashboard, find your Ethereum mainnet client, and click the "Restart" button. Temporary network blips can break the download, and a restart will often re-initiate the process.
• Check client logs for errors: In the terminal, run journalctl -u dappnode-<your-client-name> -f (replace <your-client-name> with geth/erigon/nethermind) to stream real-time logs. Look for keywords like corrupted snapshot, download timeout, or peer connection failed—these will tell you exactly what’s going wrong.
• Delete partial snapshot files: If logs mention corrupted data, navigate to your client’s data directory (you can find the path in the client’s settings on the dashboard) and delete any files with .part extensions or labeled as temporary snapshot data. Then restart the client to re-download the snapshot.

3. Troubleshoot Network Connectivity #

Snapshots rely on peer-to-peer downloads, so network issues are a common culprit:

• Verify port forwarding: Ethereum clients need ports 30303 (TCP/UDP) open. Check your router settings to ensure UPnP is enabled, or manually forward these ports to your DappNode’s local IP.
• Test external connectivity: Run curl -s https://api.ipify.org in the terminal to confirm your DappNode can reach the internet. Then test peer connectivity with nc -zv eth-mainnet.prylabs.net 443—if this fails, your network is blocking outbound connections to Ethereum nodes.
• Switch snapshot sources (if available): Some clients let you toggle between official and community snapshot mirrors. Check your client’s settings in the DappNode dashboard for a "Snapshot Source" option and try switching to an alternative.

4. Reset Client Data (Last Resort) #

If all else fails, corrupted local data might be the root cause. Note: This will delete all existing sync data and require a full snapshot re-download, so only do this if other steps don’t work:

• Use the dashboard: Find your client and click the "Reset Data" button, then confirm the action.
• Manual reset (if dashboard button fails): In the terminal, delete the client’s data directory with rm -rf /mnt/dappnode/volumes/<your-client-name>/data/* (replace with your client’s path), then restart the client service with systemctl restart dappnode-<your-client-name>.

5. Update DappNode & Client #

Outdated software can have sync bugs:

• Head to the DappNode dashboard’s "Updates" page and install any available updates for the DappNode core and your Ethereum client. Reboot your DappNode after updates, then restart the sync.

内容的提问来源于stack exchange，提问作者Prakash Dale