ProxyBridge v4.0 Beta - Windows Testers

[Anof-cyber]

Hey everyone! I'm looking for volunteers to help test ProxyBridge v4.0 Beta on Windows before the final release.

If you've been using ProxyBridge or are interested in trying it out, this is a great opportunity to get early access and help shape the final release.

---

What's New in v4.X.X-Beta

New Features

• Multi-Proxy Support - Route different processes through different proxies simultaneously
• IPv6 Support - Full IPv6 traffic interception and proxying
• Multiple Proxy Configs - Add, edit, and delete multiple SOCKS5/HTTP proxy configurations
• Proxy Profiles - Save and switch between named proxy configurations
• Domain Name Forwarding - Sends domain names (not raw IPs) to the proxy server for remote DNS resolution (issue [Feature]: Send domain to proxy #138)
• Log Filters - Filter the connection log by process, IP, port, protocol, and action using Include/Exclude rules with wildcard support
• Toolbar Quick Actions - Proxy Rule and Config in the main menu
• Auto-Clear Connection Logs - Optional: automatically trim connection logs when they exceed the limit with

Bug Fixes

• Fixed relay sockets bound to loopback only - now binds to INADDR_ANY so real traffic reaches the relay (TCP + UDP)
• Fixed SOCKS5 UDP ASSOCIATE returning 0.0.0.0 - now substitutes the proxy's resolved IP (error 10049 fix)
• Fixed disabled proxy rules not persisting across app restarts - disabled state is now correctly restored on startup and profile switch (issue [Bug]: Can't add processes with ++ in name such as notepad++.exe - Invalid characters in process name error. #157 related)
• Fixed processes with ++ in their name (e.g. notepad++.exe) being rejected by the rule validator (issue [Bug]: Can't add processes with ++ in name such as notepad++.exe - Invalid characters in process name error. #157)
• Fixed log filter Save clearing all existing entries - now re-filters in place, keeping matching lines

Removed

• Removed DNS via Proxy feature and all associated UI, settings, and C-layer code
• Removed Windows CLI Version

Improvements

• Log filter redesigned - each rule now covers all fields (process, IP, port, protocol, action) in a single card with Include/Exclude mode
• Filter evaluation: Exclude rules run first; Include rules use OR logic across rules
• Re-filtering existing log lines on filter save instead of wiping the log

---

How to Help

The v4.0 beta installer is attached to this post - go ahead and download it and give it a try!
ProxyBridge-Setup-4.0.6-Beta.zip

If you run into anything, please comment below with:

• Your Windows version (10/11)
• A description of the issue or feedback

Any feedback on bugs, unexpected behaviour, or UX issues is appreciated. Thanks in advance to everyone who participates! 🙌

[steveepreston]

What a Great Upgrade!

Please consider adding these important UX improvements:

• [Feature]: Label/Remark for each Rule
• [Feature]: Label/Remark for each Proxy Server
• [Feature]: Rules/ProxyServers buttons in Main App Screen (instead of in Menu)

[steveepreston]

• [Bug]: Pressing Esc Keyboard Button does not closes the popups

[Anof-cyber]

#102 #152 is added in 4.0.1 beta

[gemini44sam-cloud]

[Bug]: Log Filter - The wildcard "*" isn't working.

• Windows 11 23H2 Pro (Chinese)

• ProxyBridge v4.0 Beta

The wildcard "*" isn't working. Not sure if it's because of Unicode encoding.

[Anof-cyber]

This is fixed in the 4.0.1 beta version

[eldoradoel]

When using mstsc via a proxy to access 192.168.8.103, the SOCKS proxy logs show an "inbound connection to 0.1.0.1:1001". Version 3.2.0 works correctly.

[Anof-cyber]

Whats the error here?

[eldoradoel]

[eldoradoel]

[Anof-cyber]

This is fixed in the new beta 4.0.2

[eldoradoel]

Issue resolved, everything is working properly. Thanks.

[1327-cmd]

When using ProxyBridge(4.0.2) to proxy an SSH connection that establishes a SOCKS5 proxy, the connection disconnects after a short period. However, when using Proxifier(4.14) with the exact same setup, the connection remains stable and continuous without any drops.

[steveepreston]

@Anof-cyber
thanks you for explain, very sad now. 😔

[1327-cmd]

Thank you! I appreciate you taking the time to verify it.

[Anof-cyber]

ProxyBridge-Setup-4.0.5-beta.zip

@1327-cmd can you try with the above version? I have updated the early TCP session timeout for idle sessions

[1327-cmd]

Ok,please check the link,it displays "Not Found".

[Anof-cyber]

@1327-cmd can you try new 4.0.6-beta ProxyBridge-Setup-4.0.6-Beta.zip

[someperson]

I'm using 4.0.2 on Windows Server 2022 and am having trouble with UDP traffic. My SOCKS5 proxy is mihomo, with UDP enabled, and my rules in ProxyBridge are set up for TCP and UDP. I've also confirmed that using mihomo directly works fine.

I made some python scripts to test it definitively. This script fails with a timeout error when a rule is set up in ProxyBridge to route UDP traffic for python to mihomo:

import socket

s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
s.settimeout(5)
s.sendto(b"udp-test", ("65.21.106.102", 8080))
print(s.recv(1024))

On the other hand, this script, which does the exact same thing except going directly through mihomo's SOCKS5 server, works fine with no ProxyBridge rules in the mix:

import socket
import socks

s = socks.socksocket(socket.AF_INET, socket.SOCK_DGRAM)
s.set_proxy(socks.SOCKS5, "127.0.0.1", 7890)
s.settimeout(5)
s.sendto(b"udp-test", ("65.21.106.102", 8080))
print(s.recv(1024))

It isn't just my script that is failing; the problem is also reproducible with ncat (echo "udp-test" | ncat -u -w 2 65.21.106.102 8080) or dig (dig '@8.8.8.8' google.com). I just made the scripts to confirm that UDP is working on the mihomo side and that the problem definitely seems to be on the ProxyBridge side.

Do you have any suggestions for anything I can try? Thank you!

[Anof-cyber]

can you try with a different proxy server, as I validated amd its workinh fine. Also, check if your system is not blocking the tcp and udp relay server

[someperson]

I was able to reproduce the issue as well using gost. Running gost -L socks5://:7890?udp=true starts it on port 7890 with UDP support enabled. UDP connections directly through gost (e.g. my python script) work fine. But ProxyBridge doesn't seem to be forwarding UDP to it correctly.

For good measure, I also tried completely disabling Windows Firewall. This did not help.

[Anof-cyber]

I am working on this. I fixed one bug related to UDP ICMP in this release, for some reason it broke raw udp.

[Anof-cyber]

UDP issue are fixed in v4.0.6-beta ProxyBridge-Setup-4.0.6-Beta.zip

[someperson]

Thank you so much! I can confirm that 4.0.6 fixed the problem! That makes ProxyBridge seemingly the only program of its kind available with both UDP and IPv6 support :)

[steveepreston]

Good News.
It seems v4 Officially published: https://github.com/InterceptSuite/ProxyBridge/releases/tag/v4.0.0
But just a confusing version. why it's 4.0.0 not the 4.0.6 or 4.0.7?

[Anof-cyber]

4.0.x were beta version

First beta started with 4.0.0-beta. which had different issues and each fix came with new beta version 4.0.1-beta, 4.0.2-beta and soo on.

Final stable release is with new major version 4.0.0

[steveepreston]

Good. Thanks