Skip to content
Anti-detect browsers

How to use proxies with GoLogin

GoLogin sets a proxy per profile and can run profiles either locally or in the cloud. When profiles run in the cloud the traffic still exits through your configured proxy, so the same per-profile IP discipline applies.

Recommended for GoLogin

ISP proxies Persistent profiles want a persistent address, and ISP IPs carry a clean fraud score that platform risk engines do not flag.

See isp proxies

Setup

  1. 1

    Create the profile

    Add a profile and choose the OS and browser fingerprint you want it to present.

  2. 2

    Configure the proxy

    In the profile's proxy section select a custom HTTP or SOCKS5 proxy and enter host, port, username and password. Replace PROXY_HOST, PROXY_PORT, USERNAME and PASSWORD with the endpoint and credentials shown in your seamless dashboard.

  3. 3

    Check the detected location

    GoLogin displays the country it detects for the proxy. Confirm it matches what you intended before using the profile.

  4. 4

    Align timezone, locale and WebRTC

    Set these to follow the proxy so the browser's declared location and its network location agree.

GoLogin proxy FAQ

Does GoLogin work with SOCKS5 proxies?

Yes. GoLogin supports HTTP, HTTPS and SOCKS5 per profile, and seamless proxies work over any of them with the same credentials.

Should each GoLogin profile have its own proxy?

Yes, if the profiles represent accounts that must not be linked. A shared IP is one of the strongest association signals available to a platform.

Do cloud profiles still use my proxy?

Yes. A cloud-run profile still routes its traffic through the proxy configured on that profile, so the exit IP the target sees is yours rather than GoLogin's.