Guide
Proxies and Multilogin profiles
Most “the antidetect is broken” tickets are proxy stories: wrong country, rotating IP mid-session, or auth string pasta. Fix the lane before you blame WebGL.
Multilogin’s Postman collection has a Proxy folder for attaching and managing proxies on profiles. Paths move — use the official documenter. Below is the operator checklist we give media buyers and automation folks.
Before you scale ads
- One profile → one sticky residential/mobile exit when the platform is picky.
- Timezone + language inside the profile should not argue with that exit. Snap them with our TZ tool.
- Normalize host:port:user:pass with the formatter so Postman/UI paste errors drop.
- Start the profile once manually; open a geo-check page; only then wire Playwright.
When automation joins
Start via Launcher with your automation type, then attach CDP (Playwright). If connect works but every site smells datacenter, you don’t have a CDP bug — you have an IP reputation problem. See proxy troubleshooting.
Sticky vs rotating
Ads and social money lanes want sticky residential/mobile exit IPs that match profile TZ. Rotating proxies for sign-up spam are a different product — don’t mix them into the same Multilogin profile.
- Match country / city to the story the account already tells.
- One proxy credential tree per money lane; clone carefully.
- Test leak surfaces in-profile: DNS/WebRTC · proxy format.
When CDP works but every site says “datacenter”
That’s proxy quality, not Puppeteer. Fix credentials / provider first — proxy error desk.