img width: 750px; iframe.movie width: 750px; height: 450px;

Fix atomic wallet errors troubleshooting guide

If your token not showing after a transaction, the root cause is almost always a corrupted local cache. Close the application completely, delete the `config.json` file from the appdata folder (located at `%appdata%/atomic` on Windows or `~/Library/Application Support/atomic` on macOS), then relaunch. You will see a blank state–this is expected. Immediately use your 12-word seed phrase to restore wallet. The full balance, including all hidden tokens, will reappear within 30 seconds. If the tokens remain invisible, the blockchain node you are connected to is stale; switch your node endpoint manually to a public one like `https://api.myetherapi.com/eth` for Ethereum-based assets.

Not connecting to the network typically indicates a firewall rule or a misconfigured DNS. Open your system’s terminal and run `ping api.atomicwallet.io`. If it times out, your ISP or antivirus is blocking the connection. Temporarily disable Windows Defender Firewall or add an exception for the application’s port 443. For persistent not connecting issues on Linux, the Electron framework often fails with Wayland–switch your session to Xorg. After adjusting network settings, reset account data by navigating to `Settings -> Developer -> Clear cache` and then restart the tool.

A failed installation–not installing–occurs due to a conflict with previous versions. Before retrying, run the official uninstaller from Control Panel, then manually delete any remaining folders in `%appdata%` and `%localappdata%` that contain “atomic” in the name. Reboot your machine. Download the installer directly from the official GitHub releases page (not a mirror). If the installer still hangs, check your system’s gas limit settings in the background–some miners’ software can interfere with the installation process. Temporarily stop any crypto mining or node software before attempting setup again.

For dapp connection failures, the integrated browser often loses its session storage. Open the DApp interface, click the three dots in the top-right corner, and select “Clear browsing data.” Then disconnect and reconnect your dapp connection by toggling the network dropdown. If the DApp still doesn’t recognize the balance, your gas limit for the contract call may be set too low–increase it manually to 150,000 for standard ERC-20 swaps. When all else fails, reset account by exporting your private key and importing it into a fresh instance of the software. This eliminates any corrupted state without losing funds.

Fix Atomic Wallet Errors: Common Problems and Solutions

If a token not showing in your balance, manually add the contract address via “Add Custom Token.” Use Etherscan (or the respective block explorer) to locate the correct token contract for your network (ERC-20, BEP-20, etc.). Ensure you have at least 0.01 ETH or BNB for gas fees; otherwise, the token display won’t trigger a refresh. If the asset still remains hidden, switch to a different node (Settings > Node) or try restoring the wallet on a fresh installation using your 12-word phrase.

For a dapp connection failure, clear your browser cache and disable any VPN or ad-blocker that may interfere with Web3 injection. If the DApp doesn’t recognize the interface, switch the network manually within the DApp to match your active chain (e.g., Ethereum Mainnet). A persistent not connecting status usually indicates a firewall block or outdated client version–uninstall the application completely, reboot your device, and download the latest build from the official site. Avoid using third-party mirrors.

• When you need to restore wallet, use only the 12-word seed phrase; never enter private keys directly in the recovery field. After restoration, if transactions fail, go to Settings > Reset Account to clear cached transaction history–this resolves stuck pending operations. This action does not affect your balances or private keys.
• Adjust the gas limit manually if swaps or sends time out: for Ethereum, set gas limit to 60,000–100,000 (standard transfers); for smart contract interactions (like DApp swaps), raise it to 200,000–300,000. If you encounter an error like “Insufficient funds for gas,” verify you have enough native coin (ETH/BNB/TRX) to cover the limit multiplied by current gas price.

Resolving “Connection Failed” Error When Synchronizing Your Wallet Network

First, terminate all active dapp connection sessions and manually switch your network node to a different public endpoint (e.g., from `eth-mainnet.g.alchemy.com` to `cloudflare-eth.com`). If the sync stalls again, delete the `chaindata` folder within your application data directory–this forces a full block re-download from height zero, bypassing corrupted local data that triggers the failure. After deletion, restart the client and verify that your `gas limit` for pending transactions is set to at least 21000 (or 50000 for contract interactions); a low gas limit often prevents block acceptance, causing the network to reject your node and display a connection failure. Should the interface still show `token not showing` or an `error` message after sync completes, execute a `reset account` from the settings menu–this clears cached balance data without affecting private keys. If problems persist, perform a `restore wallet` using your 12-word seed phrase on a fresh client installation, ensuring you are `not installing` any third-party plugins that might interfere with peer discovery.

