[Feature]: Support Proxy Chaining (Proxy Chain / Multi-hop Routing)

[yaoxinghuo]

Platform

All platforms

ProxyBridge Version

4.0.0

OS and Version

MacOS Sequoia 15.7.7

Documentation

• I have read the Windows documentation
• I have read the macOS documentation
• I have read the Linux documentation

Code Review

• I have gone through the code page

Describe the Feature

Description of the Feature Request

First of all, thank you for developing ProxyBridge! It's an amazing, lightweight, and high-performance open-source alternative to Proxifier.

Currently, ProxyBridge allows routing process traffic through a single SOCKS5 or HTTP proxy server. However, it lacks support for Proxy Chains (Proxy Chaining), a feature widely used in Proxifier that allows users to chain multiple proxy servers together (e.g., App Traffic -> Proxy A (SOCKS5) -> Proxy B (HTTP) -> Target Destination).

Adding Proxy Chain support would make ProxyBridge a truly complete power-user alternative to commercial tools like Proxifier, especially for complex network environments, advanced debugging, or privacy-focused multi-hop setups.

Expected Behavior / UI Proposal

It would be awesome if we could:

1. Define a Proxy Chain: Under proxy settings, users can create a "Chain" and add multiple configured proxy servers to it in a specific sequence.
2. Support Mixed Protocols: The chain should ideally allow mixing different proxy types (e.g., SOCKS5 as the first hop, HTTP as the second).
3. Use Chains in Rules: In the "Proxy Rules" section, users should be able to select either a single proxy server OR a pre-defined proxy chain as the action/target for specific processes or IPs.

Alternatives Considered

Currently, to achieve multi-hop proxying with ProxyBridge, users have to chain proxies upstream manually using other third-party CLI tools (like upstream configurations in local core clients) before pointing ProxyBridge to it. Built-in support would vastly simplify the UX.

Platform

• Windows
• macOS
• Linux

Additional Context

No response

[Anof-cyber]

This won't be worked on at least for now, I don't have any such use case and not in current project goal.

Also app work with UDP as well which makes it difficult to add this and any more hops and packet like http3 voip will be dropped.

By default if you look at browser config in both chromium based ane Firefox etc. http3, web rtc timeout is very low by default. Slight milliseconds of delay and packet is dropped by browser.

[yaoxinghuo]

Thank you for the detailed explanation!

That makes total sense—I hadn't fully considered the severe latency/timeout impacts on UDP and modern web protocols like HTTP/3 and WebRTC when multi-hopping. Your point about chromium/Firefox strict timeouts is very insightful.

I'll look into handling the chaining upstream on the local core side instead. Thanks again for your time and for maintaining this awesome project!

Closing the issue now. 👍

[Anof-cyber]

Keeping it open. Post next release i have figure out what the solution and easiest way to implement it.