The system proxy mainly affects apps that follow operating-system proxy settings. Some games, command-line tools, store apps, and standalone proxy software may ignore it. Set HTTP_PROXY or HTTPS_PROXY for command-line tools, enter mixed-port in apps that support a manual proxy, and consider TUN for other apps.
Does the app use the system proxy, a dedicated port, or neither?
After enabling the system proxy, verify the local port in a browser, then check whether the target app appears in the connection list. If it does not, the app is not reading the system proxy.
- Does the browser use its own proxy extension?
- Does the command-line tool require HTTP_PROXY or HTTPS_PROXY?
- Does the app support only SOCKS or only an HTTP proxy?
- Does the client's local port match the app configuration?
Add a capture method for command-line tools, games, and specialized apps
- Open a test page in a browser to confirm that the system proxy works
- For command-line tools, explicitly set proxy environment variables or the tool's own proxy options
- For apps that ignore the system proxy, use TUN or enter the local proxy port in the app
- Check whether another program occupies local HTTP, SOCKS, or mixed-port(See Inbound configuration)
The system proxy and TUN are different capture methods(See TUN device guide)
A port conflict can make the proxy switch look enabled even though it does not work
Enterprise devices may have additional proxy policies or security-software restrictions