Windows Guide
Troubleshooting and limits (Windows)
Fix common ProxyBridge problems on Windows: traffic not going through the proxy, apps that stop connecting, service and permission messages, UDP, QUIC and HTTP/3, localhost, IPv6, plus the limits to know about.
Troubleshooting and limits
Start here: is the connection matching a rule?
Open the Connections tab, start the application, and find its lines (type its name in the search box and press Enter).
| What you see | Meaning | Go to |
|---|---|---|
via Proxy SOCKS5://... or via Proxy HTTP://... |
The rule matched and the connection was sent to the proxy | The application cannot connect after adding a rule |
via Direct |
No rule matched (or the rule says Direct) | Traffic is not going through the proxy |
via Blocked |
A Block rule dropped it | Check your Block rules in Proxy > Proxy Rules... |
| No line at all for the program | Traffic logging is off, a log filter hides it, or the program started no new connection | Nothing is listed |
The Activity Log tab shows messages from the engine, such as a proxy that could not be reached. The Live Connections tab shows what is open through a proxy right now.
Traffic is not going through the proxy
Check these in order:
- Is ProxyBridge enabled? If the window title says (PAUSED), tick Proxy > Enable ProxyBridge.
- Is the rule switched on? The On check box in the rules list must be ticked.
- Is the program name right? The rule matches the exact executable name. Click Running... in the rule editor and pick the program from the list. Many programs are several executables (a launcher, a helper, a web-view process): add all of them, separated by
;. - Did the program start before the rule? Connections that were already open keep their old route. Restart the program.
- Protocol: a rule for TCP does not touch UDP traffic, and the other way round. Use Both to be sure.
- Hosts and ports: with a Target Hosts or Target Ports filter, only matching destinations are routed. Try
*for both first. - Rule order: an earlier rule that matches (for example a Direct rule) wins over a later one. See Rule order.
- Domain rules and encrypted DNS: domain names only work with unencrypted DNS. If the browser uses Secure DNS / DNS over HTTPS, turn it off, or use IP addresses in Target Hosts. See Domain names need plain DNS.
- The program talks only to localhost: connections to
127.0.0.1/::1go direct unless the rule has Also proxy localhost traffic ticked. See Localhost traffic. - The program uses UDP or QUIC: see UDP, QUIC and HTTP/3.
The application cannot connect after adding a rule
The rule matched, but the proxy did not accept the connection.
- Open Proxy > Proxy Settings..., select the proxy and click Proxy Test. Read the result:
- Test 1 failed: the proxy is not running, or the address or port is wrong, or a firewall is in the way.
- Test 2 failed: the proxy refused to open a tunnel. With a login set, check the username and password.
- Test 4 failed (SOCKS5 UDP ASSOCIATE): the proxy does not support UDP.
- Look in the Activity Log for a line about the proxy.
- Make sure the proxy is running before the application connects, and that it listens on the address you entered (a proxy bound to
127.0.0.1cannot be reached from another PC, and the other way round). - If the proxy is a security tool that decrypts HTTPS, the application may fail with a certificate error. Install the tool's CA certificate. Programs that pin their certificates will always reject an intercepting proxy.
- To check whether the proxy is the cause, untick Proxy > Enable ProxyBridge. If the application works again, the problem is between ProxyBridge and the proxy.
If you added a Proxy rule while no proxy is configured, connections go out directly.
Nothing is listed
- Enable Traffic Logging is off: tick Settings > Enable Traffic Logging.
- A Log Filter hides it: check Proxy > Log Filters....
- The log shows one line per destination by default. A repeat connection to the same place is not listed again. Tick Settings > Log Every Connection.
- Auto Clear Logs wipes a log when it grows past 500 lines. Untick it to keep more.
- Live Connections shows only connections going through a proxy, not Direct or Blocked ones.
Messages and what to do
| Message | Cause and fix |
|---|---|
| This account is not allowed to use the ProxyBridge service... | Your Windows account is not in the ProxyBridge Users group. An administrator runs net localgroup "ProxyBridge Users" <name> /add, then you sign out and in. See Install on Windows |
| Another ProxyBridge window (possibly in a different user session) is already connected to the ProxyBridge service | Only one app window can use the service at a time. Close the other one, including one in another user's session |
| ProxyBridge is already running (GUI or CLI) | Close the other instance, then start again |
| The installed ProxyBridge service is a different version than this program | Run the installer again so the app and the service match |
| Failed to start ProxyBridge service. Run as Administrator and ensure WinDivert64.sys is present. | The engine could not start. See The engine does not start |
| Could not load ProxyBridgeCore.dll | Stand-alone mode only: keep ProxyBridgeCore.dll in the same folder as ProxyBridge.exe, or install normally |
| Administrator privileges required. (CLI) | Start the terminal with Run as administrator |
The engine does not start
- Open Services (
services.msc) and check that ProxyBridge Service exists and is running. If it is stopped, start it (right-click, Start). - Check that
WinDivert64.sysandWinDivert.dllare inC:\Program Files\ProxyBridge. Security software sometimes quarantines a packet-capture driver. Restore the file, add an exclusion for the ProxyBridge folder, and run the installer again. - Other programs that use their own packet-capture or filtering driver (some VPN clients, firewalls, and tools that use WinDivert) can conflict. Close them and try again.
- Run the installer again. It repairs the service, the driver and the permissions.
Command line, from an administrator terminal:
sc query ProxyBridgeSvc # shows RUNNING or STOPPED
sc stop ProxyBridgeSvc # stop it
sc start ProxyBridgeSvc # start it
VPNs, Public networks and the firewall
Redirected connections reach ProxyBridge's local relay as inbound traffic. On a network that Windows classifies as Public (VPN adapters such as WireGuard and OpenVPN usually are), the Windows Firewall could drop them. To prevent this, ProxyBridge adds an inbound allow rule named ProxyBridge relay ... for its own program on all network profiles. The relay also checks where each connection comes from, so this does not open it to other computers.
If proxying stops working only on a VPN or Public network, check that this rule exists (Windows Defender Firewall with Advanced Security > Inbound Rules), and that no other firewall product removes it. The Activity Log says whether the rule was added.
UDP, QUIC and HTTP/3
- HTTP proxy + UDP = direct. HTTP proxies cannot carry UDP. If a rule's Action is an HTTP proxy and the Protocol is UDP or Both, the UDP traffic goes direct, not through the proxy. TCP follows the rule normally. Block and Direct UDP rules work with any proxy.
- SOCKS5 is required, but not enough. Whether UDP reaches the destination depends on the proxy supporting UDP ASSOCIATE. Most SOCKS5 proxies, including
ssh -D, do not. A proxy without it silently drops the packets. Run the Proxy Test and look at Test 4. - QUIC and HTTP/3. Most big sites and CDNs now offer HTTP/3, which is QUIC over UDP. Carrying it through a proxy needs a proxy that understands QUIC and HTTP/3, not just raw UDP. For web testing, the easy route is a rule with Protocol TCP only: the browser then falls back to normal HTTPS over TCP.
- Testing UDP and HTTP/3. Nexus Proxy is a SOCKS5 server built to test UDP ASSOCIATE with HTTP/3 and QUIC.
- Only add UDP proxy rules when you have confirmed the proxy supports UDP.
IPv6
ProxyBridge handles IPv6 for both TCP and UDP, with the same rules as IPv4. Target Hosts accepts IPv6 addresses (::1, 2001:db8::1), IPv6 CIDR (2001:db8::/32) and IPv6 ranges. * matches every address, IPv4 and IPv6.
Limits
| Item | Limit |
|---|---|
| Proxy servers | 32 (16 before version 4.3.0) |
| Rules in a profile (app) | 128 (the command line accepts up to 256) |
| Applications field | 8191 characters |
| Target Hosts field | 8191 characters |
| Log Filters | 64 |
| Live Connections | 1200 rows kept; up to 400 live connections are read per update |
| Log lines kept | 4000 per tab (500 with Auto Clear Logs on) |
Other things to know:
- Target Hosts entries that are not valid (for example
10.0.0.0/33,192.168.*with three parts, or1*.2.3.4) match nothing, without an error. IPv4 and IPv6 CIDR, ranges and wildcards are supported; see Target hosts. IPv4 CIDR needs version 4.3.0 or later. - Some traffic is always direct: broadcast, multicast, link-local and DHCP. See Always direct.
- Windows 10 or later, 64-bit only.
- Live Connections, the Running... picker and Log Every Connection need version 4.3.0 or later. See What is new in 4.3.0.
- ProxyBridge changes where traffic goes. It is not a VPN, it does not encrypt traffic and it does not hide your address.
Start clean
- Close ProxyBridge.
- Rename or delete
%APPDATA%\ProxyBridge. This removes all profiles and settings (export any you want to keep first). - Start ProxyBridge again.
To remove and reinstall completely, uninstall ProxyBridge and run the installer again. See Install on Windows.
Asking for help
Open an issue on GitHub and include:
- the ProxyBridge version (Help > About) and your Windows version
- what you expected and what happened
- the relevant lines from the Activity Log and the Connections tab
- the proxy type and what the Proxy Test reported
- your rule (hosts and ports), with any private details removed
