Endpoints and authentication

All direct proxy customers connect to proxy.packetstream.io with username/password authentication. Use your PacketStream username as the username and your dashboard auth key as the password.

Endpoint reference

The HTTPS proxy encrypts the connection from your application to the PacketStream gateway. Requests to HTTPS destinations retain their own TLS protection through the proxy connection.

Do not disable certificate verification to work around a client configuration problem. Confirm that the library supports an HTTPS proxy—not merely an HTTP proxy used for HTTPS destinations—and that the local trust store is current.

Username/password authentication

The safest pattern is to supply credentials separately from the endpoint:

curl --proxy 'https://proxy.packetstream.io:31111' \
  --proxy-user "${PACKETSTREAM_USER}:${PACKETSTREAM_AUTH_KEY}" \
  'https://ipinfo.io'

Many libraries also accept a proxy URL containing credentials:

https://USERNAME:[email protected]:31111

Only use the URL form when the client requires it. A complete proxy URL is easy to expose in process lists, exceptions, analytics, or debug logs.

Auth-key modifiers

Targeting and session behavior are expressed as suffixes on the auth key:

Use non-sensitive session labels. Do not put email addresses, customer identifiers, destination credentials, or other personal data into a session ID.

SOCKS5 example

For cURL, use the PacketStream SOCKS5 endpoint on port 31113:

curl --proxy 'socks5h://proxy.packetstream.io:31113' \
  --proxy-user "${PACKETSTREAM_USER}:${PACKETSTREAM_AUTH_KEY}" \
  'https://ipinfo.io'

Outbound connectivity

Your runtime must be able to make outbound connections to the selected port. Proxy customers do not need inbound ports, NAT rules, or port forwarding.

If a connection fails before authentication, check:

• the hostname and port pairing;
• whether an outbound firewall permits the port;
• whether the client supports the selected proxy scheme;
• whether a corporate proxy or VPN is intercepting the connection.

Continue with rotation and sticky sessions once the base request succeeds.