Proxies
Test whether a proxy is alive or dead
Check a proxy before you bind it to a Cloud Phone. The proxy check reports alive or dead, plus the public IP and country the device appears from.
3 min read
Before binding a proxy to a Cloud Phone — especially one running an important account — make sure the proxy is alive and in the right location.
Check a single proxy
Open app.xcloudphone.com/dashboard/renter-proxies.
Find the proxy in the table.
Click the Check proxy icon (green check) on that row.
The Check Proxy Configuration dialog opens and runs the test automatically. When it finishes you see:
- Status — success (green check icon) or failure (red X icon).
- Proxy Location — country derived from the IP, shown on success.
- Public IP — the IP the outside world sees when traffic goes through this proxy, shown on success.
If the check fails, the dialog shows a specific error message. For unknown errors it shows "Cannot connect to proxy, may be expired or wrong proxy type."
The same check is reused inside the Add Single Proxy, Add Multiple Proxies and Edit Proxy dialogs under the name Network Detection — a proxy that does not pass the check cannot be saved at all.
Check in bulk
When you've just imported a batch of new proxies, don't test them one by one:
Tick multiple proxies in the leftmost column (or click Select all).
Click Check in the action bar (the button shows the selected count, e.g. Check (12)).
The Check Multiple Proxies dialog opens and runs the test for each proxy.
The summary line shows how many are checking, how many are live, and how many failed.
Common errors
The exact message comes from the proxy provider or the server side. A few common patterns:
| What you see | Most likely cause |
|---|---|
| "Cannot connect to proxy, may be expired or wrong proxy type." | Wrong proxy type selected (HTTP picked for a SOCKS5 proxy or vice versa), or the proxy is expired / shut down by the provider. |
| Auth / authentication error | Wrong username or password. Open Edit Proxy to fix the credentials. |
| Timeout, no response | Proxy is too slow to respond, or the xCloudPhone server's IP is blocked by the proxy provider. |
If many proxies from the same provider all time out, your server IP is probably blocked at their end — contact the proxy seller.
Check passed but the device still can't reach the internet
Sometimes a proxy passes the test but the Cloud Phone still has no internet. Quick fix:
Go to the Proxy Management page → click Unbind on that proxy's row to clear it from every session that uses it.
Go back to My Devices and re-assign the proxy to the device as described in Assign and connect a proxy.
In the viewer, click Disconnect proxy then Connect proxy again from the Actions menu.
Re-assigning and reconnecting usually forces the network config to refresh, and traffic starts flowing through the proxy again.
Build the habit of always checking a freshly imported proxy before binding it to a device that runs a valuable account. Ten seconds of testing can save you from a flagged account caused by a dead IP.
Some SOCKS5 formats may pass Network Detection here but still fail to reach the network from the device. If this happens, please contact us for help.