Set up and verify your PhoneFarm proxy connection

Your PhoneFarm phone has its own internet connection. The proxy configuration belongs to that phone, even though you enter it through a browser on your computer. This distinction explains many setup problems: a successful test from your laptop does not prove the cloud phone is using the same route.

PhoneFarm's setup flow asks you to bring a residential or ISP proxy with one dedicated IP per phone, in the country selected for that phone. It then binds the connection and verifies the exit from inside the phone environment.

What the proxy does

A proxy is an intermediary that carries network traffic. The host is the server you connect to; the exit IP is the address a destination sees when that traffic leaves the proxy. Those addresses do not have to be identical. A supplier may give you a hostname that routes to an exit in your chosen country.

“Residential” and “ISP” describe the type of network associated with the service. “Dedicated” describes how the endpoint or IP is assigned. “Rotating” describes whether exits can change. These terms answer different questions; a product being residential does not automatically make it dedicated or stable.

For a phone that keeps a particular account session, a clear phone-to-connection assignment is easier to operate and diagnose. If several phones lose access at once, knowing whether they share a supplier or endpoint helps identify the common failure. Read proxies and networking for the broader infrastructure explanation.

Collect the six pieces of information you need

The example hostname is a placeholder and will not connect. Copy real values from your supplier's connection instructions. Do not substitute the website address of the supplier for the proxy host; a website login and a proxy endpoint are different services.

Check that the purchased service uses credentials supported by the setup form. If the supplier requires a separate IP allowlist or a particular session configuration, understand that requirement before attempting to bind it. A proxy that only accepts requests from your laptop's IP may reject the cloud phone's connection.

Enter the connection in PhoneFarm

Open the setup runway for the intended phone. Confirm Phone and proxy country before entering credentials. This country comes from the phone purchase.

Under Paste proxy line, the interface supports these shapes:

host:port:user:pass
user:pass@host:port
http://user:pass@host:port
socks5://user:pass@host:port

Select Fill fields, then inspect the parsed values. A scheme-free line defaults to HTTP. If your supplier gave you SOCKS5, include socks5:// or choose the correct Type explicitly. The type selector also exposes HTTPS where supported by your endpoint.

You can instead enter Host, Port, Username and Password separately. This is often clearer when a credential contains punctuation that makes a pasted line difficult to interpret. Keep the hostname in Host and the port in Port; do not paste the entire connection string into both fields.

What “Verify and bind proxy” checks

Select Verify and bind proxy once the phone exists and the fields are complete. The action does more than save a label: it checks the supplied connection, binds it to the phone, and verifies the phone-side exit and expected country. The setup also rejects exits identified as likely datacenter or hosting networks for this flow.

While it runs, the interface shows Verifying proxy.... Wait for the result before changing fields or trying another endpoint. A successful result shows Proxy verified and enables the phone-ready step.

A proxy can be valid in the supplier's dashboard but fail here because credentials, access restrictions, protocol, country or actual phone routing differ from what was expected. “Valid account with the proxy supplier” and “working connection from this phone” are different checks.

Verify ordinary internet use inside the phone

Open live control and launch a browser on the phone. Load a normal HTTPS page and confirm it finishes. If you use an IP information page, open it inside the phone and compare the reported exit country with the configuration.

Do not use a new tab in your desktop browser for this check. That would show your computer's connection. Similarly, enabling a VPN on your computer does not demonstrate that the phone has inherited it.

An IP information service estimates location using its own database. Different databases may disagree, particularly about cities. A country mismatch deserves investigation; a city's name alone is not a precise measurement of a device's physical location. Keep the observed value and the time when reporting a mismatch.

A practical example

Suppose you created a United States phone and received a SOCKS5 endpoint from your supplier. You paste proxy.example.com:12345:your-username:your-password and choose Fill fields. PhoneFarm interprets the scheme-free line as HTTP, but your endpoint only accepts SOCKS5. Verification may fail even though the credentials are correct.

The useful correction is to select SOCKS5 or paste the explicitly prefixed line. Repeatedly buying a new proxy or changing the password would not address that protocol mismatch. After correcting it, run verification again and test from the phone.

Another common case is an endpoint configured for the wrong country in its username or supplier settings. The hostname may look generic while its routing options choose the country. Compare the complete supplier configuration, not just the visible host name.

What a successful connection does—and does not—tell you

A successful setup establishes a usable configured route at the time of verification. It is the foundation for app installation, login, browsing and publishing. It does not guarantee that a third-party app will always accept a login, that a social account has no restrictions, or that content will reach a particular audience.

When an app fails later, test the connection again before changing account settings. If multiple unrelated pages fail inside the phone, investigate networking. If pages load normally and only TikTok presents a verification prompt, follow account-login troubleshooting.

Keep proxy credentials out of shared spreadsheets and support screenshots. Your operating record needs the phone assignment, supplier reference, country and last successful check; it does not need a reusable password. For failed verification, missing internet or changed exits, continue with the network troubleshooting guide.