Proxy setup in PhantomBuster

Prokso proxies in PhantomBuster: Phantom Setup, Advanced settings, the Proxies tab, the HTTP option with Address, Username and Password, and proxy pools.

Updated · Prokso editorial team

Connection details
Host
gw.prokso.com
Port
823 HTTP · 824 SOCKS5 — new IP per request · 10000–20000 sticky session, HTTP(S) and SOCKS5
Username and password
in your dashboard, on the plan page

Your dashboard generates ready-made lines in the format you need: choose the country, IP type and protocol.

Key takeaways
  • Host gw.prokso.com, ports 823 (HTTP), 824 (SOCKS5), 10000–20000 (sticky sessions, HTTP or SOCKS5)
  • The username and password are in your dashboard on the plan page
  • After setup, check your IP on the My IP page

A step-by-step guide to connecting Prokso proxies in PhantomBuster. It takes a few minutes.

Step 1. Get the proxy details from your dashboard

Open your plan and copy the host gw.prokso.com, port, username and password. Port 823 is HTTP and 824 is SOCKS5 (both give a new IP for every request); ports 10000–20000 keep one IP (sticky session) for up to 120 minutes and work as both HTTP and SOCKS5 (each port is a separate address). Set the country in the username: username__cr.ua.

The “Access” block on the plan page: host, ports, username and password for the proxy line
The “Access” block on the plan page: host, ports, username and password for the proxy line

Step 2. Open the Phantom's setup

On the Phantom's card click the three-dot menu and choose Setup.

Step 3. Go to proxies

At the bottom left open Advanced settings and go to the Proxies tab.

Step 4. Enter the HTTP proxy

Choose the HTTP option and fill in the fields: Address — the proxy address with the port (gw.prokso.com and a sticky port from 10000–20000), Username and Password — your plan credentials. Save the settings.

Step 5. Save the proxy for several Phantoms

To avoid re-entering the details, create a proxy pool with your credentials in the workspace and assign it to Phantoms in the same Advanced settings.

Step 6. Check with a run

Launch the Phantom. If the run log shows an error about not being able to connect through the proxy, check the address, port, username and password. A successful run without that error means requests go through the proxy.

Phantoms run in the cloud

PhantomBuster runs Phantoms on its own servers. The IP whitelist (no password) will not work, so use a username and password. And the IP you see in your own browser says nothing about which address the Phantom works from.

The proxy country and your account

A Phantom logs in to your account on a third-party site. If you usually log in from one country and the Phantom from another, the site sees a login from a new place and may ask for confirmation. Take a proxy in the same country you work from yourself.

For the same reason you need a sticky port with the maximum session duration: the address must not change while the Phantom is doing its job.

If a Phantom ends with a proxy error

  • Special characters in the username or password. PhantomBuster does not accept them. Change the plan password to one made of letters and digits.
  • There is no port in the Address field. The address is entered together with the port.
  • The wrong type is selected. You need HTTP.
  • The plan has run out of traffic. The remaining traffic is shown in your dashboard.

FAQ

Which port should I use for Phantoms that work with accounts?

A sticky one from 10000–20000: the Phantom works from one address during the session. Port 823 changes the IP on every request and does not suit account work.

Which proxy country should I set?

The one you usually log in from: a sudden change of country looks suspicious to the service. The country is set in the dashboard generator.

How much traffic does a Phantom use?

It depends on the Phantom: some work through requests and use little, while others open pages in a browser. Run the Phantom once and look at the plan statistics.

Can I use one proxy for several accounts?

It is better not to: the accounts will end up on one IP. Take a separate sticky port for each account.