How to add a proxy in GoLogin

A proxy in GoLogin goes on a profile rather than on the application, so profile one can exit in Lisbon while profile two exits in Toronto on the same laptop.

You attach it by pasting a single string. GoLogin accepts several shapes of that string, and the rest of this page is what they are, what the checker tells you afterwards, and how to do the same thing from the SDK.

What is GoLogin?

GoLogin is an anti-detect browser built on its own Chromium fork, Orbita. Each saved browser profile carries its own fingerprint, cookies, extensions, timezone and proxy, so several accounts can run from one machine without a site linking them to each other. GoLogin's own documentation describes a profile as "a generated set of browser parameters, that the browser uses to mimic a unique physical device and user".

The proxy is per profile rather than per application, so profile one exits in Lisbon and profile two exits in Toronto, at the same time, on the same laptop.

GoLogin proxy features

Seven accepted paste formats

Under the heading "We support the following proxy pasting formats:", GoLogin lists these verbatim:

192.168.0.1:8000:login:password
http://192.168.0.1:8000:login:password:name
socks5://login:password@192.168.0.1:8000:name
socks5://login:password@192.168.0.1:8000[https://change-my-ip.com]:name
http://192.168.0.1:8000:login
http://192.168.0.1:8000:myproxy:pass[https://change-my-ip.com]
http://192.168.0.1:8000:myproxy:pass[https://change-my-ip.com]:name4

Three rules are readable straight off that list. The scheme prefix is optional, because line one has none. A trailing :name segment sets the label the proxy gets in the Proxy Manager. And a URL in square brackets sets the rotation endpoint, which the REST API calls changeIpUrl and describes as: "This allows you to change IP address of the proxy if your proxy provider supports it".

Automatic protocol selection

You are not asked to pick one. Per the docs, "the HTTP or SOCKS protocol will get selected automatically based on availability, you can change it later."

The user-facing protocol page names four: HTTP, HTTPS, SOCKS4 and SOCKS5. The REST API's mode enum is wider than that and lists http, socks4, socks5, possh, geolocation, none, gologin and tor. SSH and Tor are backend modes with no matching user-facing documentation.

A checker that runs on its own

After you click Connect, "Gologin will check your proxy right away. You will see the green indicator if the proxy works properly, or the red one if it is not." You can re-run it later from the profile list, and it reports back more than a colour: "It will show the proxy country and the current outgoing IP."

Bulk paste in the same syntax

The same formats work many at a time, one per line. "You can paste proxies one by one or in bulk at the same page. Copy a few proxies and paste them all at once into the Location column."

Adding a proxy

1. Open the profile list. "At the All profiles page, find the Location column and click the + button at the profile, which you want to add a proxy to."
2. Choose the third-party option and paste. "In the opened window, hit the computer icon and input your IP, port, username and password." Pasting one of the seven strings above fills all four boxes at once.
3. Leave the protocol alone unless your provider tells you otherwise. It is selected for you from availability.
4. Commit it. "Click Connect, the proxy is now added to your profile!"
5. Read the indicator. Green means the check passed. Red is the subject of the next section.

To change it later: "click on the proxy > click the pencil icon > click Save after making changes." To detach one without deleting it, "click on the proxy, then click the X to unlink it."

Why the check goes red

The credential order is the first thing to suspect, because it is the failure the format list invites. These two are both documented and both accepted:

192.168.0.1:8000:login:password          host first, credentials after
socks5://login:password@192.168.0.1:8000 credentials first, host after

A string in one shape pasted where you meant the other still parses. It just parses into the wrong fields, which is the same trap Dolphin Anty surfaces as a port length error, and the endpoint answers 407 with nothing naming the cause. GoLogin's own support escalation instructions use the plain colon form, ip:port:login:password, which is the safer one to standardise on.

The second suspect is IP allowlisting, and this one is not your mistake. GoLogin lists it under "Possible root causes of the issue": "Access to proxies allowed only from whitelisted IPs. If the IP of our checker is not set up there, the proxy won't work in Gologin."

Read that carefully, because it has a consequence the docs do not draw out. The check runs from GoLogin's infrastructure, not from your machine. A proxy scoped to your home address will show red in GoLogin and work perfectly from a terminal on the same desk. GoLogin does not publish an IP range for its checker, so there is no address you can add to a provider allowlist to fix it. If your provider offers both authentication modes, credentials are the one that works here. Multilogin is the one tool of this group that documents allowlisting as a supported path rather than a failure.

