> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/faq/connection-issues.md). # Resolving connection issues Occasionally, you might have trouble connecting to a node while using Cake Wallet. This guide is designed to help you identify and resolve such connection problems for a smoother experience. {% hint style="info" %} First, try a quick reconnect: pull down on the home screen to make Cake Wallet reconnect to its current node. If that doesn't help, work through the steps below. {% endhint %} ## Connection status Understanding the connection status of your wallet can be the first step in resolving any issues. Below are the different types of statuses you might encounter: * **Disconnected**: A connection issue is preventing your wallet from accessing a node. * **Connecting**: Your wallet is currently initiating connection to the node, but has not yet established a stable connection. * **Attempting Sync**: Your wallet has connected to a node, and is currently exchanging information before the sync begins. * **# Blocks Remaining**: Your wallet is currently synchronizing; you should be patient and keep the wallet app open until the number reaches zero. If the number decreases very slowly or stalls, see the **Sync is slow or stuck** section below. * **No status shown**: When syncing has finished, the sync area at the top of the home screen is empty — no status text and no dot. That empty space is how you know your wallet is synced, and no further action is needed. If your wallet ever appears to be stuck at any of these steps, it's recommended to attempt the following steps. ## WiFi & data Some cellular data providers might block cryptocurrency-related connections. Similarly, some WiFi networks may be unstable or have firewalls that restrict your connection. If you're experiencing issues, try switching between WiFi and data to see if one connection type works better than the other. ## VPN It's possible that a VPN may help you to connect properly if a network firewall is blocking your connection. If you have a VPN available, it can be helpful to try enabling it. On the other hand, certain VPN providers may block or restrict access to cryptocurrency nodes, so if you are having issues connecting through a VPN, it may help to disable it. ## Nodes If your wallet is stuck at the `Disconnected` or `Attempting Sync` status, changing nodes might help. To do this: {% stepper %} {% step %} ### Open Settings Tap the gear icon at the top right of the home screen. {% endstep %} {% step %} ### Nodes Under `Wallet settings`, select `Nodes`. {% endstep %} {% step %} ### Select a node Select a new node from the list. Only nodes highlighted with a green dot will work; red dots are unavailable. Alternatively, you can [add a new custom node](https://docs.cakewallet.com/features/managing-your-wallet/manage-nodes). {% endstep %} {% endstepper %} ## Sync is slow or stuck If your wallet connects but the block count drops very slowly, stalls, or never finishes syncing — most common with Monero — try the following: * **Use a reliable node close to you.** A slow, overloaded, or distant node is the most common cause. Switch to a different node using the steps in the **Nodes** section above, or, for the fastest and most private experience, [run and connect to your own node](https://docs.cakewallet.com/features/managing-your-wallet/manage-nodes). Remember that only nodes with a green dot are reachable. * **Use a stable, unrestricted network.** A weak or filtered connection slows syncing — see the **WiFi & data** and **VPN** sections above. * **Expect the first sync to take a while.** The initial sync of an older wallet with a long transaction history is inherently slow, because the wallet has to scan every block since the wallet was created. Keep the app open and in the foreground and let it finish. * **Enable background sync (Android).** So your wallet keeps syncing even when the app isn't open, turn on [background sync](https://docs.cakewallet.com/features/advanced/background-sync). * **Switch nodes if it stays stuck.** If the block count hasn't moved for a long time, changing to another green node often gets syncing going again. {% hint style="info" %} Your funds are safe on the blockchain the whole time, no matter how far along the sync is. Syncing only affects whether your wallet can *display* and *spend* them yet. {% endhint %} ## Tor If you're ***not*** routing Cake Wallet through Tor — either with the built-in Tor option (`Settings` → `Connections` → `Enable built-in Tor`) or an external Tor proxy like Orbot — do not connect to `.onion` nodes. These nodes are designed for use through the Tor network and will not work without it. Either enable Tor, or switch to a different clearnet node. We hope this guide helps you resolve any connection issues you're facing. If you still encounter problems, please reach out to our support team for further assistance. You can contact us using the support bubble in the lower right of this page, or by using the in-app support. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cakewallet.com/faq/connection-issues.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.