PacketStream integration
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
Close existing Chrome windows, then launch a separate instance with PacketStream’s HTTPS endpoint.
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'
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-servervalue. An existing browser process can ignore new launch flags. - Keep
https://in the proxy argument and pair it with port31111. - 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.