Advanced proxies and multi-hop routes

Use an advanced proxy when the provider gives you more than a standard HTTP, HTTPS, or SOCKS5 address. Use an upstream proxy when one proxy must connect through another.

Import an advanced proxy

1. Open Proxies and select “Add proxy.”
2. Select “Advanced proxy.”
3. Paste the JSON or YAML proxy configuration supplied by the provider.
4. Select “Check configuration” and verify the recognized node count, protocol, and server address.
5. Optionally choose a group or upstream proxy and add descriptive details.
6. Select “Import proxies.”

Accepted input shapes include:

• One standard proxy outbound object.
• A JSON configuration containing an outbounds array.
• A generic JSON or YAML configuration containing a proxies list.

Each valid node with a remote server address and port is saved separately. Routing-only entries such as direct, block, or selector are not saved as assignable proxies.

The protocol and fields must pass validation in the current client. Do not infer compatibility from a file extension or provider name; use the actual result shown by “Check configuration.”

Handle multiple recognized nodes

If the check finds several nodes, the import creates a separate proxy record for every valid node. The selected group, upstream proxy, and descriptive details apply to that import.

Before importing, confirm that:

• The node count is broadly consistent with the provider configuration.
• The displayed protocols and server addresses are expected.
• The configuration does not accidentally contain unrelated production or personal nodes.
• A single pasted configuration is no larger than 1 MiB and contains no more than 100 valid remote nodes. Ask the provider to split a larger configuration and import each part separately.

An advanced proxy currently has no edit action. To change any connection field, group, upstream proxy, or descriptive detail, first prepare a new import with the correct information. Then close the profile, remove its assignment to the old proxy, delete the old record, import the replacement, and assign the new record.

Understand “upstream proxy”

If proxy B is selected as the upstream proxy of proxy A, the connection order is shown as:

Browser profile → Proxy A → Proxy B → Internet

The profile is still assigned only to proxy A. A is the entry node, and B is A’s upstream proxy and the final exit in this example. B can have another upstream proxy to form a longer route.

We recommend creating the route from the final exit inward:

1. Add and check final exit proxy B first.
2. Add entry proxy A and choose B as A’s upstream proxy.
3. Save A, then run “Check full connection” from A’s action area.
4. Assign A to the browser profile.

A proxy cannot use itself as its upstream proxy, and circular routes are not allowed.

Check a multi-hop route

“Check full connection” verifies progressively longer route prefixes: hop 1, then hops 1–2, and so on until the complete route. The result shows the connection order and identifies the first failing hop.

If hop 2 fails, do not only replace the second node. Also check whether:

• Hop 1 allows connections to hop 2’s address and port.
• Hop 2 restricts the source IP.
• Authentication, TLS, or transport parameters are correct on both nodes.
• The local network blocks a protocol used anywhere in the route.

A complete route normally has more latency than one node. Judge it by reachability, the actual exit, and stability across repeated checks rather than latency alone.

Take care when changing a route

• Close every browser profile using the route first.
• After changing the upstream proxy of a standard node, run the full connection check again.
• Deleting, expiring, or disabling any node in the route can prevent an assigned profile from starting.
• A complete route already used by one profile is not offered for duplicate assignment to another profile.