Programa de referidos
Navegador antidetección

Configuración de proxy en Multilogin

Aísla cada perfil de Multilogin con su propia IP de SotaProxy.

Multilogin crea perfiles de navegador aislados con huellas digitales únicas. Empareja cada perfil con un endpoint de SotaProxy dedicado para garantizar una separación de IP completa entre cuentas.

Guía de configuración

1

Crea o edita un perfil

En Multilogin, crea un perfil nuevo o edita uno existente. Ve a la sección Proxy.

2

Configura los ajustes de proxy

Establece el tipo en HTTP. Introduce proxy.sotaproxy.com como host y 10000 como puerto. Introduce tu nombre de usuario y contraseña de SotaProxy.

3

Asigna una sesión única por perfil

text
# Profile 1
Username: YOUR_USERNAME_s_1001_ttl_1h

# Profile 2
Username: YOUR_USERNAME_s_1002_ttl_1h

Usa IDs de sesión únicos por perfil. Esto garantiza IPs distintas incluso cuando varios perfiles se ejecutan simultáneamente.

Automatízalo con la API de SotaProxy

Todo lo anterior funciona sin abrir el panel. Con una clave API, Multilogin puede obtener credenciales de proxy actualizadas, comprar nuevos proxies y renovar los que caducan - directamente desde el código.

bash
# Every active proxy on your account (ip, ports, login, password as JSON)
curl -H "Authorization: Bearer $KEY" https://api.sotaproxy.com/api/v1/proxies

# Buy more when you scale (price-check first with POST /quote)
curl -X POST https://api.sotaproxy.com/api/v1/orders \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  -H "Idempotency-Key: my-unique-order-id" \
  -d '{"product":"ipv4","countryId":565,"periodId":"1m","quantity":5}'
Leer la documentación de la API

What goes into the profile proxy form

Multilogin asks for five fields and nothing else. Residential targeting rides inside the login, so you never need a separate endpoint per country:

Type
HTTP, or SOCKS5 on the same port
Host
proxy.sotaproxy.com
Port
10000
Login
login_c_US_s_17_ttl_1h
Password
your package password

Multilogin lets you save the proxy at the profile level or reuse a saved entry across profiles. Save it per profile: shared entries are how two accounts end up on one address by accident.

One session id per profile, forever

The number after _s_ is what ties a profile to an address. Give every profile its own and never reuse one, because two profiles on the same id share an address and that link is the cheapest signal a platform can compute:

Login strings for a fleet

profile_01  ->  login_c_US_s_1_ttl_1h
profile_02  ->  login_c_US_s_2_ttl_1h
profile_03  ->  login_c_GB_s_3_ttl_1h
profile_04  ->  login_c_DE_s_4_ttl_1h

# static address instead of residential:
# host = the IP from your dashboard, port 50100, no suffixes
  • One hour is the longest sticky lifetime we offer, and a residential device can drop earlier. For accounts that must never see an address change, buy an ISP address instead and put it in the same form.
  • Match the profile timezone, locale and language to the proxy country. An account on a German address reporting a Warsaw timezone contradicts itself.
  • Check the address inside the profile before the first login, not from your own browser. What matters is what the profile sees.
  • Keep a note of which session id belongs to which profile. Rebuilding that mapping after a crash is painful and mistakes cost accounts.

What gets accounts linked

Two profiles on one address

Whether through a shared session id or a shared static address, this is the fastest way to lose a cluster: one flagged account takes the rest with it.

Changing country under a live account

An account that always logged in from Poland suddenly appearing on a German address reads as a takeover, and the platform asks for a phone number you may not have.

Rotation under a logged-in session

When a sticky hour expires mid-session the platform sees the session teleport. Long-lived accounts belong on ISP addresses.

Shared proxy entries

The convenience of picking a saved proxy from a list is exactly what puts two profiles on one address. Create a separate entry per profile even though it takes longer.

Notas y consejos

  • Multilogin admite la importación de proxy mediante API - automatiza la asignación de proxy al crear perfiles programáticamente.
  • Verifica el proxy de cada perfil con el comprobador de proxy integrado antes de lanzarlo.

FAQ

¿Funciona Multilogin con proxies rotativos?

Sí. Usa sesiones persistentes para mantener la misma IP durante la sesión de un perfil. Rota a una IP nueva cambiando el ID de sesión o dejando que expire la ventana de persistencia.

Obtén tus credenciales de proxy

Regístrate, recarga tu saldo y copia tu endpoint en Multilogin. Tarda menos de 5 minutos.

Empezar