Set up Proxy302 proxies
Generate a region- and protocol-specific Proxy302 connection, then import its host, port, and credentials and assign it in MaskPilot.
Updated Aug 25, 2026MaskPilot does not connect to a Proxy302 account or purchase and target Proxy302 locations in the client. Select the product, exit location, protocol, and session behavior in Proxy302 first, then save the generated standard connection as a proxy.
Generate a Proxy302 connection
In the Proxy302 dashboard, choose the required static or rotating product and set the location, protocol, and other provider-side parameters before generating a connection. Copy:
Host and port reference
| Product or connection | Server | Port | Protocol | How to use it |
|---|---|---|---|---|
| Public Proxy302 setup example | proxy.proxy302.com | 2222 | HTTP or SOCKS5 according to the generated record | The user-provided reference calls this a common example; it is not a universal fixed entry |
| Actual proxy from an overseas network | Proxy address generated by Proxy302 | Port from the same generated record | HTTP or SOCKS5 selected during generation | Host, port, username, and password must come from one record |
| Proxy302 helper tool | LAN address shown by the helper | LAN port shown by the helper | Match the helper’s current mode | Valid only through the device running the helper; do not substitute a remote example host |
Proxy302’s official documentation does not promise one universal host and port for every product. proxy.proxy302.com:2222 comes from the referenced setup guide and is only a common field example. If the Proxy302 dashboard displays another value, use the current generated record.
- The protocol currently supplied by Proxy302, such as HTTP or SOCKS5.
- The proxy host and port.
- The proxy username and password, or the IP allowlist requirement.
- The node expiry, traffic, and session policy.
Do not use a dashboard page, API, or speed-test URL as the proxy host. The protocol, address, port, and credentials must come from the same generated record. Proxy302’s own troubleshooting guide also asks users to verify these fields together; see the official Proxy302 connection guide.
Add one Proxy302 proxy
- Open Proxies in MaskPilot and select “Add proxy.”
- Select “Standard proxy.”
- Choose HTTP, HTTPS, or SOCKS5 according to the generated connection.
- Enter the proxy host, port, username, and password separately.
- Set Provider to
Proxy302and optionally record the region, expiry date, or purpose. - Save, select “Check connection,” and verify the exit region and latency.
The Region field in MaskPilot is only a label. It does not send location targeting to Proxy302. To change a country, state, city, or rotation behavior, generate the corresponding connection in Proxy302 first, then update or re-import the proxy.
Bulk import connections
When several proxies are generated, normalize them to one connection per line:
host:port:username:password
http://username:password@host:port
socks5://username:password@host:port
A host:port:username:password line without a scheme is imported as HTTP; keep the socks5:// prefix for SOCKS5 endpoints. Open Bulk import, paste the list, and verify the recognized count. A rotating-proxy username may contain location or session parameters, so preserve it in full. Successful import confirms the format was recognized; it does not replace protocol, port, and connection checks.
Assign it to a browser profile
- Create or edit a browser profile.
- Under Network connection, select “Use proxy.”
- Choose a successfully checked Proxy302 node.
- Save and launch the profile, then verify the actual exit.
Use a static proxy when a profile requires a fixed exit. Proxy302 parameters determine whether and how long a rotating proxy keeps an IP. Do not infer the current exit from the proxy name; use the live check before and after launch.
Common failure causes
- The protocol does not match the entry port.
- Address, port, username, and password came from different generated records.
- A rotating connection or static node expired, or traffic balance is insufficient.
- The current device’s public IP is missing from the source-IP allowlist.
- The device network cannot reach the Proxy302 entry.
- Proxy302 currently requires a reachable overseas network environment when connecting from mainland China; do not remove a required upstream route while retesting.
Check node status in Proxy302 first, then run the MaskPilot check again. See Why does a proxy check fail? for diagnosis and Add, import, and assign proxies for import and assignment formats.