---
title: "Multilogin Proxy Setup: One Sticky IP per Profile | Proxonym"
description: "Connect proxies to Multilogin profiles: custom HTTP or SOCKS5 settings, a sticky IP per profile, proxy checks and fingerprints matched to the IP."
url: https://proxonym.com/integrations/multilogin
updated: 2026-10-01T21:01:06+00:00
---

# How to use proxies with Multilogin

Multilogin saves a proxy inside every browser profile. These steps add the Proxonym gateway as a custom proxy, keep a stable IP per profile with a session ID, and verify the connection before launch.

- 6 steps
- 12 min setup
- Copy-paste code

Before you start

- The Multilogin desktop app, signed in
- A Proxonym residential, mobile or ISP plan
- Your proxy username and password from the dashboard

Connection values

- **Host**: `gw.proxonym.com`
- **HTTP**: `8000`
- **SOCKS5**: `1080`
- **User**: `USERNAME-country-us`

1. **Prepare a username for each profile**: Give every profile its own session ID so it keeps one exit IP. Add the country you need and the longest residential lifetime, 120 minutes. Text `USERNAME-country-gb-session-mlx001-lifetime-120`
2. **Open the Proxy section**: Create a profile, or open the settings of an existing one, and go to its Proxy section. Choose the custom proxy option so the profile uses your own gateway rather than a built-in proxy.
3. **Choose the protocol and paste the details**: Select HTTP, or SOCKS5 with port 1080, and enter the proxy as one host:port:username:password string. Multilogin splits it into host, port and credentials for you. Text `Protocol: HTTP Proxy: gw.proxonym.com:8000:USERNAME-country-gb-session-mlx001-lifetime-120:PASSWORD Protocol: SOCKS5 Proxy: gw.proxonym.com:1080:USERNAME-country-gb-session-mlx001-lifetime-120:PASSWORD`
4. **Run the proxy check**: Multilogin checks a new proxy automatically, and you can run the check again from the Proxy section at any time. A passed check means the gateway accepted the login and returned an IP in the location you requested.
5. **Let IP-based settings follow the proxy**: Keep timezone, geolocation and language based on the proxy IP so they match the exit location, then save the profile and start it.
6. **Use static IPs for long-lived profiles**: Residential sessions hold an IP for up to 120 minutes. For profiles that must return from the same address for days or weeks, paste a static ISP proxy from your Proxonym list, which uses the same format. Text `Protocol: HTTP or SOCKS5 (both work on the port in your list) Proxy: IP:PORT:USERNAME:PASSWORD`

## Frequently asked questions

### Should I use HTTP or SOCKS5 in Multilogin?

Either works. HTTP on port 8000 is the standard choice and tunnels HTTPS sites through CONNECT. SOCKS5 on port 1080 suits workflows that need it and accepts the same username. Both protocols reach the same IP pool and support every targeting and session parameter, so pick one and keep it consistent across profiles.

### How long does a profile keep the same IP?

As long as its session lasts: up to 120 minutes on residential with -lifetime-120, and up to 3 minutes on mobile. Unlimited residential plans hold sticky sessions for up to 12 hours on their own gateway. ISP proxies are static, so the IP stays assigned to you for the whole plan term.

### What does a failed proxy check mean?

Multilogin could not get an IP through the gateway. Check the username and password for typos, make sure your plan is active and has balance, and confirm the protocol is HTTP or SOCKS5 rather than HTTPS. Testing the same credentials with cURL on your computer quickly shows whether the problem is the account or the profile.

### Can I use Proxonym ISP proxies in Multilogin?

Yes. Download your ISP list from the dashboard or the API and paste one ip:port:username:password line into each profile. HTTP and SOCKS5 both work on the port in the list, bandwidth is unlimited, and the IP stays the same for the whole term, which makes ISP proxies a good fit for account profiles.

Tips & gotchas

- Use a different session ID for every profile, because two profiles with the same ID share one exit IP.
- Pick HTTP rather than HTTPS for port 8000: the gateway accepts plain HTTP connections and tunnels HTTPS traffic inside them.
- Copy credentials straight from the Proxonym dashboard, since a stray space in the pasted string is a common cause of failed checks.
- Mobile IPs need -type-mobile and a supported country, the United States, the United Kingdom or Austria, and hold an IP for up to 3 minutes.

Go further

- [What Is an ISP Proxy? Static Residential Proxies Explained](https://proxonym.com/blog/what-is-an-isp-proxy)
- [Rotating vs Sticky Proxies: Choosing the Right Session Type](https://proxonym.com/blog/rotating-vs-sticky-sessions)

Stuck on a step?

Most failures come down to an error code. Check it first, then test the proxy on its own.

- [Help center](https://proxonym.com/help)
- [Gateway error codes](https://proxonym.com/docs#errors-and-troubleshooting)
- [Test your proxy](https://proxonym.com/proxy-checker)

## More integration guides

[All integrations](https://proxonym.com/integrations)

- [AdsPower (Anti-detect browser)](https://proxonym.com/integrations/adspower)
- [cURL (Command line)](https://proxonym.com/integrations/curl)
- [Go](https://proxonym.com/integrations/go)
