Setup guide
Connect your static ISP proxies in a couple of minutes: credentials, curl tests, anti-detect browsers, and fixes for the common snags.
1Where your credentials live
As soon as an order is active, every proxy shows up in your dashboard with its host, port, username, password, protocol, location and expiry. Copy the values straight from there. A single proxy is delivered as four colon-separated parts:
HOST:PORT:USERNAME:PASSWORD
A filled-in example looks like this:
45.135.12.34:1080:ips_9f3a2c:Kp7xR2mQ
HTTP/HTTPS works on every line and is the safe choice; SOCKS5 is available on the lines that support it, and your dashboard shows which protocols your IP offers. See the next section for when to pick each. Keep the string private: anyone who has it can route traffic through your IP.
2HTTP or SOCKS5?
Every ipsurfer IP speaks HTTP/HTTPS, and the lines that support it also speak SOCKS5. Your dashboard shows which protocols your IP offers and the port for each, next to the proxy — if no SOCKS5 port is listed, that line serves HTTP only. Either way it's the same IP and the same username and password.
SOCKS5 — on supported lines
A low-level tunnel that forwards any TCP traffic and can resolve DNS remotely (that's the h in socks5h), which avoids DNS leaks. Use it when your dashboard lists a SOCKS5 port for that IP.
HTTP / HTTPS — recommended
The classic web proxy, supported on every ipsurfer line. It carries HTTPS traffic just fine and is accepted by every anti-detect browser, scraper and automation tool. When in doubt, use this.
Not sure which to choose? Go with HTTP — it works on every IP.
3Test it with curl
The fastest way to confirm a proxy is alive is curl. It prints the exit IP so you can check it matches. Swap in your host, port, username and password.
HTTP / HTTPS — works on every IP
curl -x http://HOST:HTTP_PORT -U "USERNAME:PASSWORD" https://ipinfo.io/json
SOCKS5 — if your dashboard lists a SOCKS5 port
curl -x socks5h://HOST:SOCKS_PORT -U "USERNAME:PASSWORD" https://ipinfo.io/json
Use the HTTP port with http:// and, where it is offered, the SOCKS5 port with socks5h://. Same host, same login, just a different port. The h in socks5hresolves DNS through the proxy so your real DNS isn't leaked.
A healthy response returns JSON whose ip, city and orgare the proxy's — not yours:
{
"ip": "45.135.12.34",
"city": "Dallas",
"region": "Texas",
"country": "US",
"org": "AS… ISP name"
}4Anti-detect browsers
Anti-detect browsers pin one proxy per profile. The fields are always the same. Map them from your proxy string:
- Proxy type — HTTP (recommended) or SOCKS5
- Host / Server — the HOST part — the IP
- Port — the PORT that matches your chosen protocol
- Username / Login — the USERNAME part
- Password — the PASSWORD part
Set the profile's proxy type to HTTP(or SOCKS5 if your dashboard lists it for that IP), paste the four values, then use the tool's Check / Testbutton. It should return the proxy's IP and country.
AdsPower
New or edit profile → Proxy Info. Set Proxy Type to HTTP (recommended), then fill Host, Port, Account (username) and Password. Click Check Proxy.
GoLogin
Open a profile → Proxy → Custom. Choose HTTP (recommended) or SOCKS5, enter host, port, username and password, then Check proxy.
Multilogin
Create or edit a profile → Proxy. Set Proxy type to HTTP (recommended) or SOCKS5, add host, port, username and password, then run Check.
Dolphin{anty}
Profile → Proxy → New proxy. Pick HTTP (recommended) or SOCKS5. You can paste the whole host:port:username:password string into the format field, then Check.
Octo Browser
New profile → Proxy → Add. Select HTTP (recommended) or SOCKS5, enter host, port, login and password (or paste host:port:login:password), then Check proxy.
5Regular browsers & extensions
For an everyday Chrome or Firefox session, a proxy-switcher extension is the easiest route. The built-in OS proxy settings handle proxy authentication poorly.
- Install FoxyProxy or Proxy SwitchyOmega.
- Add a profile, choose HTTP (or SOCKS5 if your dashboard lists it), and enter the host and matching port.
- Enable authentication and add your username and password.
- Toggle the profile on, then open ipinfo.io to confirm the IP switched.
On a phone:the system-wide proxy settings in iOS and Android usually can't pass a username and password along, so a proxy configured there can look connected and still fail to authenticate. Use something that takes credentials of its own — a browser with a proxy extension, or your anti-detect / automation app — and enter the username and password there.
6One login, the same IP, anywhere
Every proxy authenticates with its own username:password— that is the only authentication method: IP allow-listing (whitelisting) isn't available. It is also all you ever carry: nothing to re-register when you switch laptop, move office, or your home connection changes address.
- The exit IP is yours and stays the same, wherever you connect from.
- Works in anything that accepts a proxy with authentication: anti-detect browsers, scrapers, curl, proxy-switcher extensions, automation frameworks.
- Each IP carries its own credentials, so you can hand one line to a tool or a teammate without exposing the rest.
- Keep the string private — anyone who has it can route traffic through your IP. The username and password are fixed for the life of the line and can't be reset, so treat them like any other password.
Something not authenticating? Email support@ipsurfer.com.
7Troubleshooting
Authentication failed (407)
Re-copy the username and password with no leading or trailing spaces — every ipsurfer proxy authenticates with username:password, so both fields must be filled in. Confirm the port matches the protocol you picked: SOCKS5 and HTTP use different ports. Also check your tool is actually sending the credentials; some have a separate 'proxy requires authentication' switch.
Connection timed out or refused
First try HTTP — it's the protocol every line supports. If you were connecting as SOCKS5, switch your tool's proxy type to HTTP with the exact same host, port, username and password. Also make sure a firewall or VPN isn't intercepting the port, and run the curl test to isolate whether it's the tool or the proxy.
SOCKS5 doesn't connect but HTTP works
That's expected on some lines: every proxy speaks HTTP/HTTPS, but not every upstream node accepts SOCKS5. Use HTTP as the proxy type — it carries HTTPS traffic just fine and is what we recommend by default.
Proxy still shows “provisioning”
Freshly ordered IPs take a short while to activate upstream. Wait until the dashboard marks the proxy active before connecting. A proxy that hasn't finished provisioning will refuse connections.
The IP looks wrong or leaks my real location
Load ipinfo.io through the proxy (the curl test, or inside the browser profile). The ip and org should be the proxy's, not yours. If DNS leaks, use socks5h:// (remote DNS) rather than socks5://, and make sure the whole profile, not just one browser tab, routes through the proxy.
8Good to know
- Your IP is static — it stays the same while your subscription is active.
- Every IP speaks HTTP/HTTPS, plus SOCKS5 on supported lines — each on its own port. Your dashboard shows which.
- Renewals bill automatically each period; nothing to do on your side.
- Check status, manage, or cancel anytime from your dashboard.