ability to define entry and exit proxy for a proxy group (proxy chaining simplification)

[argio11]

In some countries there is a concept similar to an internet “whitelist”, where only a limited number of websites are accessible and most of the internet is blocked.

In such environments, sometimes it is possible to obtain a working proxy that is reachable despite these restrictions. However, many websites block traffic coming from such proxies.

To solve this, proxy chaining can be used:

• The first proxy in the chain is accessible under whitelist restrictions — let's call it proxy1
• The second proxy is the one that websites actually see — let's call it proxy2

Example chain:

proxy1 → proxy2

I have successfully configured such chains and they work well. However, problems appear when there are many proxies available.

For example, if I have 100 proxies, and proxy1 must always be the first node, I currently need to create 99 separate chains manually:

proxy1 → proxy2
proxy1 → proxy3
proxy1 → proxy4
proxy1 → proxy5
...

This is time-consuming and inconvenient to manage.

Proposed improvement

I would like the ability to specify a proxy through which all proxies in a selected group should be accessed.

For example:

I often have multiple proxy groups (usually subscription-based sources). I would like to configure a group so that all proxies inside that group automatically connect through a specified upstream proxy (for example proxy1).

A similar concept is described here:
https://wiki.metacubex.one/en/config/proxies/dialer-proxy/

WARP as entry node

If possible, please also allow WARP to be used not only as the final node in a chain, but also as the first node.

Example:

WARP → proxy

Currently WARP can typically only be configured as the exit node, but allowing it as the entry node would improve flexibility.

Exit node selection for proxy groups

Another useful scenario:

Some websites are only accessible from specific countries. In cases where I cannot connect directly to a proxy located in the required country, I need to create a proxy chain:

proxyA → proxyCountry

It would be very helpful to allow specifying not only the entry node (first proxy), but also the exit node (last proxy) for a proxy group.

In other words, similar to how WARP can currently act as the final node, it would be useful to allow any proxy to be defined as the final node for a group.

Summary of requested functionality

1. Ability to define an upstream proxy (entry node) for all proxies within a group
2. Ability to define a downstream proxy (exit node) for all proxies within a group
3. Allow WARP to be used both as entry and exit node
4. Reduce the need to manually create dozens of proxy chains

This feature would significantly simplify configuration and improve usability for users working in restricted network environments.

Thank you for your work!

[Mahdi-zarei]

This is already implemented. A group can have front or landing proxies which are exactly what you described. As for being able to configure warp as entry proxy, I cannot understand why it can be useful, warp is easily blocked via DPI, so it makes little sense to have it as the entry proxy in an environment where there is a strict censorship.

[argio11]

Thank you, this is indeed already implemented — I just wasn’t aware of it. However, there is one major usability issue.

When selecting a proxy in the following places:

• front-proxy
• landing proxy
• routing (for example, when choosing an outbound proxy for a domain or IP rule)

please add sorting of proxies by groups, similar to how it is done when adding proxies to a regular chain.

Right now, all proxies are displayed in a random order. The last item in the list is simply the most recently updated proxy, regardless of its group. For example, if I have 20 groups and I update the 8th group, any changed proxy from that group will appear at the end of the list in these sections.

At the very least, please display the group name for each proxy.

When there are more than a thousand proxies and many of them have identical names, it becomes very difficult to identify the correct one. For example, I have more than 30 proxies named "LTE" — how am I supposed to know which one to choose?

Also, it seems that not all proxies are shown in these lists, especially in the routing section when selecting an outbound proxy for a specific rule.

As an alternative solution, you could allow selecting proxies by their index/ID. For example, we could see the proxy number in its properties and then specify that number in routing. This was possible when configurations were stored in JSON, but now it is no longer available.

At the moment, there are at least 5 proxies that I cannot find in the inbound/outbound group settings or in routing, even though they are definitely present in the main proxy list in the main application window.