Set up IPFoxy proxies

MaskPilot does not require access to your IPFoxy account or a synchronized provider key. Obtain a directly usable protocol, server address, port, username, and password from IPFoxy, then save those fields as a standard proxy.

Get connection details from IPFoxy

Static proxies are normally available from the purchased proxy list. For a rotating proxy, first choose the exit location, route, and session behavior in the IPFoxy dashboard, then generate the connection details.

Common hosts and ports

Product or route	Server	Port	Protocol	How to use it
Rotating residential · Asia-Pacific route	gate-sg.ipfoxy.io	58688	HTTP / SOCKS5	The Singapore entry is used; username parameters select the exit location
Rotating residential · Americas route	gate-us.ipfoxy.io	58688	HTTP / SOCKS5	The US entry is used; username parameters select the exit location
Static IPv4, IPv6, or ISP proxy	IP or hostname assigned in the dashboard	Port assigned in the dashboard	HTTP or SOCKS5	Values can differ per node and must be copied from the static proxy list

58688 is the current unified port for IPFoxy rotating residential proxies. IPFoxy still accepts the legacy SOCKS5 port 58622 and HTTP port 58611 for existing connections; use the current dashboard value, normally 58688, for a new setup. The entry route does not determine the final exit location.

Confirm these fields before copying:

• Protocol: use the HTTP or SOCKS5 option currently supplied for the endpoint instead of inferring it from the port.
• Server and port: use the entry address and port shown for this generated connection.
• Username and password: location, city, or session parameters may already be embedded in a rotating-proxy username; preserve the complete value.
• Expiry: when a static node has an expiry date, you can also record it in MaskPilot.

IPFoxy may change its available routes and parameters. Use the current dashboard output and the official IPFoxy parameter guide as the source of truth.

Add one IPFoxy proxy

1. Open Proxies in MaskPilot and select “Add proxy.”
2. Select “Standard proxy.”
3. Choose HTTP, HTTPS, or SOCKS5 according to the IPFoxy connection details.
4. Enter the server address, port, username, and password in their separate fields.
5. Set Provider to IPFoxy and optionally record the region, expiry date, and a note.
6. Save the proxy, then select “Check connection” on its row.

Enter only a hostname or IP address in the server field. Do not put a protocol, port, refresh URL, or dashboard link there. A rotating-proxy refresh URL is not a proxy server address.

Bulk import endpoints

When IPFoxy exports several connections, open Bulk import and paste one node per line. Normalize the values to one of these formats:

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. If the copied value uses socks5://host:port:username:password, do not import it as a URL and do not simply remove the protocol. Convert it to the standard authenticated URL socks5://username:password@host:port, URL-encoding reserved characters in credentials. If it cannot be converted safely, use Add proxy and enter each field manually. Check the recognized count first and review every imported protocol, port, and connection result.

Assign it to a browser profile

1. Create or edit a browser profile.
2. Under Network connection, select “Use proxy.”
3. Select “Choose proxy” and find a checked node whose provider is IPFoxy.
4. Select the node, save, and then launch the profile.

A rotating proxy can change its exit per request or per session. If the browser session requires a stable exit, generate a sticky-session connection in IPFoxy first. Do not remove session parameters from the username in MaskPilot.

If the check fails

• Copy the complete username again and make sure location and session parameters were not truncated.
• Confirm that the selected protocol matches the current entry port.
• Verify that the node, plan, credentials, and provider-side source-network rules are still valid.
• IPFoxy currently requires a connection from a network outside mainland China; do not remove the provider-required reachable network path while retesting.
• If only bulk-imported nodes fail, add one endpoint manually for comparison.
• If the check succeeds but the profile cannot start, check the launch-time exit and time-zone lookup next.

See Why does a proxy check fail? and Why can’t a profile start after assigning a proxy? for the complete diagnosis flow.