Skip to content
Guides

How to Connect to Your GlobProxy Proxy: A Step-by-Step Setup Guide

·7 min read

Connecting a GlobProxy session takes four values and one test command. Nearly every failed first attempt comes from the same handful of mistakes: copying only part of the username, using the wrong port for the session type, or testing in the first few minutes before new credentials have finished syncing. This guide walks the whole path, then covers the errors people hit most.

One word to pin down first. In the dashboard, a session is one set of proxy credentials with its own GB allocation, listed under My Proxies. Sticky sessions (covered below) are named endpoints that live inside it.

Before you start

You need a session with bandwidth on it. If you have not created one yet, buy bandwidth first, then go to My Proxies and choose New session. If your account has no unallocated GB, the New session page sends you to Buy Bandwidth instead.

Step 1: Find your connection details

  1. 1Sign in and open My Proxies in the left sidebar.
  2. 2Click your session's row to expand it.
  3. 3Open the Credentials tab. It shows four fields: Host, Port, Username and Password. The password stays hidden until you click show.
  4. 4Use the copy button beside each field rather than retyping. The username is long, and everything after the first dash matters.

For a one-click version, the copy button (⧉) on the session row copies the whole endpoint in host:port:username:password form, which is the format most scraping tools and anti-detect browsers import.

What the username is made of

The username is not just an ID. Your location choices are part of it, which is why a connection exits where you picked without any extra setup.

A rotating session targeted to Austin, Texas (your base ID will differ)
text
gp_3f9a1c7e2b8d4a6f0c15-type-residential-country-us-state-texas-city-austin
  • →gp_3f9a… is your session's base ID.
  • →-type-residential is the network type.
  • →-country-us-state-texas-city-austin is the location. State and city are optional; an ISP appears as -asn-<number> if you chose one instead of a state or city (an ISP is country-wide, so it is not combined with them). A session created with Any country has no location part at all.

A sticky username adds two more parts that hold one exit IP for a set time:

text
gp_3f9a1c7e2b8d4a6f0c15-type-residential-country-us-state-texas-city-austin-lifetime-60-session-Ab3dE9xQ

-lifetime-60 is how many minutes the IP is held, and -session-Ab3dE9xQ identifies that one sticky IP. Because location lives in the username, changing a session's location later means copying the username again. Anything still using the old one keeps the old location.

Step 2: Use the right port

ProtocolIP behaviourPortTypically used for
HTTP / HTTPSRotating9000Scrapers, browsers and most libraries
HTTP / HTTPSSticky10000Logins and multi-step flows that must keep one IP
SOCKS5Rotating11000Tools that only speak SOCKS5
SOCKS5Sticky12000The same, with a fixed IP

You do not pick a port freely. It is fixed by the protocol and IP behaviour chosen for the session, and the Credentials tab always shows the matching one. Pairing a username with the wrong port is a common reason for a request that hangs or resets, so use the port on the card.

Step 3: Test with one command

Before touching your own code, confirm the proxy works. This request asks a public service which IP it sees:

bash
curl -x "http://YOUR_USERNAME:YOUR_PASSWORD@proxy.globproxy.com:9000" https://ipinfo.io/json

For a SOCKS5 session, change the scheme and port: socks5h://…@proxy.globproxy.com:11000. The h makes the proxy resolve DNS, so your own resolver is not involved.

On Windows PowerShell, type curl.exe

In Windows PowerShell, plain curl is an alias for a different command and rejects the -x option. Use curl.exe instead, or run the command in Command Prompt or Git Bash.

You should get a small JSON reply with an ip, plus city, region and country. Check the country against your targeting. Public geolocation databases are estimates, so a nearby town in the reply does not mean targeting failed, but a different country does. On a rotating session, running the command twice should show two different IPs.

Step 4: Set it up in your tool

The Code snippets tab on each session generates all of the following with your real values already filled in. Copy from there when you can. The examples below show the shape with placeholders.

Python (requests)

python
import requests

proxy = "http://YOUR_USERNAME:YOUR_PASSWORD@proxy.globproxy.com:9000"
proxies = {"http": proxy, "https": proxy}

response = requests.get("https://ipinfo.io/json", proxies=proxies, timeout=30)
print(response.json())  # shows your proxy IP and location

For SOCKS5, install pip install "requests[socks]" and use socks5h://YOUR_USERNAME:YOUR_PASSWORD@proxy.globproxy.com:11000 as the proxy value.

Node.js

npm install https-proxy-agent node-fetch@2
javascript
const { HttpsProxyAgent } = require("https-proxy-agent");
const fetch = require("node-fetch");

const agent = new HttpsProxyAgent(
  "http://YOUR_USERNAME:YOUR_PASSWORD@proxy.globproxy.com:9000"
);

(async () => {
  const res = await fetch("https://ipinfo.io/json", { agent });
  console.log(await res.json()); // shows proxy IP and location
})();

Playwright and Puppeteer

Both drive Chromium, which cannot authenticate to a SOCKS5 proxy. Use a session set to HTTP / HTTPS for browser automation. You can change an existing session's protocol on its Edit tab.

Playwright — npm install playwright
javascript
const { chromium } = require("playwright");

(async () => {
  const browser = await chromium.launch({
    proxy: {
      server: "http://proxy.globproxy.com:9000",
      username: "YOUR_USERNAME",
      password: "YOUR_PASSWORD",
    },
  });
  const page = await browser.newPage();
  await page.goto("https://ipinfo.io/json");
  console.log(await page.textContent("body"));
  await browser.close();
})();
Puppeteer — npm install puppeteer
javascript
const puppeteer = require("puppeteer");

