407 Error Code: Proxy Authentication Problem Solved

What the hell is wrong with this stupid error code 407?

Recently, many brothers in the use of proxy IP, suddenly popped up a 407 error code, anxious to scratch their heads. To put it bluntly, this is the proxy server is shouting: "Brother dei, you pour out the ID card ah!" Just like you go to the Internet cafe without an ID card, the network administrator will not let you open the same.

Here's the kicker: 407 errorNinety-nine percent of the time, it's because the authentication information isn't correct.. Either the account password was entered incorrectly, or the authentication parameters were not configured at all. Some proxies require authentication information to be in a specific format, such as prefixed or encrypted with base64.

Hands-on guide to filling out your certification information

Take our ipipgo's proxy service as an example, the correct configuration posture is like this:

 Python Example
import requests

proxies = {
    "http": "http://用户名:密码@gateway.ipipgo.com:9021",
    "https": "http://用户名:密码@gateway.ipipgo.com:9021"
}

response = requests.get("https://example.com", proxies=proxies)

Look at this address structure.The username and password must be in front of the proxy addressThe code is separated by a colon in the middle of the code. Some newbies directly write the account password in the code, the result of the address is written as http://gateway.ipipgo.com:9021?user=xxx, this kind of iron will report 407 error.

5 common rollover sites

According to our customer service statistics, these pits should not be stepped on:

Special Scenario Survival Guide

Don't panic in these situations:

Scene 1:Automated testing with selenium Times 407
Add proxy configuration in ChromeOptions:

options.add_argument("--proxy-server=http://用户名:密码@gateway.ipipgo.com:9021")

Scene 2:The mobile app can't connect to the agent
Check if you are using socks5 protocol, our ipipgo mobile terminal is recommended to use http(s) protocol is more stable.

QA First Aid Kit

Q: I won't report 407 if I use a free proxy, right?
A: I'd like to think so! Free proxies are more prone to authentication problems instead. ipipgo's paid proxies all come with automatic authentication, which saves you a lot of trouble.

Q: How to test whether the agent is configured successfully?
A: Test with the curl command first:
curl -x http://用户名:密码@gateway.ipipgo.com:9021 https://api.ipipgo.com/check
Successful if IP information is returned

Q: What if I need a large number of proxies for enterprise-level crawlers?
A: Directly to ipipgo customer service to open theDynamic Concurrent AuthorizationIt supports launching thousands of requests at the same time without dropping the line.

The Ultimate Solution

If you try everything and still can't get it to work, just use ipipgo.Intelligent Agent SDKThis thing automatically handles authentication, retries, and load balancing. This thing handles authentication, retries, and load balancing automatically, with only three lines of initialization in the code:

from ipipgo_sdk import ProxyClient
client = ProxyClient(api_key="your key")
response = client.get("https://目标网站")

The most flirty thing about this SDK is that it will automatically renew the IP, and when it encounters a 407 error, it will change the IP and retry by itself, so you don't have to worry about it at all.