PacketStreamPacketStream integration
Using PacketStream residential proxies on Windows
Set PacketStream as the Windows 11 system proxy, sign in at the browser prompt, and check the exit IP, or use Chrome's encrypted setup instead.
For browsing on Windows, start with the Chrome guide. Its launch command opens a separate Chrome window through PacketStream’s encrypted HTTPS endpoint and leaves the rest of Windows alone.
Use the Windows proxy setting when you need a system-wide proxy. Windows has no field for a proxy username and password, so browsers ask for them. Many other apps and Windows features can’t answer that request and fail while the proxy is on.
Before you start
Copy these values from the Proxy Access page in your dashboard:
| Field | Value |
|---|---|
| Proxy IP address | proxy.packetstream.io |
| Port | 31112 |
| Username | Your Proxy Username, entered at the browser prompt |
| Password | Your Proxy Password (auth key), with optional suffixes, entered at the browser prompt |
Leave Protocol on that page set to HTTP Proxy so it shows port 31112. Choosing a Location or Sticky IP adds the matching suffix to the Proxy Password for you.
Every app that follows the system proxy sends its traffic through PacketStream. All of it is billed at $1 per GB, so turn the proxy off when you finish.
Configure
These steps follow Microsoft’s documentation for Windows 11.
- Open Settings > Network & internet > Proxy.
- Under Manual proxy setup, next to Use a proxy server, select Set up.
- Turn on Use a proxy server.
- Enter
proxy.packetstream.ioin Proxy IP address. The field accepts a host name. Enter31112in Port. - Select Don’t use the proxy server for local (intranet) addresses.
- Select Save.
- Open your browser and load a page. When it asks for proxy credentials, enter your username and password.
To stop using PacketStream, open the same dialog, turn off Use a proxy server, and select Save.
Verify your exit
Open ipinfo.io in the browser and check the IP and country.
Country targeting and sticky sessions
Keep the username unchanged and add suffixes to the password you enter at the browser prompt.
| Goal | Password |
|---|---|
| New exit per connection | AUTH_KEY |
| United States exit | AUTH_KEY_country-US |
| Keep one exit | AUTH_KEY_session-browser42 |
| Both | AUTH_KEY_country-US_session-browser42 |
- Without a session, each new connection can get a different exit, and one page load opens several connections. Use a session for logins and other multi-step browsing.
- Use only letters and digits in the session label. Everything from the first other character is dropped, so
my-phonebecomesmy. - A session ends after 60 minutes without a new connection. It also fails if the Packeter providing the exit disconnects; choose a new label to continue.
- To get a valid code, choose the country in the Location list on the Proxy Access page; the generated password then carries the right suffix. An unrecognized code is ignored and you can get an exit in any country, so check the country at ipinfo.io after you change it.
- If no exit is available in a recognized country, requests fail instead of using another country.
Browsers usually keep the credentials until they quit. To switch country or session, close the browser completely, reopen it, and enter the new password at the prompt.
See rotation and sticky sessions and country targeting for details.
Which apps use it
- Edge, Chrome, and Firefox (in its default system-proxy mode) use it and ask for your username and password on the first proxied request.
- Other apps that follow the Windows setting use it too. Apps that can’t show a password prompt, including many background updaters, fail, often without an error. Expect some apps and Windows features to fail or keep retrying while the proxy is on.
- Windows services that keep a separate WinHTTP proxy setting aren’t affected. Don’t copy this proxy into it with
netsh winhttp import proxy: services can’t answer a password request.
Why port 31112
PacketStream recommends its HTTPS endpoint on port 31111, which encrypts the connection to the gateway. Windows proxy settings can only describe a plain HTTP proxy; an HTTPS proxy can’t be set there. Port 31111 expects an encrypted connection from the first byte, so a system setting pointed at it fails.
With port 31112:
- https:// sites stay encrypted end to end.
- Your username, auth key, and the hostnames you visit reach the gateway unencrypted, and so do plain http:// pages.
- Use the setup only on networks you trust. If your auth key may have been exposed, select Reset Proxy Password on the Proxy Access page.
For browsing only, the Chrome and Firefox guides use port 31111 and keep that connection encrypted.
Limitations
- Windows can’t store proxy credentials. Browsers prompt for them; apps without a prompt fail.
- The system proxy carries web traffic over TCP only. Traffic over UDP, such as browser video calls (WebRTC), may still connect directly. Don’t rely on this setup for anonymity.
- Windows’ built-in proxy settings can’t use PacketStream’s SOCKS5 endpoint. They support only SOCKS4, without a username and password.
Troubleshooting
- The browser shows no prompt and pages don’t load. Check that the address is
proxy.packetstream.ioand the port is31112. Port31111doesn’t work in system settings. - The prompt keeps coming back. Check the username and password for typos or extra spaces.
- A new suffix doesn’t take effect. Close the browser completely and enter the new password at the next prompt.
- An app or Windows feature stops working. Turn the proxy off. This setup is meant for browsers.
See proxy troubleshooting for authentication, targeting, and rotation checks.