Multilogin Proxy Setup: Databay HTTP and SOCKS5

Multilogin stores browser-profile settings; Databay supplies the external network route. In the setup below, Multilogin sends one profile's traffic to gw.databay.co:8888, and the Databay proxy username selects the purchased product, requested geography, and optional session behavior. Cookies, browser storage, operating-system settings, account history, language, time zone, and destination permissions remain separate inputs.

This is a nominative setup guide for interoperating two independent products. Databay is not affiliated with, sponsored by, or endorsed by Multilogin. Multilogin owns its interface and trademarks. The guide uses plain text and a generic router mark rather than Multilogin screenshots or brand assets. A working proxy changes the network exit; it does not guarantee how a destination classifies a browser, device, person, or account.

Choose from the network origin and location control the authorized job actually requires. Do not switch products simply because a destination refuses a request. Every Databay option below uses a shared pool; none is a permanently static or dedicated address.

Start with the least complex route that can answer the question. A rotating country route is easier to diagnose than a finely targeted sticky route. Add one selector at a time after the base credentials pass.

The current Multilogin custom proxy guide, updated June 17, 2026, asks for proxy type, host, port, and either password authentication or an allowlisted source IP. Use these values for a normal Databay password-authenticated profile:

Multilogin also documents an IP-authenticated host:port form. Use it only when the exact outbound IP of the machine or connected agent is already allowlisted in the Databay dashboard. A profile's requested exit country is unrelated to the source IP that must be allowlisted.

After selecting the protocol separately, Multilogin documents the password-authenticated value as IP:port:login:password; its prerequisite explicitly allows an IP address or hostname. The non-secret rotating example used by this guide's test is:

gw.databay.co:8888:DATABAY_USER-zone-residential-countryCode-us:DATABAY_PASSWORD

Replace DATABAY_USER and DATABAY_PASSWORD locally with the proxy credentials shown in the Databay dashboard. Do not add an http:// or socks5:// scheme to this particular paste field because the protocol is already chosen in the Multilogin control. For a 30-minute continuity request, a safe placeholder example is:

gw.databay.co:8888:DATABAY_USER-zone-residential-countryCode-us-sessionId-multilogin01-sessionLength-30:DATABAY_PASSWORD

Use a distinct alphanumeric session label for each continuity-sensitive authorized workspace. Omitting sessionId requests normal pool selection on new connections, but connection reuse can retain an exit and a different address is not promised. Including a session label requests continuity; upstream availability can still end it early. If a real credential contains a colon and the four-part parser does not accept it, do not guess at escaping or alter the secret in a shared document. Obtain a parser-compatible proxy credential through the approved Databay support path.

The steps below reproduce the current regular-profile workflow in Multilogin's June 17 custom-proxy guide and its Proxy section reference, updated July 20, 2026.

1. Create a browser profile or open the settings for the authorized profile you intend to change.
2. Find the Proxy section.
3. Select Custom as the proxy type.
4. Select HTTP or SOCKS5 according to the field map above.
5. Paste the single host:port:login:password line. For allowlist authentication, paste only gw.databay.co:8888 after confirming the machine's current outbound IP is allowlisted.
6. Wait for Multilogin's automatic proxy check and read the result before saving or starting the profile.
7. Save the profile, start it, and run the independent in-profile exit check described below.

Proxy check passed means Multilogin connected and obtained the IP-dependent data its check needs. Proxy check failed means the route did not pass that check. Neither result establishes permission at the destination, future availability, continued session identity, or a successful business outcome.

For a disposable, authorized check, Multilogin's current Quick flow is: choose Quick on the main dashboard, select Custom in Proxy, choose One proxy, select HTTP or SOCKS5, and paste the same four-part line. Its Proxy list option accepts up to 25 lines and can consume them sequentially or randomly without repetition. A list policy is not the same as Databay rotation: Multilogin chooses an entry from the list, while Databay decides the exit behind each authenticated route.

For maintained fleets, the official proxy-template guide, updated August 10, 2026, documents Proxy templates in the left menu, Create, a non-secret template name, Custom, One proxy, protocol, paste line, Check proxy, and Create. It then allows assignment through Manage assigned profiles or by selecting Template inside a profile's Proxy section. The cited page says template management is available on Pro 50 and higher as of its update date; verify the current plan screen before depending on it.

Do not put the password in a template name, profile name, screenshot, operations ledger, or chat. Record only a route label such as US QA / residential / 30m, the owner, expected country, and review date.

1. Connection layer: require Multilogin's automatic check to pass. This confirms a point-in-time connection from the current Multilogin environment.
2. Assignment layer: confirm the intended Custom value or named template is attached to the intended profile and that the profile change was saved.
3. Observed-exit layer: launch the profile, open the Databay IP checker, and compare the reported public IP and country with the written route plan. The reported address should be an exit, not gw.databay.co.

Record a redacted receipt containing profile label, expected product and country, selected protocol, check result, observed country, observed exit, UTC timestamp, and reviewer. Never record the complete proxy line or password. Recheck after changing a proxy template, product zone, country flag, session label, credential, device network, Multilogin version, or Databay configuration.

An observed country does not set the profile's language, time zone, geolocation permission, account country, payment details, cookies, or device attributes. Review those inputs independently for the authorized test rather than treating a proxy check as proof that the whole profile is coherent.

Multilogin's profile and proxy troubleshooting guide, updated August 3, 2026, starts with its status page and Check proxy. Use the evidence below to change one variable at a time.

If the proxy works in another approved client but not Multilogin, preserve the redacted check result and contact Multilogin through its current support channel. If it fails in both places, contact Databay with the timestamp, protocol, gateway, redacted username shape, and error class. Rotate the proxy credential if an unredacted line entered a screenshot, log archive, ticket, or shared message.

The setup fixture verifies the Databay gateway, port, zone names, selector order, sticky caps, and Multilogin's documented four-field shape without placing a real secret in the repository. Databay did not use a customer's credentials, launch a paid Multilogin workspace, or call an unapproved destination to publish this guide. Interface labels were reconciled with the official source dates shown above; when a later Multilogin release differs, treat the current Multilogin help center and visible application as the control and report the drift.

Use Multilogin and Databay only for systems, accounts, and data you own or are expressly authorized to operate. Browser-profile isolation and a routed exit do not permit impersonation, deceptive engagement, unauthorized account access, or bypassing a destination's controls. Apply named owners, multifactor authentication, least-privilege team access, source-level request budgets, stop conditions, and credential rotation. Review the Databay Acceptable Use Policy before expanding a workflow.

1. Write down the authorized purpose, profile owner, destination, expected network origin, country, and stop conditions.
2. Choose Premium Residential, Residential Flex, Datacenter, or Mobile from the required origin and controls.
3. Copy the proxy username and password from the Databay dashboard; do not use website sign-in credentials.
4. Select Custom and choose HTTP or SOCKS5. Use HTTP for HTTPS destinations through CONNECT.
5. Build exactly one host:port:login:password line locally.
6. Start with a base zone or one country flag; add a session request only when continuity is required.
7. Require Multilogin's automatic proxy check to pass.
8. Save and confirm the route is assigned to the intended profile.
9. Launch the profile and verify the observed exit and country independently.
10. Store only a redacted receipt; never capture the password or complete line.
11. Recheck after any route, credential, profile, client, or network change.
12. Stop on destination permission, account, consent, or rate controls.