Troubleshooting VPN prompts when using mobile data

You may occasionally see unexpected VPN prompts or errors in Atomic Wallet when performing actions like cryptocurrency swaps — even while using mobile data and with no VPN app running. This can prevent transactions from completing. This guide explains why it happens and how to resolve it.

Contents

Why your connection is detected as a VPN

Several factors can cause your device or network to be interpreted as a VPN, even when you aren't using one:

  • Mobile carrier network. Some mobile providers, particularly in certain regions, use network-level optimizations or proxies that apps can mistakenly identify as a VPN connection.
  • Security or ad-blocking apps. Apps for security, privacy, or ad-blocking often use a local VPN service on your device to filter or route traffic. Even without a traditional VPN, these can trigger VPN detection.
  • Background VPN apps. A VPN application may be running in the background without your recent activation.
  • Network glitches. Temporary network issues or misconfigurations can sometimes cause incorrect VPN detection.

How to resolve VPN prompts

If you're seeing VPN-related prompts or errors, work through these steps.

Check for active VPN connections: go to Settings → Network & internet → VPN, and disconnect any active VPN connections.

Check for active VPN profiles: go to Settings → General → VPN & Device Management → VPN, and disconnect or remove any configured VPN profiles.

Then continue with these steps, which apply to both platforms:

  1. Review security or ad-blocking apps. If you have any security suites, ad blockers, or privacy apps installed, check their settings — many use a local VPN service. Try temporarily disabling these apps or their VPN features to see if the issue resolves.
  2. Restart your device. A simple restart often clears temporary network caches and minor glitches.
  3. Try a different network. If possible, switch to a different Wi-Fi network or mobile provider. This helps determine whether the issue is specific to your current connection.
  4. Reset network settings (last resort). On Android: Settings → System → Reset options → Reset Wi-Fi, mobile & Bluetooth. On iOS: Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings.

Note: Resetting network settings will erase all saved Wi-Fi passwords and network configurations. Use this option only after the other steps have failed.

If the issue isn't VPN-related: swap troubleshooting

If the steps above don't help, or you're certain a VPN isn't involved and your swap is still failing, try the following:

  1. Ensure a stable internet connection. Confirm you have a strong, stable connection.
  2. Update Atomic Wallet. Make sure you're running the latest version from your app store.
  3. Check swap limits. Confirm your swap amount falls within the minimum and maximum limits set by the chosen exchange provider.
  4. Check funds and fees. Make sure you have enough cryptocurrency to cover both the swap amount and the network transaction fees.
  5. Try a different exchange provider. Atomic Wallet integrates with multiple third-party providers. If one fails, try the swap with a different provider in the app.
  6. Clear app cache (Android only). Go to Settings → Apps → Atomic Wallet → Storage & cache → Clear cache.

What Atomic Wallet can and cannot do

Atomic Wallet can:

  • Provide guidance and support for troubleshooting common application and network-related issues.
  • Help you identify whether a problem originates in the wallet app or from external factors.
  • Offer access to multiple integrated swap providers to increase your chances of a successful transaction.

Atomic Wallet cannot:

  • Directly control or modify your mobile carrier's network configurations or policies.
  • Disable or manage VPN applications, security software, or ad blockers installed on your personal device.
  • Bypass network restrictions or censorship imposed by your internet service provider or country.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.