Multilogin proxy setup: a static IP for every browser profile

Multilogin sells its own proxies, but it takes anyone’s, and a static IP of your own is often the better fit for a profile you plan to keep. This Multilogin proxy setup guide adds a custom HTTP or SOCKS5 proxy with a username and password to a browser profile in Multilogin X, saves it as a reusable proxy template, checks it, and fixes the one default most people miss: the profile’s language.

Checked against Multilogin docs in September 2026, for Multilogin X, the current app. Multilogin’s custom proxy help article has the latest screens.

Before you start

Multilogin’s own checklist: the proxy type, the IP or hostname, the port, and whether the proxy wants a username and password or an allowlisted IP. Your dashboard lists all of it for each order. Most people use the username and password; an IP allowlist works too, but only while your own IP stays the same.

Give each profile its own static IP and leave it there. The antidetect browser proxy guide explains why, and why rotating residential is the wrong choice here.

How to add a custom proxy in Multilogin

Create or edit a profile, open its Proxy section, choose Custom, pick HTTP, HTTPS or SOCKS5, and enter the proxy as IP:PORT:USER:PASS. Multilogin checks it on the spot.

1. Go to Profiles → Browser → Create. For an existing profile, open its settings instead.
2. Name the profile in the General section, ideally after the client or project it is for.
3. In the Proxy section, choose Custom. The other options are Multilogin (their own proxies), Template (a saved proxy) and None (your own connection, shared by every profile without a proxy).
4. Choose the protocol. HTTP is the plain choice for browsing; SOCKS5 also works with a login here, which is not true of Chrome.
5. Enter the proxy in one line:

   IP:PORT:USER:PASS

6. Wait for the automatic check. Proxy check passed means Multilogin reached the proxy and got the IP details it needs. Proxy check failed means it could not; see the fixes below.
7. Click Create, go back to Profiles, and click Start.

Quick profiles and proxy lists

Multilogin also has quick profiles, started from the Quick button in the main dashboard. Under Custom it has a Format choice: One proxy, or Proxy list, which takes up to 25 proxies used Sequentially or Randomly. That suits a one-off look at a page from several places. For a profile you will open again, use a regular profile with one proxy, so it keeps its address.

Save the proxy as a Multilogin proxy template

Templates are Multilogin’s reusable proxy list. You set a proxy up once, test it, and apply it to profiles. Not every plan includes them; Multilogin’s docs list which do.

1. Click Proxy templates in the left menu, then Create in the top menu.
2. Name the template. Naming it after the IP’s country and client helps: uk-client-a.
3. Choose Custom, then One proxy, pick the protocol, and enter IP:PORT:USER:PASS.
4. Click Check proxy, wait for Proxy check passed, then click Create.

In a profile’s Proxy section, choose Template and pick it. To retest later, open Proxy templates and click Check beside the template. One template per profile keeps the one-IP-per-profile rule easy to see at a glance.

Timezone, language and WebRTC in Multilogin

These are in the profile’s Fingerprint section. Multilogin’s defaults are mostly right, with one exception.

• Timezone: Masked by default, which matches the timezone to the proxy’s location. Keep it.
• Geolocation access: Prompt by default, so the browser asks when a site wants your location. Geolocation data is Masked: coordinates near the proxy’s location, with a small offset.
• WebRTC: Masked by default, which keeps the WebRTC address in line with the proxy. Keep it.
• Browser languages: Masked by default, and here that means English, whatever country the proxy is in. Multilogin’s docs point out that languages are a preference and do not have to match the proxy. But if you are testing how a German site looks to a German visitor, switch this to Custom and put German first.

Timezone and geolocation follow the IP, so the IP has to be in the right country. Our static ISP proxies come in the country you choose at checkout; residential ones cannot be pinned to a country at all.

How to check your IP in a Multilogin profile

1. Select the profile in the list and click Check proxy in the top menu, or use the right-click menu.
2. Start the profile and open https://httpbin.org/ip. The origin should be your dashboard IP.
3. Open BrowserLeaks, one of the checkers Multilogin’s docs name, and confirm the IP, timezone and WebRTC address agree.

Multilogin proxy not working? Fixes

“Proxy check failed”

Multilogin could not connect. Check the IP, port, username and password against your dashboard, and that the order is active. Then rule Multilogin out with a test outside it:

curl -x http://USER:PASS@IP:PORT https://httpbin.org/ip

A rejected login there shows up as 407, covered in the 407 guide. No answer at all is a timeout; see connection timeouts.

“Wrong proxy data”

Multilogin’s fix list for this error includes the format. It expects IP:PORT:USER:PASS in that order. A line copied as USER:PASS@IP:PORT from somewhere else needs rearranging.

ERR_SOCKS_CONNECTION_FAILED

The profile is set to SOCKS5 and the proxy did not accept it. Check the details, and if they are right, switch the profile to HTTP with the host and port your dashboard lists.

Proxy check passes, but the profile will not start

Multilogin’s advice is to restart the desktop app, then look at antivirus software, firewalls and VPNs on your computer, which can get in the way. Its docs also say your computer’s own clock should be set to update the time and timezone automatically; a system timezone that is out of sync is one of the rare causes of IP leaks they list.

Your real IP shows up anyway

The other known cause in Multilogin’s docs is NordVPN’s Threat Protection, which pushes every browser through NordVPN even when the VPN is off. Turn it off and restart the profile.

What these profiles are for

One profile per client or market is how agencies, ad verification teams and testers work. We do not support fake-account farms or getting round a platform’s ban, and platforms’ own terms still apply. The antidetect browser guide and the acceptable use policy have the detail. Setting up Dolphin Anty as well? The Dolphin Anty proxy guide covers it.