GoLogin proxy setup: formats, bulk import, API and error fixes

What you need before you start

• A GoLogin plan with enough profiles. The Free plan has 3 profiles and no API access. GoLogin's pricing page lists the REST API from Professional 100 up (checked 1 October 2026).
• A TrueProxies Traffic pack, or the one-hour free trial. The trial supports country targeting and sticky sessions, without lifetime. City, region, ASN and session lifetimes need a Traffic pack.
• A current GoLogin app. The app and Orbita, GoLogin's Chromium-based browser, update in the background; click Restart app when prompted. The latest app on 1 October 2026 was v4.18.3. We tested GoLogin 4.18.3 on macOS with Orbita not recorded.
• Your connection details. Copy the host, username and password from your service page in the TrueProxies dashboard. Examples here write them as YOUR_HOST, YOUR_USERNAME and YOUR_PASSWORD. Targeting and session options are appended to the username with hyphens, and the password never changes (how to connect).

Which TrueProxies proxy to use in GoLogin

Residential IPv4 exits cannot reach IPv6-only destinations. Bigger packs go down to $0.60/GB at 5,000 GB; the full ladder is on the pricing page.

Proxy formats GoLogin accepts

GoLogin's docs list seven paste formats that work almost anywhere a proxy field appears, one at a time or in bulk. Without a prefix, GoLogin selects HTTP or SOCKS automatically, and you can change it later.

Wrong option values are refused, not ignored: country-usa is not a country code, so the gateway answers 407 with its targeting reason. Our parsing check of these formats: Import proxies accepted a credential list including host:port:user:pass and type://user:pass@host:port:name. An entry without a type selected HTTP. Other documented variants were not tested separately..

How to add a proxy to a GoLogin profile

From the All profiles page

1. Copy a string from the formats table. On All profiles, hover the profile's Proxy & Location column and click Paste proxies, or use your paste shortcut.
2. To type the details instead, click + in that column, choose the computer icon, enter host, port, username and password, and click Connect.
3. GoLogin checks the proxy right away. A green indicator means it works; a red one means it does not.
4. Click the arrows next to the proxy name to see its country and current outgoing IP.

From the profile settings

1. Click the 3 dots on the profile > Settings > Proxy > Your proxy. A new profile has the same Proxy tab under Add profile.
2. Paste the string or fill in the fields, then check the type: HTTP for 8080, SOCKS5 for 1080.
3. Save (Create Profile for a new one), click Run, and open the IP leak test in Orbita to confirm the IP and location.

To edit a proxy, click it, then the pencil icon, then Save.

Add proxies in bulk

Each paste route takes one proxy per line, in the formats above.

• Proxy & Location column: paste several lines at once on All profiles, then rearrange them between profiles if needed.
• Proxies page: click Proxies in the left menu > Import proxies, paste the list and click Import proxies to store them for later.
• Bulk actions: tick several profiles, click Proxy in the bulk actions row, paste the list and click Update proxy. GoLogin doesn't document how lines map to the selected profiles, and we haven't tested it.
• CSV: click the arrow next to Add profile > Import profiles, upload or paste CSV data and click Import. Proxy settings are included, but the column names aren't published, so export one profile first (Export profiles) and reuse its header. Existing profiles are updated, not duplicated.

http://YOUR_HOST:8080:YOUR_USERNAME-country-us-session-shopus01-lifetime-86400:YOUR_PASSWORD:shopus01
http://YOUR_HOST:8080:YOUR_USERNAME-country-us-region-NY-session-shopny01-lifetime-86400:YOUR_PASSWORD:shopny01
http://YOUR_HOST:8080:YOUR_USERNAME-country-us-asn-7922-session-shopus02-lifetime-86400:YOUR_PASSWORD:shopus02
http://YOUR_HOST:8080:YOUR_USERNAME-country-gb-city-london-session-shopuk01-lifetime-86400:YOUR_PASSWORD:shopuk01
socks5://YOUR_USERNAME-country-fr-city-paris-session-qafr01-lifetime-3600:YOUR_PASSWORD@YOUR_HOST:1080:qafr01

