Proxy Format Guide: Host, Port, Credentials and Protocol

Match the format your tool actually accepts

A proxy line describes how to connect, not whether a retailer will accept the resulting request. Read your tool's import instructions and the provider's export options before converting a list. The protocol and authentication method matter as much as the field order.

These examples use a reserved example hostname and fake credentials:

gateway.example:8000:demo-user:demo-pass
http://demo-user:demo-pass@gateway.example:8000

The first is a common four-field list format. The second is a URI with an explicit HTTP scheme. They are not interchangeable in every application. Neither example is a working proxy.

Know each field

Field	Purpose	Common mistake
Host	Gateway hostname or IP	Copying a target website instead
Port	Proxy listener	Assuming the target's 443 port is the proxy port
Username	Authentication and sometimes routing options	Removing provider country or session parameters
Password	Proxy credential	Adding spaces or exposing it in screenshots
Scheme	HTTP, HTTPS or SOCKS as documented	Treating all protocols as equivalent

An HTTPS destination can be reached through an HTTP proxy using a CONNECT tunnel. The destination's HTTPS URL does not automatically mean you should prefix the proxy with https. Use the scheme the provider and client support.

Convert carefully

If the client accepts authenticated URIs, reserved characters in credentials may need percent encoding. If it accepts separate fields, it may require the raw values instead. A colon in a password can make a naive four-part splitter fail. Do not rewrite credentials blindly or strip suffixes to make a validator turn green.

Keep one entry per line when the tool requires it. Remove accidental blank lines and leading or trailing whitespace, while preserving meaningful credential characters. IPv6 addresses also need the client's documented syntax; a validator built for simple four-field samples cannot establish full IPv6 compatibility.

Diagnose a failed import

Symptom	First check
Tool rejects the list immediately	Field order, delimiter and supported protocol
407 response	Proxy authentication method and credentials
Connection refused or timeout	Gateway, port, local firewall and service status
Neutral test works but retailer denies access	Target response and permitted use, not text formatting

Proxy authentication is separate from a retailer account login. Do not put your store password in proxy fields.

Use the validator for text shape only

The RestockRoute format validator checks a non-sensitive sample in the browser. It does not authenticate credentials, check balance, reserve an exit or contact a retailer. After fixing the sample, follow the small-sample test checklist in a trusted tool. Never paste a real proxy password into a public example or shared report.