Wallet
Why won't Coconut Wallet connect to an Electrum server?
Coconut Wallet communicates with servers through the Electrum protocol. Switching a VPN on and off can temporarily disrupt routing or DNS, and a partially active VPN profile may prevent connection.
✔️ Check these first
- Confirm that the VPN is fully disabled; some profiles continue processing traffic in the background.
- Make sure no other VPN or proxy app is active.
- Reset the network: toggle Wi-Fi or Airplane Mode, then restart the device if necessary.
✔️ Connection guide
- To use Coconut's official Electrum server, disable the VPN and retry. Residual VPN settings may block or reroute TLS traffic on port 443.
- A VPN is fine when connecting to your own node, but verify routing to its private network, port, and domain.
Why can the Coconut Electrum server be unreachable abroad?
Roaming networks, local carriers, and public Wi-Fi may block Electrum traffic through captive portals, proxies, firewalls, or port restrictions. This is especially common on hotel and corporate networks that permit only web traffic or inspect TLS.
✔️ Solutions
- Open a website and complete any captive-portal login or terms prompt.
- Try toggling the VPN.
- Switch to another Wi-Fi network or mobile data.
- Temporarily disable VPNs, ad-blocking DNS, and security filters.
- Try a VPN endpoint in South Korea.
- Register and connect to your own Electrum server through its VPN.
Why can't I see a new transaction?
Coconut Wallet initially scans only 20 addresses beyond the last used address. This is the gap limit. A deposit to an address after a long sequence of unused addresses may therefore remain undiscovered.
✔️ Solution
Use your existing addresses in sequence. As the missing address falls within the gap limit, the balance will appear normally.
Increasing the gap limit would slow synchronization and waste resources, so Coconut currently follows the recommended limit of 20 while evaluating better approaches.