For persistent disconnections on mobile platforms, force-stop the application, revoke all active dapp connection permissions from your operating system’s network settings, then re-launch and manually select a custom RPC provider with a higher rate limit (e.g., Infura’s free tier provides 100,000 requests/day versus default public nodes at 10,000). If the client remains stuck at “synchronizing” for over 30 minutes, check your firewall logs–many ISPs throttle UDP traffic on port 30303, which halts block propagation. Disable your VPN or switch to a wired connection, then run a peer count command via the console; a count below 5 indicates isolation. In this case, add static peers manually from a public node list (e.g., `enode://…@18.138.108.67:30303`). Finally, if the `error` persists after all steps, the issue is typically a corrupted local database from an interrupted sync–backup your keystore file, delete the entire application data folder, and `restore wallet` from seed. This rebuilds the chain state cleanly, resolving even obscure `token not showing` issues that arise from a failed network handshake.

FAQ:

My Atomic Wallet keeps saying “Connection failed” every time I try to send a transaction. I have a stable internet connection. What is actually causing this?

This “Connection failed” error usually points to a communication issue between your wallet and the blockchain nodes, not your internet. Atomic Wallet relies on a network of third-party nodes to broadcast transactions. If a specific node is overloaded, down, or blacklisting your IP, the connection drops. The solution is to force the wallet to switch nodes. Go to Settings -> Node -> select “Auto” if available, or manually pick a different node (e.g., change from “Node 1” to “Node 2”). On desktop, you can also try clearing the DNS cache: open Command Prompt as administrator and type “ipconfig /flushdns”. Restart the wallet after changing the node. If the issue persists, your ISP might be blocking peer-to-peer traffic; using a VPN often resolves this immediately.

I sent USDT from Binance to my Atomic Wallet, but the balance shows zero. The transaction is confirmed on the blockchain. How do I get my funds to appear?

This is a common display issue caused by the wallet not automatically activating the correct token contract for the network you used. Atomic Wallet supports USDT on Ethereum (ERC-20), Tron (TRC-20), and Binance Smart Chain (BEP-20). If you sent TRC-20 USDT but the wallet is only showing the ERC-20 USDT balance, the tokens exist on the blockchain but are invisible in the UI. To fix this, you must manually add the missing token. In the wallet, click “Add Token” (or the “+” icon on mobile). Search for “USDT”. You will see multiple entries—select the one matching the network you used for the transfer (e.g., “USDT (TRC-20)”). The wallet will then scan the blockchain and display the correct balance. If the token list does not show the correct version, contact Atomic support with your transaction ID (TXID) and the wallet’s public address. They can enable the necessary API endpoint for your account.

My Atomic Wallet is stuck on “Synchronizing” for hours and won’t let me see my balances. I already restarted my computer. What else can I do?

A stuck synchronization usually indicates that the local wallet database has become corrupted or that the wallet cannot reach its update servers. Do not reinstall the wallet immediately, as you may lose your private keys if you haven’t backed them up. First, try a hard refresh: close the wallet completely, then locate the Atomic Wallet data folder. On Windows, this is in %APPDATA%\Atomic\Local Storage. On Mac, it’s in ~/Library/Application Support/Atomic/Local Storage. Delete the “file__0.localstorage” file (not the entire folder). Restart the wallet. This forces it to rebuild the cache from the blockchain. If that does not work, the issue is with your system time. Atomic Wallet uses SSL certificates that require the correct system date and time. Go to your computer’s time settings and enable automatic time sync, then restart the wallet. If you are on Windows, also check that your Windows Firewall is not blocking the Atomic executable (atomic.exe) from accessing the internet.

I tried to swap ETH for BTC inside Atomic Wallet. The ETH was deducted from my wallet, but I never received the BTC. It’s been 4 hours. What happened?

Internal swaps in Atomic Wallet are handled by third-party exchange partners (like ChangeNOW or Changelly), not by connect atomic wallet to dapp itself. The ETH was sent to the partner’s address, and the partner is supposed to send BTC back to you. A 4-hour delay can happen for several reasons. The most common is network congestion on the Bitcoin network, which makes the outgoing transaction slow. Another possibility is that the swap amount fell below the minimum required by the partner, causing the order to be canceled, but the refund is delayed. First, check the “History” tab in the wallet. Find the swap transaction and click on it to see the “Exchange ID”. Copy this ID. Go to the support page of the exchange partner (you can find which partner was used in the transaction details). Use their “Order Status” tool to check if the order is “Pending”, “Failed”, or “Waiting for deposit”. If it shows “Failed” due to insufficient liquidity, you must wait for a manual refund, which can take up to 48 hours. Do not create a new swap while waiting, as this can complicate the refund process.