Using PacketStream Residential Proxies with Chrome

Set up PacketStream in Chrome with its built-in HTTPS proxy flag, authenticate at the prompt, and check your residential exit.

Need to see what a page returns through a residential IP? Launch a separate Chrome instance through PacketStream, then browse normally without installing an extension.

Configure

Launch a separate Chrome instance with PacketStream’s HTTPS endpoint. On Linux, close existing Chrome windows first. On macOS, quit Chrome completely with Chrome > Quit Google Chrome or Command-Q. Closing its windows leaves Chrome running, and the running Chrome ignores the flag.

On Linux:

google-chrome --proxy-server='https://proxy.packetstream.io:31111'

On macOS:

'/Applications/Google Chrome.app/Contents/MacOS/Google Chrome' \
  --proxy-server='https://proxy.packetstream.io:31111'

On Windows, --user-data-dir gives this instance its own profile. It starts even while your normal Chrome is running, and its cookies stay separate. In PowerShell:

& "$env:ProgramFiles\Google\Chrome\Application\chrome.exe" `
  --user-data-dir="$env:LOCALAPPDATA\PacketStreamChrome" `
  --proxy-server="https://proxy.packetstream.io:31111"

In Command Prompt:

"C:\Program Files\Google\Chrome\Application\chrome.exe" --user-data-dir="%LOCALAPPDATA%\PacketStreamChrome" --proxy-server="https://proxy.packetstream.io:31111"

If Windows can’t find chrome.exe, Chrome may be installed for your account only. Use %LOCALAPPDATA%\Google\Chrome\Application\chrome.exe instead. Older installs can be in C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. The flag applies only to this instance and doesn’t change the Windows proxy setting. To start fresh, close the window and delete the %LOCALAPPDATA%\PacketStreamChrome folder.

Chrome prompts for proxy credentials on the first proxied request. Enter your PacketStream username as the username and your dashboard auth key as the password. Keep credentials out of the launch command.

This uses Chrome’s built-in proxy setting. No browser extension is needed.

Chrome’s SOCKS5 launch flag does not provide the authenticated username and password flow needed for this setup, so use PacketStream’s HTTPS endpoint.

Verify your exit

Open ipinfo.io in the launched browser. Check the displayed IP and country before navigating to the page you want to inspect.

Country targeting and sticky sessions

Keep the username unchanged. Enter the modified password in Chrome’s proxy credential prompt:

AUTH_KEY_country-US_session-browser42

The launch command and proxy endpoint stay the same.

Troubleshooting

Close every existing Chrome process before using a different --proxy-server value. An existing browser process can ignore new launch flags. On Windows, close the windows that use the PacketStreamChrome profile; your normal Chrome can stay open.
Keep https:// in the proxy argument and pair it with port 31111.
A refresh or new tab can reuse the current proxy connection and exit. It does not force rotation.

See proxy troubleshooting for authentication prompts, endpoint pairing, TLS, and rotation checks.

Using PacketStream residential proxies with Chrome

Configure

Verify your exit

Country targeting and sticky sessions

Troubleshooting

Related