# GoLogin

GoLogin assigns a proxy per profile. Configuration is similar to AdsPower; the field labels differ.

## Per-profile setup

1. **Create profile** → **Proxy** tab.
2. Pick **Your proxy** (not "Free GoLogin proxy").
3. Fill in:

### Residential / Mobile (gateway)

| Field    | Value                                                            |
| -------- | ---------------------------------------------------------------- |
| Type     | HTTP or SOCKS5                                                   |
| Host     | `gate.helodata.io`                                               |
| Port     | `7777`                                                           |
| Username | `helo_s1a2b3c4d5e-type-res-region-us-session-prof01-sesstime-30` |
| Password | sub-user password                                                |

### ISP

| Field    | Value              |
| -------- | ------------------ |
| Type     | HTTP or SOCKS5     |
| Host     | `198.51.100.42`    |
| Port     | `8000`             |
| Username | `helo_s1a2b3c4d5e` |
| Password | sub-user password  |

4. Click **Check proxy** — confirms the exit IP.
5. **Create profile** → **Run**.

\[screenshot: GoLogin Proxy tab filled in]

## Bulk import

**Settings → Proxy management → Import** accepts `ip:port:user:pass` lines or a CSV file. Each row becomes a reusable proxy entry that you can assign to multiple profiles. For best practice, **one row → one profile** for ISP IPs.

## Verify

In the launched browser, hit `https://browserleaks.com/ip` and confirm the exit IP plus no WebRTC leak.

## Common pitfalls

* **GoLogin's "Auto-replace IP" feature** can override your settings — disable it for residential sticky sessions or ISP IPs.
* **Free proxy fallback** — if the proxy check fails GoLogin sometimes falls back to its own free proxies. Disable that toggle.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.helodata.com/integrations/antidetect-browsers/gologin.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.