What type of proxy do I need for GoLogin?

For browsing inside a profile, a residential proxy with a sticky session: the IP belongs to a home connection in the country you chose and stays put while the profile is open. If a profile needs the same US address for weeks, a Static Residential IP never rotates. Datacenter IPs are fine for testing your own sites.

Should I choose HTTP or SOCKS5 in GoLogin?

Both work with Evomi. HTTP on port 1000 is the simpler default and carries HTTPS sites without trouble. Pick SOCKS5 on port 1002 if you want GoLogin's Custom DNS setting, which only works with SOCKS proxies.

How do I keep the same IP on a GoLogin profile?

Add a session parameter to the Evomi password. _session-ID holds the IP for 30 minutes by default and up to 24 hours with _lifetime-1440, while _hardsession-ID keeps it for as long as possible. Give every profile its own ID so no two profiles share an address.

Why does my GoLogin profile show the wrong timezone?

GoLogin takes the timezone from the proxy's IP while 'Fill timezone based on the external IP' is on. If it looks wrong, check that the toggle is on, that the country in your Evomi password is the one you meant, and which IP the profile is really using at ip.evomi.com/s.

Is it allowed to use GoLogin with proxies?

GoLogin and proxies are ordinary tools, and the rules come from the sites you use them on: each site's terms decide whether automation, several logins or a given location are allowed. Use them for testing, localization checks, ad verification, privacy and your own business accounts, not to create or run accounts a platform does not permit.

GoLogin Proxy Setup with Evomi Residential IPs

Connect an Evomi residential proxy to a GoLogin profile, keep the profile's timezone and language in step with its IP, and fix the errors that stop a profile from launching.

Try for Free View Pricing

Money Back Guarantee Superior Support

Trusted by brands worldwide

Setup

Add an Evomi proxy to a GoLogin profile

GoLogin keeps each profile's cookies and browser fingerprint apart, but it still has to be told which network to use. Evomi Residential runs through a single gateway, so every profile gets the same host and port and differs only in the password.

Copy your Residential username and password from the Evomi dashboard. Evomi's Proxy Generator can build the password with a country and a session already added.
In GoLogin, open the profile's three-dot menu and go to Settings → Proxy → Your proxy. On the All profiles page, the + in the Location column opens the same form.
Enter host rp.evomi.com with port 1000 for HTTP or 1002 for SOCKS5, then your username and password.
Press Check proxy. Green means GoLogin reached the internet through Evomi. Red means one of the details is wrong; the troubleshooting list below covers the usual ones.
Launch the profile and open https://ip.evomi.com/s, which prints the IP the profile is using.

GoLogin also accepts a pasted line in host:port:login:password form, so rp.evomi.com:1000:USERNAME:PASSWORD_country-US_session-gl01prof fills every field at once.

Sessions

Give each profile a sticky session

Without a session parameter, Evomi assigns a new residential IP to every request. That suits bulk data collection, but a browser profile should keep one address while it is open. Otherwise a site sees the same cookies arrive from a different place on every page. Add one of three parameters to the password, with an ID of 6 to 10 letters and digits that belongs to that profile alone:

_session-ID keeps the IP for 30 minutes by default. Add _lifetime-120 for two hours, up to 1440 for 24 hours. It may move to a new IP to keep the connection up.
_hardsession-ID keeps the same IP for as long as possible and ignores _lifetime. It suits long working sessions on an account your team owns.
_lockedsession-ID never switches. If that IP goes offline, requests fail instead. Use it when a silent IP change would spoil the result, such as a QA run you would rather repeat.

To move a profile to a new IP, change its session ID. To keep the same ID but get a fresh address, call Evomi's rotation endpoint, GET https://api.evomi.com/public/rotate_session, with the session ID and your API key.

Location

Match the profile's location to its IP

Evomi residential IPs cover 195+ countries, and the location goes in the password: _country-DE for a country, _region-california for a state or province, or _city-paris for a city, written in lowercase with dots for spaces (new.york). Combine it with a session, for example PASSWORD_country-FR_session-gl02fr.

GoLogin then aligns the rest of the profile with that IP, as long as its defaults stay in place:

Fill timezone based on the external IP and Fill geolocation based on the external IP are on by default. Leave them on.
Set Languages to Based on IP so the profile asks sites for the local language.
Set WebRTC to Based on IP so WebRTC reports the proxy address rather than your own connection.

This is what makes location work worth trusting. A check of how a localized price, ad or consent banner looks in a market only means something when the IP, timezone and language all describe a visitor from that market. The same alignment helps teams that look after their own company's regional storefronts or ad accounts from one office, within each platform's rules.

Troubleshooting

When GoLogin's proxy check fails

Red check, or "Wrong proxy settings, bad connection". Compare host, port, username and password with the dashboard character for character. The port has to match the protocol: 1000 is HTTP and 1002 is SOCKS5.
"Socks5 proxy rejected connection". Usually SOCKS5 chosen against the HTTP port, or a typo in the credentials.
Errors right after you edit the password. Every parameter starts with an underscore, and session IDs are 6 to 10 letters or digits. A _lifetime above 1440 is refused with error 412, and so is a city with no available IPs.
The IP changes while a profile is open. The password has no session parameter, or a _session outlived its lifetime. Switch to _hardsession for long sittings.
Custom DNS has no effect. GoLogin applies Custom DNS only to SOCKS proxies, so use port 1002.
The check passes in GoLogin's web app but not on your computer. Something on that machine is in the way: a firewall, a corporate VPN, or another app that changes how it connects to the internet.
It worked yesterday. Check your traffic balance in the dashboard; Residential is billed per GB.

One gateway for every profile

Every GoLogin profile connects to rp.evomi.com on port 1000 or 1002. Location and session live in the password, so moving a profile to another market means editing one string.

FAQ

GoLogin proxy questions

Open the profile's menu and go to Settings, Proxy, Your proxy. Enter rp.evomi.com, port 1000 for HTTP or 1002 for SOCKS5, and your Evomi username and password, then press Check proxy. You can also paste one host:port:login:password line and GoLogin fills in the fields for you.