(async () => {
  const browser = await puppeteer.launch({
    args: ["--proxy-server=http://proxy.globproxy.com:9000"],
  });
  const page = await browser.newPage();
  await page.authenticate({ username: "YOUR_USERNAME", password: "YOUR_PASSWORD" });
  await page.goto("https://ipinfo.io/json");
  console.log(await page.evaluate(() => document.body.innerText));
  await browser.close();
})();

A regular browser

A browser's own proxy settings do not take a username and password in one place, so a proxy-switching extension such as Proxy SwitchyOmega (Chrome and Firefox) is the simplest route. Enter:

FieldValue
ProtocolHTTP
Hostproxy.globproxy.com
Port9000 (or the port on your Credentials tab)
UsernameThe full username from Step 1
PasswordYour session password

Scrapers, anti-detect browsers and other tools

Most of these accept one line per proxy in host:port:username:password form:

text
proxy.globproxy.com:9000:gp_3f9a1c7e2b8d4a6f0c15-type-residential-country-us:YOUR_PASSWORD

On a rotating session, the Endpoint tab has copy all and .txt buttons that produce exactly this. On a sticky session, the Sticky sessions tab has the same for every named session. Treat the downloaded file like a password, because it contains one.

Rotating or sticky: which endpoint am I using?

A rotating endpoint gives each new connection a fresh IP. One endpoint serves any number of simultaneous connections, so there is no need to create several; they all draw from the same session bandwidth.

A sticky session holds one IP for its lifetime, which you can set from 1 minute to 24 hours. On a sticky session, the username on the Credentials tab is only a ready-made example. Open the Sticky sessions tab and choose + new session (you can create 1, 5, 10 or 25 at once, up to 200 per session). Each named session is its own fixed endpoint with its own IP. Remove hides one from the list but its IP keeps working until the lifetime ends; Delete frees the endpoint.

If it does not connect

What you seeLikely causeWhat to do
407 Proxy Authentication Required in the first minutesNew credentials take a few minutes to sync across the network. The card shows warming up for about 10 minutes after activation.Wait a couple of minutes and retry. If it persists past 10 minutes, re-copy the username and password.
407 that never goes awayThe username or password is incomplete or out of date. Most often the username was truncated, or the password was rotated after you copied it (rotating invalidates the old one at once).Re-copy both values in full from the Credentials tab.
Request hangs, is refused or resetsWrong port or protocol (for example a SOCKS5 client on an HTTP port), or your network blocks outbound traffic on that port.Use the port shown on the card. Try from a different network to rule out a firewall.
Exit IP is in the wrong country or cityLocation lives in the username. You may be using a copy from before an edit, or the session was created with Any country.Open the Edit tab, check Country, State and City, save, then copy the username again. Changes apply to new connections only.
Session says it is queuedThe network is adding capacity. Your GB is already reserved.Nothing. It activates on its own.
Red banner: not responding on our networkA fault on our side. We are alerted and your bandwidth is safe.Retry in a while. Contact support if it lasts.
Nothing works and Remaining shows 0 GBThe session's allocation is used up.On the Bandwidth tab, top up from your unallocated balance, or buy more bandwidth first.
The session badge says SUSPENDEDIt was paused by you, your account was suspended, or our team disabled it. The banner inside the session says which.If you paused it, choose Resume session. Otherwise contact support from the banner.
Playwright or Puppeteer fails on a SOCKS5 sessionChromium cannot authenticate to SOCKS5.Use an HTTP / HTTPS session for browser automation.
Stopped working after changes on the Whitelist tabWhitelist entries are the one thing in this guide you may have changed beyond the four credentials.Remove the entries, retest, and contact support if the problem remains.

Keep your password private

The password sits inside connection strings, which tend to end up in shell history, logs and repositories. Read it from an environment variable or secret store instead of hard-coding it. If it leaks, open the Credentials tab and choose Rotate password. The old password stops working immediately, so update everything that used it. Rotation is only offered where it is currently available.

Still stuck?

Open Support in the dashboard sidebar and quote the session's label. Include the exact error and the output of the Step 3 test, with the password removed. That is usually enough for us to find the cause without a back-and-forth.

Frequently asked

Do I need to whitelist my IP to connect?
No. The setup in this guide uses only the username and password from the Credentials tab. There is no whitelist step.
Should I choose HTTP or SOCKS5?
HTTP / HTTPS works with browsers and almost every library, and it is the only option for Playwright and Puppeteer. Choose SOCKS5 only for tools that specifically require it.
Can several machines or threads use the same endpoint at once?
Yes. One rotating endpoint serves any number of simultaneous connections. They all use the same session bandwidth, so heavy parallel use draws it down faster.
Why does my IP change on every request?
That is what a rotating session does. If you need the same IP across requests, use a sticky session and connect through one of its named sessions.
Will changing a session's location break connections already running?
Editing a session's location does not touch your bandwidth, and it applies to new connections. Anything still using the old username keeps the old location until you swap in the new one.
Does it work with HTTPS websites?
Yes. The examples above request an HTTPS address through an HTTP proxy port, which tunnels the encrypted connection.

Still stuck?

Email us at support@globproxy.com and include your account email and what you see on screen.

Contact support →