To add a proxy in GoLogin, open the profile's settings, go to Proxy and choose Your proxy. Set the type that matches the port, enter host, port, login and password, click Check Proxy and save. Give every profile its own sticky session. Below: each step, the formats GoLogin accepts, Residential Premium, ISP and mobile proxies, bulk import and a fix for each error.
GoLogin keeps every browser profile apart: its own cookies, its own fingerprint and, once you add one, its own proxy. The proxy decides which IP address and which country the sites see. Getting it right takes four values, and a type that matches the port; getting them wrong is the reason behind most "proxy not working" searches. The field names below are the ones in GoLogin's own documentation, and the values come from the QuanticData endpoint generator.
What you need before you start
- GoLogin installed, with an account. Its Forever Free plan keeps up to 3 profiles at a time and up to 25 new profiles a month; the paid plans lift those limits.
- A proxy plan. Residential Premium, ISP or mobile: each works in GoLogin, and the sections further down say which one fits which profile.
- The four values: host, port, username and password. In the QuanticData dashboard they are under My proxies, on the plan's page, in the Endpoint generator.
The proxy formats GoLogin accepts
Wherever GoLogin takes a whole line, in the Paste proxies button, in Import Proxies or in the bulk Proxy action, it reads these layouts:
- host:port:login:password: what the generator gives with the output format host:port:user:pass.
- login:password@host:port: the same proxy, written the other way round.
- host:port: only with IP whitelist authentication, where no login is sent.
- A type prefix,
http://orsocks5://, at the start. A line without a prefix is read as HTTP, so a SOCKS5 line needssocks5://. - A name after a last colon, for example
:de-profile-01, which becomes the proxy's name in the list.
The same QuanticData proxy in each layout:
# host:port:login:password, read as HTTP
residentialpremium.quantumproxies.io:8080:USER-country-de-sid-p01-ttl-60m:PASS
# login:password@host:port with a name at the end
USER-country-de-sid-p01-ttl-60m:PASS@residentialpremium.quantumproxies.io:8080:de-profile-01
# SOCKS5 on its own port: the prefix is required
socks5://USER-country-de-sid-p01-ttl-60m:PASS@residentialpremium.quantumproxies.io:1080The login is the whole username string, with everything after the first dash: -country-de picks the exit country, -sid-p01 names the session and -ttl-60m keeps it for 60 minutes. Copy it whole. A login cut at the first dash still authenticates, but the profile then leaves from a random country on a new IP at every request. GoLogin also takes a change-IP link in square brackets at the end of a line; with QuanticData leave it out.
Step by step: add a proxy to a GoLogin profile
- Generate the line. In the QuanticData dashboard open My proxies, then your plan. In the Endpoint generator choose the Country (and a Region or City if the profile needs one), set Session to Sticky, set Session TTL (minutes) to at least the time the profile stays open, choose the Protocol and keep the Output format on host:port:user:pass. Connection details shows the same four values one by one, which is what the profile form asks for.
- Open the profile's settings in GoLogin. For a new profile click Add profile; for an existing one click the three dots on the profile, then Settings.
- Go to the Proxy tab and choose Your proxy. Choose saved proxy lists the proxies you stored before; below it, Add or edit proxy holds the fields.
- Set Proxy Type, Host and Port. The type that matches the port: HTTP for 8080, SOCKS5 for 1080. Auto lets GoLogin detect it; choosing it yourself rules out a wrong guess. Host is
residentialpremium.quantumproxies.io. - Enter Login and Password. Login is the whole username from the generator,
USER-country-de-sid-p01-ttl-60min this example. - Leave Change IP URL empty. With QuanticData a new IP comes from a new session ID in the login, not from a URL.
- Click Check Proxy. The country has to match the
-country-in the login. - Click Create Profile, or Save for an existing one. The profile's time zone, which GoLogin takes from the IP by default, then follows the proxy.
The quick way: the Proxy & Location column
GoLogin's documentation calls this the simplest way. On the All profiles page, hover the Proxy & Location cell of a profile and click +, then the computer icon for your own proxy. The form asks for Type, Name, Host with the port, Login, Password and Change IP; fill them as above and click Connect. GoLogin checks the proxy straight away: a green indicator if it works, a red one if it does not. The clipboard icon next to + is Paste proxies: copy one or more lines and paste them into the column.
To check a proxy later, click the arrows next to its name on the All profiles page. GoLogin shows the proxy's location and its current outgoing IP. On 23 October 2026 a QuanticData Residential Premium line with -country-de, checked this way, left from Mannheim, Germany; the same request through ipinfo.io gave the region Baden-Württemberg and the time zone Europe/Berlin.
To change a proxy, click it in the list, then the pencil, and Save; the X next to it unlinks the proxy from the profile without deleting it.
One sticky session per profile
An antidetect profile is meant to look like one person on one connection. A rotating proxy changes IP on every request, which suits scraping and breaks a profile that logs in. A sticky session keeps one IP for as long as the session lives, and the session lives in the username, so the line never has to change once it is saved in the profile.
# profile 1: Germany, one session for a working day
residentialpremium.quantumproxies.io:8080:USER-country-de-sid-p01-ttl-480m:PASS
# profile 2: same plan, its own session (never reuse p01)
residentialpremium.quantumproxies.io:8080:USER-country-de-sid-p02-ttl-480m:PASS
# profile 3: Germany, open all day
residentialpremium.quantumproxies.io:8080:USER-country-de-sid-p03-ttl-1440m:PASS- A different session ID in every profile. GoLogin's own documentation advises against one proxy for several profiles: two profiles on the same line share one IP.
- A lifetime longer than the work. The generator accepts up to 1440 minutes, a full day. When the session ends, the next request gets a new IP, and a site can see that as a new login location.
- The country in the login. Without
-country-the exit can be anywhere, and the profile's time zone will not match. - A new IP is a new session ID. Edit the login, for example from
-sid-p01to-sid-p01b, and save.
With Session set to Sticky, the generator makes as many lines as the Quantity field says, ten by default, each with its own session ID; Copy all or Download takes them out in the same format.
Residential Premium, ISP and mobile proxies in GoLogin
Residential Premium
The setup above. One sticky line per profile, with the country, and a region, city or ISP if the profile needs one, in the login. Authentication is username and password; HTTP on 8080, SOCKS5 on 1080. It is the right choice for most profiles: home IPs in the country you pick. More on why each profile needs its own address in residential proxies for antidetect browsers.
ISP
ISP plans list fixed IPs under Assigned IPs, in the format IP:Port:Username:Password, which is exactly GoLogin's host:port:login:password layout: paste the line, or put each value in its field. Give each profile one IP and keep it: the address does not change, which is what long-lived accounts need. There is nothing to rotate, so Change IP URL stays empty. The plans are on the page for ISP proxies.
Mobile
Mobile lines go in the same way: one line per profile, a gateway (Global, USA, EU or Asia), HTTP on 8080 or SOCKS5 on 1080, a sticky session in the login. GoLogin's form labels Change IP URL "for mobile proxy"; with QuanticData leave it empty too, because a new session ID gives a new IP. Mobile plans also offer IP whitelist authentication: add your IP in the dashboard, then use the host:port lines, which GoLogin accepts with no login. More in mobile proxies for GoLogin.
| Proxy type | In GoLogin | Good for |
|---|---|---|
| Residential Premium | One sticky line per profile; country, region, city or ISP in the login; HTTP 8080 or SOCKS5 1080; username and password | Most profiles: home IPs in the country you choose |
| ISP | Fixed IPs under Assigned IPs as IP:Port:Username:Password; one IP per profile | Long-lived accounts that should keep the same address for months |
| Mobile | One line per profile; Global, USA, EU or Asia gateway; HTTP 8080 or SOCKS5 1080; IP whitelist available | Phone-first platforms and accounts tied to mobile networks |
| Datacenter | The same one-line format | Testing and low-risk profiles where speed matters more than the type of IP |
Adding proxies to many profiles at once
- Make the lines. In the generator, set Session to Sticky and the quantity you need, generate, then Copy all or Download.
- Import them. Click Proxies in the left menu, then Import Proxies, paste the list, one proxy per line, and click Import proxies. Add a name after a last colon to find each one later; start a line with
socks5://for port 1080. - Assign them. On All profiles, tick the profiles, click Proxy in the bulk actions, paste one line per profile and click Update Proxy. The window shows which line goes to which profile before you confirm.
residentialpremium.quantumproxies.io:8080:USER-country-de-sid-p01-ttl-1440m:PASS:de-profile-01
residentialpremium.quantumproxies.io:8080:USER-country-de-sid-p02-ttl-1440m:PASS:de-profile-02
socks5://USER-country-de-sid-p03-ttl-1440m:PASS@residentialpremium.quantumproxies.io:1080:de-profile-03
The Proxies page keeps three tabs: All proxies, Errors for those that failed a check, and Archive. A proxy no profile has used for 30 days moves to Archive and is deleted after another 180 days there; Restore brings it back.
GoLogin proxy not working: errors and fixes
When a check fails, GoLogin shows a red indicator next to the proxy, and the Proxies page lists it under Errors. Its documentation says to hover the red or yellow icon first: the expanded message usually names the reason. These are the cases behind it, in the order to check.
| What you see | Usual cause | Fix |
|---|---|---|
| Red indicator after Connect or Check Proxy, proxy under Errors | The type does not match the port: HTTP on 1080 or SOCKS5 on 8080, often a pasted SOCKS5 line without a prefix | HTTP with 8080, SOCKS5 with 1080, or socks5:// at the start of the line |
| The same error, with the right type | The login was cut, a colon is missing, or a space came with the paste | Copy the line again from the generator's Preview and paste it whole |
| The check worked yesterday, fails today | The plan expired or its traffic is used up | Check the plan in My proxies: status, remaining traffic, expiry date |
| "The proxy is functional but not working on your device or network" | Your network, firewall or antivirus blocks the connection to the proxy port | Try another network, such as a phone hotspot, and allow GoLogin and the port in the firewall or antivirus |
| The proxy fails only after setting a custom DNS | GoLogin applies custom DNS only with SOCKS4 and SOCKS5 proxies | Switch to SOCKS5 on port 1080, or remove the custom DNS |
| Wrong country, or a site shows your real location | No -country- in the login, or the site reads the browser's geolocation | Generate the line with a country; set the profile's Geolocation to Blocked or to coordinates in the proxy's country |
| The IP changes in the middle of a session | The session lifetime ended, or two profiles share one session ID | A longer -ttl- and a different -sid- in every profile |
One test outside the browser settles most cases in a minute. If this returns an address in the right country, the proxy works and the problem is in the profile's fields:
curl -x http://residentialpremium.quantumproxies.io:8080 \
-U "USER-country-de-sid-test-ttl-10m:PASS" https://ipinfo.io/jsonIf the same command fails on your network but works from another one, the network is blocking the proxy port, the case GoLogin's message above describes.
HTTP or SOCKS5 in GoLogin
Both work for browsing, and every QuanticData network offers both. HTTP on port 8080 is the simpler choice and the one to start with. SOCKS5 on port 1080 passes any kind of connection, not only web pages, and it is the one GoLogin needs if the profile uses a custom DNS; the details are on the page for SOCKS5 proxies. What breaks a profile is never the choice itself, only a type that does not match its port. For the same steps in another antidetect browser, see the same setup in Dolphin Anty; the plans are on the page for QuanticData residential proxies.
Before you run accounts
A proxy changes where a profile's traffic comes from, not what the profile is allowed to do. Keep to each platform's terms and to the law where you work, and use one profile, one session and one identity per account.