The GoLogin FAQ lists "incorrect IP, port, username, or password" first among the reasons a proxy fails, which covers the first case and not the second.

Automating it

GoLogin drives Orbita locally through its SDK, and the debugger port is returned to you at launch rather than fixed. Attach the proxy to the profile first, then start it and connect to whatever endpoint comes back.

import { GologinApi } from "gologin";

const GL = GologinApi({ token: process.env.GOLOGIN_API_TOKEN });

// The proxy fields the REST API names: host, port, username, password.
await GL.updateProfileProxy(profileId, {
  mode: "http",
  host: "gate.example.com",
  port: 7000,
  username: "user-session-abc123",
  password: "secret",
  changeIpUrl: "",
});

const { status, wsUrl } = await GL.start();
// Connect Puppeteer or Playwright using wsUrl
const browser = await puppeteer.connect({ browserWSEndpoint: wsUrl });
const page = await browser.newPage();
await page.goto("https://example.com");
await GL.stop();

Python drives Selenium off the same handle, and the address is again whatever the launch hands back:

from gologin import GoLogin
from selenium import webdriver
from selenium.webdriver.chrome.options import Options

gl = GoLogin({"token": TOKEN, "profile_id": PROFILE_ID})
debugger_address = gl.start()

chrome_options = Options()
chrome_options.add_experimental_option("debuggerAddress", debugger_address)
driver = webdriver.Chrome(options=chrome_options)
driver.get("https://example.com")

driver.quit()
gl.stop()

Do not hardcode 44777 or 44778. Both appear in GoLogin's documentation and neither is Orbita's debugger. They are the CLI daemon ports: the local agent takes GOLOGIN_DAEMON_PORT, "Daemon port (default: 44778)", and the cloud agent binds "Localhost HTTP on 127.0.0.1:${GOLOGIN_DAEMON_PORT:-44777}".

Cloud profiles are reached differently again:

const browser = await puppeteer.connect({
  browserWSEndpoint:
    `https://cloudbrowser.gologin.com/connect?token=${TOKEN}&profile=${PROFILE_ID}`,
});

with the vendor's warning attached: "Only the /connect endpoint works for Puppeteer/Playwright."

These follow GoLogin's documented endpoints and field names rather than a run of ours, because the API is excluded from the free tier and we did not buy a plan to check. Every name above appears in the source list at the foot of this page.

Whichever tool you settle on, the proxy behind it is the recurring cost, and per-gigabyte prices vary far more between providers than these applications vary between each other. What each charges, with the date it was read, is on the provider table.

Limitations

The free tier cannot automate. Three profiles are free with no time limit, which is genuinely useful for testing a proxy by hand. But the "Free Plan Limitations" list puts "API access" among the things it excludes, along with bulk profile creation and cloud profiles. Every programmatic path in the section above needs a paid plan, which starts at nine dollars a month.

The field names are inconsistent in GoLogin's own documentation. The same four inputs are "IP, port, username and password" in the walkthrough, "Host, port, login and password" on the Proxies page, and host, port, username, password in the API. If you are searching their help centre for a label you saw on screen, that is why you cannot find it.

Custom DNS is protocol-gated to SOCKS4 and SOCKS5, and team members are a Business-tier feature.

What the documentation does not say

We looked for these and could not establish them from GoLogin's own pages, so we are printing them as gaps rather than filling them in:

• The literal field labels of the Add Proxy dialog, in order. GoLogin documents it in prose and screenshots, never as a rendered form, and the two label sets above disagree.
• A published IP range for the proxy checker. Without one, the allowlist problem above has no fix inside GoLogin.
• Whether SSH and Tor modes reach the desktop dialog at all. They are in the API enum and absent from every user-facing protocol page.
• Whether the "Add Proxy" button opens the same form as the "+" in the Location column. Both are documented as existing; neither is described field by field.

One thing no paste format settles: the session token sits in the username at some providers and the password at others, and the wrong one gives you the same 407 as a mis-ordered string. What each provider states is on its provider page, with the date we read it.

Conclusion

GoLogin's proxy handling is more permissive than most, and that is the thing to be careful about rather than the thing to enjoy. Standardise on host:port:login:password, expect the checker to disagree with your terminal whenever allowlisting is involved, and read the port out of the launch response instead of the docs.