# Multilogin Proxy Setup for Custom Browser Profiles

[All guides](https://proxylane.dev/blog) 

INTEGRATION GUIDES · 5 MIN READ

Connect a third-party HTTP, HTTPS or SOCKS5 proxy in Multilogin, choose the right profile mode, and verify the live route.

**Founder, ProxyLane** Published September 22, 2026

On this page [Map provider fields before opening Multilogin](https://proxylane.dev/blog/multilogin-proxy#map-provider-fields-before-opening-multilogin)  [Configure a regular profile](https://proxylane.dev/blog/multilogin-proxy#configure-a-regular-profile)  [Configure Quick profiles and lists](https://proxylane.dev/blog/multilogin-proxy#configure-quick-profiles-and-lists)  [Verify the live browser route](https://proxylane.dev/blog/multilogin-proxy#verify-the-live-browser-route)  [Troubleshoot the first failed phase](https://proxylane.dev/blog/multilogin-proxy#troubleshoot-the-first-failed-phase)

**Residential proxies from $2/GB**

Non-expiring traffic, location targeting and rotating or sticky sessions for your existing tools.

 [Sign up](https://proxylane.dev/register?interest=proxies)

Multilogin attaches a proxy to a browser profile, so the route, cookies and local storage travel through the profile boundary you selected. The setup is complete only when the product accepts the endpoint and the running profile reaches the expected exit and target content. The profile check is evidence about connection at that moment, not a guarantee about the next page.

 

This guide is for a purchased third-party endpoint in Multilogin's browser profiles and Quick flow. The  [anti-detect browser proxy setup hub](https://proxylane.dev/blog/antidetect-browser-proxy-setup)  links to this guide and the other tool-specific procedures. If your workspace uses GoLogin, follow the  [GoLogin proxy guide](https://proxylane.dev/blog/gologin-proxy) .

 

## Map provider fields before opening Multilogin

 

Collect the endpoint details and decide how you will accept the test:

 

| Provider value | Multilogin field or check |
| --- | --- |
| HTTP, HTTPS or SOCKS5 | **Protocol** under **Custom** |
| IP address or hostname | **IP** or host value |
| Numeric port | **Port** |
| Username and password | Login fields when password-authenticated |
| Your current public IP | Allowlist it when the provider uses IP authentication |
| Expected exit and target marker | Compare them from the running profile |

 

Multilogin's custom proxy guide documents `IP:port:login:password` for password-authenticated endpoints and `IP:port` for endpoints that use IP authentication. Do not paste a username and password into an IP-authenticated record, and do not assume that a provider's URL format is accepted by the Custom form. A SOCKS5 endpoint remains SOCKS5 in the protocol selector.

 

Multilogin documents custom SOCKS5 support at the product level. Chromium's raw proxy layer supports SOCKSv5 transport but states that **SOCKSv5 authentication is not supported by Chrome**. An endpoint that requires SOCKS5 username/password therefore needs the Multilogin path or provider integration that explicitly supports that authentication. A generic Chrome proxy setting with embedded credentials is not a valid workaround. For an HTTP or HTTPS endpoint, test the host and port separately with the  [curl proxy guide](https://proxylane.dev/blog/curl-proxy)  before diagnosing the profile.

 

## Configure a regular profile

 

Use the current Multilogin path **Profiles → Browser → create or edit a profile → Proxy**. The Proxy section offers four modes:

 

| Mode | Use it when | What it proves |
| --- | --- | --- |
| **Multilogin** | You are selecting Multilogin's built-in proxy service | The selected built-in route is configured in the profile |
| **Custom** | You are connecting your purchased endpoint | The entered external endpoint is the intended route to test |
| **Template** | You want to reuse saved settings across profiles | The template contains saved settings; it still needs a live check |
| **None** | You intentionally want the device connection | The profile is using the device network, not the purchased endpoint |

 

For a third-party endpoint, select **Custom**, choose **HTTP**, **HTTPS** or **SOCKS5**, enter the IP or hostname and port, add credentials when required, and save the profile. Multilogin checks the proxy automatically. “Proxy check passed” means Multilogin connected and obtained the required IP-dependent data; “Proxy check failed” means the connection could not be completed. Start the profile and run the browser-level checks below even after a pass.

 

Templates help with repetition. The current profile settings page says a template can apply saved custom or Multilogin settings to multiple profiles and offers a one-click test. Treat that test as a configuration check for the template. Open one of the actual profiles and verify its live route before using it for a permitted workflow.

 

## Configure Quick profiles and lists

 

For a one-off profile, open **Quick** on the main dashboard, choose **Custom** in **Proxy**, choose **One proxy** under **Format**, select the protocol, and enter `IP:port` or `IP:port:login:password`.

 

For a list, choose **Proxy list** under **Format** and add at most **25 proxies** in those same formats. The documented selection modes are **Sequentially**, from top to bottom, and **Randomly**, in random order without repetition. The selected list and rotation behavior change the meaning of an exit check: record which entry was used, and do not compare a later request with the first entry unless the route is meant to be stable.

 

## Verify the live browser route

 

Run the test from the same profile or Quick browser that will perform the approved work:

 

1. Open an IP endpoint you operate or explicitly trust. Record the observed exit and compare it with the provider's expected value or session log.
 
1. Open the target HTTPS page and record the final URL, response status and a distinctive title, selector or record field.
 
1. If location matters, keep language, timezone, account state and parser fixed. An IP country is one signal; it does not guarantee a target's currency, locale or content variant.
 
1. Store `expected_country`, `observed_exit`, `target_final_url`, `content_check` and `timestamp`, then close the profile through Multilogin after the test.

 

The checker and the target answer different questions. A passed proxy check can coexist with a redirect, sign-in page, challenge, 403 or empty application shell. Diagnose the target response separately from the route.

 

## Troubleshoot the first failed phase

 

| Observation | Inspect first | Next action |
| --- | --- | --- |
| Format error | Protocol selector and whether the line is `IP:port` or `IP:port:login:password` | Match the authentication mode supplied by the provider |
| Proxy check failed | Host, port, expiry, credentials or IP allowlist | Test the endpoint separately and correct the first failing value |
| 407 or repeated auth prompt | Password pair versus IP authentication | Use the provider's required method; do not add credentials to an allowlisted record by guesswork |
| SOCKS5 transport works but auth fails | Chrome's documented SOCKSv5 authentication limitation | Use an explicit authenticated-SOCKS5 integration or a supported endpoint |
| Quick list uses the wrong route | List order, random mode and which entry was selected | Record the chosen entry and validate that entry in the same browser |
| Profile starts but target is wrong | Final URL, account state, locale and content validator | Classify target policy or content failure separately from proxy success |
| Related pages change exit | Provider rotation and profile/session policy | Use a documented sticky behavior for related pages, or split the pages into independent observations |

 

Use these tools for accounts and workflows you own or are authorized to operate. A proxy and a browser profile do not grant access to a target or permission to push through its rate limits. Keep retained evidence redacted to profile identifier, phase, target host, status, validator result and timestamp.

 

## Sources and further reading

- [https://multilogin.com/help/profile-settings-proxy-section](https://multilogin.com/help/profile-settings-proxy-section)

- [https://multilogin.com/help/http-and-socks-proxies](https://multilogin.com/help/http-and-socks-proxies)

- [https://chromium.googlesource.com/chromium/src/+/HEAD/net/docs/proxy.md](https://chromium.googlesource.com/chromium/src/+/HEAD/net/docs/proxy.md)

[Sign up](https://proxylane.dev/register?interest=proxies)

## Keep reading

[Use cases · 3 min read

### Amazon Scraper API vs Proxy: Choose a Product Data Source

Distinguish authorized Amazon APIs, licensed product data and proxy-based page checks by record quality and access rights.

 Read guide](https://proxylane.dev/blog/amazon-scraper-api-vs-proxy)   [Integrations · 5 min read

### Apify Custom Proxy Setup: Use Your Own Residential Route

Connect a buyer-owned proxy to an Apify Actor, keep the session boundary clear, and validate records instead of counting requests.

 Read guide](https://proxylane.dev/blog/apify-custom-proxy)   [Proxy fundamentals · 6 min read

### Australia Residential Proxies: Verify the AU Exit and State-Level Result

Separate Australian egress from en-AU content, AUD pricing, GST display, postcode validation and the state delivery context.

 Read guide](https://proxylane.dev/blog/australia-residential-proxies)

Canonical source: https://proxylane.dev/blog/multilogin-proxy

Documentation index: https://proxylane.dev/llms.txt