PowerShell Agent: Windows Configuration Tutorial

Hands-on with a proxy on Windows (hands-off fix: configure proxy)

Today we nag some real, a lot of friends do data collection in the whole work on Windows, often encountered IP was blocked the bad things. At this time we have to rely on proxy IP to save the day, the following I'll teach you how to play around with proxy configuration in PowerShell in the vernacular.

Pay attention to the highlights.The proxies mentioned here are not for you to engage in any dangerous operations, but purely to facilitate local development debugging, such as crawler testing or multi-account management for these serious purposes.

 Temporary proxy setup (disabled by closing the window)
$env:HTTP_PROXY = "http://username:password@gateway.ipipgo.net:9021"
$env:HTTPS_PROXY = "http://username:password@gateway.ipipgo.net:9021"

Configuration of the Great Law of perpetual effect

If you think it's too much trouble to set up every time you open a window, let's just change the registry to get rid of it once and for all. Press Win+R and typeregedit, find this path:

HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionInternet Settings

Right-click in the right margin to create three new string values:

1. Proxy address fill → ProxyServer = gateway.ipipgo.net:9021
2. exception address fill → ProxyOverride = local address;.internal
3. Enable switch → ProxyEnable = 1

tipThe proxy server of ipipgo comes with authentication, remember to write the account password in the address, the format is user:pass@proxy address.

Command Line Proprietary Agent Settings

Sometimes if you just want PowerShell to go proxy without affecting other software, you can try this tawdry operation:

netsh winhttp set proxy gateway.ipipgo.net:9021 bypass-list=".ipipgo.com"

Where is this command? It only controls the flow of the command line tool, the browser should be used how to use it, especially suitable for the need to switch between multiple environments of the old driver.

Real-world common rollover scene QA

Q: What should I do if I can't connect to the agent?
A: First check the three-piece suite: 1. whether the IP address is expired 2. whether the port is written wrong 3. account password is not correct. Recommended to use ipipgo's dynamic proxy, their IP validity up to 24 hours, more than the market common 12 hours conscience.

Q: What should I do if the speed suddenly slows down?
A: It is likely that the current IP is being targeted. In the background of ipipgo there is a "second cut IP" function, click on it can immediately change the export IP, faster than a drink of water.

Q: How do I mess up if I have to change my IP frequently?
A: Directly use ipipgo's rotating proxy package, their API interface supports automatic IP change per request, add this in the code to realize:

$proxyList = @(
    "user1:pass1@gateway.ipipgo.net:9021",
    "user2:pass2@gateway.ipipgo.net:9022"
)
$randomProxy = $proxyList | Get-Random
$env:HTTP_PROXY = $randomProxy

Why do you recommend ipipgo?

After using so many proxy services, the last long-term use of ipipgo is not without reason. First of all, his family IP pool is large enough, the country has more than 200 city nodes, to do geographically oriented collection is particularly powerful. Secondly, the stability of the actual test of 48 hours of continuous hang-ups did not fall off the line, which is too important to the need for long-term operation of the task.

And they recently came out with aIntelligent Routing功能，能自动选择最低的节点。比如你在广州，默认就会分配深圳或东莞的服务器，这个细节确实能提升效率。

Finally, a hidden benefit: new users get 1G of free traffic for signing up, which is enough for testing. If you're just starting out with an agent, you can absolutely use the free traffic to practice first, and then go on to the paid packages when the business runs smoothly, this strategy is very friendly to newbies.

(Sudden thought) Right! Remember to set a timeout in the code for their service, suggesting that 30 seconds or so is more appropriate. Some brothers did not set the timeout, the result of the program stuck there, thought it was a proxy problem, in fact, it is a low-level error...