What do HTTP proxy and SOCKS5 mean? When you turn off the accelerator, the webpage spins everywhere, but WeChat works fine—90% of the time it's because the system proxy hasn't been restored

during the National Day holiday, my niece brought her laptop back to find me, saying her computer was "infected": the browser kept spinning in circles, not a single webpage would appear, but WeChat video chat lasted half an hour without any lag. She used a game accelerator in her college dorm to play on foreign servers. The night before the holiday, she turned off the accelerator and packed her luggage, but the next day her computer was just like that. I dragged the error page from the browser to the bottom and saw a line of small text—"Unable to connect to proxy server." It's not a virus; it's just that when the accelerator exits, the system proxy switch doesn't restore it.
spend two minutes first distinguishing between proxies and VPNs
the concept of agency sounds mysterious; to put it bluntly, it's just a errand runner. Normally, your browser directly finds the website to get the page, and no one passes through in between. After opening a proxy, the browser first sends the request to the proxy, which runs the website for you and then returns the result. What the website sees is the agent knocking on the door, not the person themselves.
I only fully understood the difference from VPNs after trying my hand at it. A VPN is like building a tunnel with a virtual network card, and all traffic is fed into the tunnel the computer without dissipation—I previously connected to the company VPN during a business trip, but after it was disconnected, a line of default routes remained in the routing table, causing the network to crash halfway. That time, it was the extra line in the routing table the problem. Proxies are different; they are recognized individually by application: obedient apps like browsers read system proxy settings and follow them; WeChat and most games ignore this setting and just connect directly to the door. This explains the symptoms of my niece's computer—the browser waits for the errand runner to open the door, but the errand runner leaves work early; WeChat goes out by itself, living just fine.
want all the devices in your home to go through a tunnel is a different matter. I've previously written about using router and VPN to remotely home, which has nothing to do with system proxy.
HTTP agent and SOCKS5 differ in whether they check packages or not
usually hear about two main types of agents, each with different errands and methods.
HTTP agents are veterans, born to run errands for web pages. It can read the header of HTTP requests and can do other tasks at the same time: set up a company that caches pages repeatedly visited by all staff here, and caches them directly when someone visits; You can also filter by the address in the head. In the era when HTTPS was everywhere, it used a method called CONNECT to punch a hole first, then forwarded the encrypted byte as is—it couldn't understand what was being passed through the hole. The details of this hole mechanism were discussed in articles about http and https.
SOCKS5 is another approach: they don't even open the package, just look at the "delivery destination" on the shipping label. Because it is not particular about content, it handles web pages, emails, games, and any TCP/UDP tasks, so accelerators and various clients love using it. TCP and UDP: Which controls retransmission and which controls speed? previous article detailed in detail.
| comparison item | HTTP proxy | SOCKS5 proxy |
| whether you read the content | understand the webpage request header | don't look, just forward |
| can do what you can | webpages, caching and filtering | any protocol, game email is fine |
| common port | 8080、3128 | 1080 |
port is a custom, not a rule. The 1080 is a long-standing tradition in SOCKS5. Nowadays, many clients default to high-level ports like the 7890, where the port number itself doesn't depend on the protocol. The port is clearly explained in that article You see in the tutorial that you have to enter 127.0.0.1:7890, which means "there is a proxy client on port 7890 on this machine with the door open." 127.0.0.1 always refers to your own computer.
is secretly altering your system proxy
The
Windows proxy switch is hidden on the Configure → Network and Internet → Proxy page, which has three boxes: "Automatically detect settings," "Use setup scripts," and "Manually set proxies." On a normal home computer, all three slots should be closed. However, the following types of software will turn on the switch for you when installed and running:
Game Accelerator is the top contender; my niece's machine got caught in this way; The second type is packet capture and debugging tools, which I have failed myself — there was a period when I tried to adjust smart home interfaces, had the packet capture tool running system proxy, closed the lid at night, and the next day the browser was completely disabled, and only remembered after half an hour of fiddling; The third type is the company intranet client, which connects to company resources at work, and most computers from handovers remain after resignation; Some ad-removal browser plugins take the path of "using setup scripts," scientifically called PAC, which essentially gives the browser a list of "which addresses use proxies."
pitfalls are that exiting doesn't equal resetting the . Most apps will obediently turn the switch back on when exiting normally, but once it crashes, forcibly exits, or directly unplugged the power, the switch freezes on. The house number was still hanging, the runner was gone, and the browser kept crashing headfirst toward the dead door.
the webpage is fully circular, WeChat is fine; first read the small text on the wrong page
this symptom is the easiest to guess. Instead of blaming routers, optical modems, and DNS one by one, it's better to drag the error page to the bottom of the browser error page, where the gray text directly reveals the root of the problem. I have summarized a triage form myself:
| error page | root cause | where to check |
| unable to connect to proxy server / ERR_PROXY_CONNECTION_FAILED | Proxy residual | main thread of this article. Turning off the switch |
| can't find the server IP address / DNS_PROBE For the | DNS at the beginning | see the DNS configuration article, on the optical modem side another article |
| half the app is down, half is normal, and restarting doesn't help | VPN the route remains | route print finds the extra line |
note: "WeChat is normal" does not mean the proxy retains a unique signature; when DNS is broken, WeChat is still normal—it has its own server address memory. So don't rely on guessing, rely on reading: if an error contains the word "proxy," it's a proxy matter; if it includes "DNS," it's a parsing matter. Not a single word will lie to you. Here's another piece of evidence: if the phone and WiFi are all normal, it means the issue is locked in the computer's settings and has nothing to do with the router.
remnants of the Qing Dynasty, follow these three layers from top to bottom
the first layer is the settings interface. In Windows 11: Set up → Network and Internet → Proxy, turn off 'Use Proxy Server,' and also turn off 'Auto Detection Settings'—this switch is on, so every time the computer switches to a network, it broadcasts asking 'Is there a proxy script on this network?' If no one answers, you connect directly, which is wasted and leaves it in a home environment doing nothing. After making changes you must restart your browser. Chrome and similar browsers read the system proxy once at startup, so if you turn off the switch, it won't notice. For plugins like SwitchyOmega, you also need to check whether the plugin has switched back to 'Direct Connection'—it has an extra layer of its own switch than the system settings.
second layer is the system services layer, which manages proxy services like Windows updates, which is different from the settings interface. Open the terminal as administrator, type netsh winhttp show proxy to check. If a proxy appears, then type netsh winhttp reset proxy reset to direct connection. My niece's machine was fully healed after the first layer was closed, and the second layer was prepared for difficult cases.
third layer is the environment variable. Command-line tools (git, curl, pip, etc.) don't look at the settings interface, but look at the environment variable http_proxy. In the terminal, tap echo %http_proxy% check, and if there are values, set http_proxy= clear them. Once, I tried to pull code from the command line and couldn't connect no matter what. The browser worked fine, but then I found out that a tutorial had asked me to export the proxy once, and it was left there.
When will
family really need it
first mention a common misstep: there's a 'proxy' option in the mobile WiFi details, and it always stays at 'None.' Home routers don't use proxies; if you fill in anything, all your phone's data will knock on a door that doesn't exist.
really want all devices in the home to use proxies—remove ads, let certain types of traffic go out all at once—the legitimate approach is to attach an old router next to it as a bypass router, just point the gateway to it, and don't touch any browser settings. I the whole process about using N1 as a bypass router. Compared to manually filling out proxies on each device, the advantage of bypass routing is that you can disconnect and leave anytime without leaving any residue.
| symptom | what should you do first |
| the browser says 'Unable to connect to proxy server' | turn off two switches in settings and restart the browser |
| switch turned off but still not working | netsh Winhttp reset proxy |
| command line cannot connect, browser | check normally http_proxy Environment variable |
| want your whole family to use the proxy | bypass route, don't fill in the |
end the order: read the error page to confirm it's a proxy → Turn off two switches in the settings interface → Restart the browser → still can't check netsh Winhttp → Command line tools check environment variables separately → always leave the phone with "None." The complete approach to troubleshooting is the same as the five checkpoints from network cable to web pages: first identify which layer the problem is, then take action. My niece's phone takes three minutes to turn off a switch and restart a browser—provided you know this switch exists.