Give every line its own session ID, since two profiles with one ID request the same exit. Separate IDs do not guarantee distinct IPs. On the free trial, use country and session only, without lifetime.

Add proxies through the GoLogin API

GoLogin documents PATCH https://api.gologin.com/browser/proxy/many/v2 for setting the proxy on one or more profiles. Send the API token from Settings > API as a bearer token. For your own proxies, mode takes http, socks4 or socks5; there is no https value. Success returns 204.

export GL_API_TOKEN="your GoLogin API token"
export GL_PROFILE_ID="the profile ID"
export TP_PROXY_HOST="YOUR_HOST"
export TP_PROXY_USER="YOUR_USERNAME-country-us-session-shopus01-lifetime-86400"
export TP_PROXY_PASS="YOUR_PASSWORD"

curl -X PATCH "https://api.gologin.com/browser/proxy/many/v2" \
  -H "Authorization: Bearer $GL_API_TOKEN" \
  -H "Content-Type: application/json" \
  --data @- <<EOF
{"proxies": [{"profileId": "$GL_PROFILE_ID", "proxy": {
  "mode": "http", "host": "$TP_PROXY_HOST", "port": 8080,
  "username": "$TP_PROXY_USER", "password": "$TP_PROXY_PASS",
  "customName": "shopus01"}}]}
EOF

Add more objects to proxies to update several profiles in one call, each with its own session ID. For SOCKS5, use "mode": "socks5" and port 1080. POST /proxy/add_proxies stores proxies without attaching them. GoLogin warns that a 429 rate-limit response permanently invalidates your token, so pace bulk calls.

One sticky session per profile

Traffic packs rotate by default. Add a session ID to each profile's username to keep one exit IP: the same ID asks for the same IP, and a new ID asks for a new one.

• Name sessions after profiles: shopuk01, shopuk02, qafr01. Use 1 to 32 letters or digits, with no hyphens or underscores, because the hyphen is the separator.
• Pick a lifetime: lifetime-86400 (24 hours, the maximum) for profiles your team uses all day, and lifetime-3600 for short QA checks. Without lifetime, a session holds its IP only briefly. The range is 60 to 86400 seconds.
• Expect best effort: if the residential exit goes offline, the session gets a new IP. Relaunch the profile and rerun the IP leak test.
• Change the IP on purpose by bumping the ID, so shopuk01 becomes shopuk02.

Our test: HTTP and SOCKS5 checks returned the same IP for each of the three session IDs. A 24-hour hold was not verified..

A sticky session is not a static IP. We don't offer static ISP or mobile proxies, so a profile that needs one address for weeks needs GoLogin's Dedicated IP or another static proxy. See sticky vs rotating proxies and ISP vs residential proxies.

Match the profile to the proxy location

GoLogin can fill each location signal from the proxy IP, in the profile's Settings:

If a site shows the wrong place while the IP is right, it is reading the browser's Geolocation API: set Geolocation to Block or enter coordinates that match the proxy city.

Then verify each profile with the IP leak test, the WebRTC leak test and the DNS leak test, relaunching after any proxy change. Our recorded profile checks: Timezone: 3 of 3. Language: 2 of 3.

HTTP, HTTPS or SOCKS5 in GoLogin

For your own proxies, GoLogin supports HTTP, SOCKS4 and SOCKS5. Its docs group "HTTP/HTTPS" and describe HTTPS proxies as using SSL/TLS, but they document no separate type that opens TLS to the proxy itself. Protocol basics: HTTP vs SOCKS5.

IPv6: GoLogin's docs don't mention it, and its IPv6 proxy page lists providers without saying whether profiles accept IPv6 proxies. Traffic pack exits are IPv4-only. Datacenter IPv6 exits are IPv6-only, so sites without an IPv6 address return 502, possibly including the services GoLogin uses to check a proxy and look up its location. Our result: Not tested..

