Proxy setup in Multilogin

A step-by-step guide to connecting Prokso proxies in Multilogin. 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.

Step 2. Prepare a line for the profile

In the dashboard generator choose a country, HTTP or SOCKS5, and “Sticky session” mode to get a line with a sticky-session port (10000–20000). Choose the host:port:username:password format — that's what Multilogin accepts in the proxy field. Use a separate line, with its own port and IP, for each profile.

Step 3. Open the Proxy section of the profile

In Multilogin X create a new profile or open an existing one's settings and find the Proxy section. Multilogin's own built-in proxy may be selected there — switch the type to Custom to connect yours.

Step 4. Paste the proxy details

Choose the protocol — HTTP(S) or SOCKS5 — matching the one in the generator. Paste the line in gw.prokso.com:port:username:password format. Copy the username and password without spaces at the start or end, or the check will fail.

Step 5. Wait for the check

Multilogin checks the proxy on its own. Proxy check passed means the connection works and the app received the IP data. If you see Proxy check failed, match the protocol to the port: 823 is HTTP only, 824 is SOCKS5 only, and a sticky port accepts both types.

Step 6. Several profiles at once

The Quick button on the main dashboard creates a quick profile. In the Proxy section choose Custom and set Format to Proxy list: you can paste up to 25 lines, and Multilogin uses them sequentially or randomly. For accounts it's safer to tie one port to one profile.

Step 7. Check the IP inside the profile

Start the profile and, in its window, open the My IP page. It should show the proxy's IP and country, and the WebRTC block shouldn't reveal your real address. Your regular browser will show your own IP — that's expected, as it doesn't use the proxy.

Your own proxy or the built-in one

Multilogin has built-in proxies provided by the service itself, and one of those may be selected by default. For traffic to go through your plan, the type must be "Custom". It is easy to check: in a running profile, open My IP and compare the address and country with what the generator in your dashboard shows.

If you see "Proxy check failed"

• The protocol and port do not go together. 823 is HTTP, 824 is SOCKS5, and sticky ports 10000-20000 take either of the two.
• The string is in a different format. Multilogin expects host:port:username:password. Convert a string of the form username:password@host:port to the required format in the proxy format converter.
• A space in the username or password. Most often it slips in when copying from a spreadsheet.
• No traffic left on the plan. The remaining traffic is shown in your dashboard.

If the check in Multilogin fails while the proxy checker on the site shows that the string works, the cause is in the profile settings or in your network.

The proxy list in quick profiles

The "Proxy list" mode hands out strings in order or at random. That is convenient for one-off tasks but not for accounts: on the next launch the profile may get a different string and a different IP. An account needs a permanent profile with one string assigned to it.