GoLogin proxy errors and fixes

Hover the red or yellow icon next to the proxy to read GoLogin's full message. Our wrong-password check showed "Proxy login or password error" and "The proxy server rejected your username or password." The other strings below come from GoLogin's help center.

Our SOCKS5 error check: Not isolated in this run: the recorded check used SOCKS5 on 8080 with a made-up password.

The yellow icon isn't explained in GoLogin's docs, and none of our test proxies showed it. On the Proxies page, the Errors tab lists proxies that failed a check, and Archive holds deleted or long-unused proxies you can restore.

GoLogin proxy not working? Read the gateway's reason

Anti-detect browsers show their own generic error and hide the gateway's reason. In GoLogin, a wrong password, a misspelled option and a used-up allowance can all look like the same 407. Paste the same proxy into the TrueProxies proxy checker, or run it with curl over HTTP on port 8080 and read the X-Proxy-Reason header. SOCKS5 carries no reason text, so diagnose over HTTP.

curl -v -x http://YOUR_HOST:8080 \
  -U "YOUR_USERNAME-country-us-session-shopus01-lifetime-86400:YOUR_PASSWORD" \
  https://example.com -o /dev/null

Reasons you are most likely to see:

• "Wrong proxy password. Check the credentials on your service page."
• "The targeting options in your username are not valid for this service. Check spelling, and do not repeat an option."
• "This service has used its traffic allowance. Add traffic to continue."
• A bare 407 with no reason: rate-limited after repeated failed attempts. Wait 60 seconds.

GoLogin notes that proxies which admit only listed IPs fail unless its checker's IP is listed too, so use username and password rather than a trusted IP list. More: error codes, gateway errors and anti-detect browser proxy errors.

TrueProxies in GoLogin: test results

We imported 3 Traffic pack sticky sessions (US, UK and Germany) over HTTP and SOCKS5, let GoLogin check all 6, then opened each HTTP session in its own profile with our IP, WebRTC and DNS leak tests. Tested on macOS during a GoLogin trial.

GoLogin built-in proxies vs your own

GoLogin sells its own proxies, called Gologin proxies, inside the app. Figures checked 1 October 2026; GoLogin says prices shown in the app are the most current.

Sources: gologin.com/gologin-proxies/ (updated 9 September 2026), gologin.com/pricing/ and GoLogin's proxy docs.

Built-in is the easier start. There is nothing to paste, and at small volumes $1 per GB is less than our 1 GB tier. GoLogin's Dedicated IP also covers profiles that need one address for weeks, which TrueProxies doesn't offer.

Your own proxy gives more control. You set each profile's session length, target by region, city or ASN, and pay less per GB as volume grows. Your own proxies don't use GoLogin's included traffic, and you can mix both kinds across profiles.

Choosing a proxy for GoLogin

• Session control: can each profile keep one IP for a working day, with a lifetime you set?
• Targeting depth: localized QA and regional clients often need region, city or ASN, not just country.
• Protocols: GoLogin takes HTTP and SOCKS5; Custom DNS needs SOCKS5.
• Pricing model: GoLogin estimates 0.3 to 0.5 GB per profile per day for light browsing and 0.5 to 1 GB for active work, so per-GB pricing fits. Size a pack with the calculator.
• IP type: residential for most profiles; static ISP or mobile only where a profile really needs it.

Where TrueProxies fits: teams that want residential IPv4 with one sticky session per profile, city and ASN targeting, and per-GB tiers across 150+ countries. It doesn't fit profiles that need a static IP for weeks or mobile carrier IPs, which we don't sell.

GoLogin proxy FAQ

Related guides

• Anti-detect browser proxy guides
• AdsPower proxy setup
• Dolphin Anty proxy setup
• Anti-detect browser proxy errors
• TrueProxies proxy checker