Today to summarize the user in the use of proxy IP in the process of some of the problems often encountered in order to facilitate the better use of proxy IP, to avoid new users and friends to make similar mistakes, can be effective in improving work efficiency.

First, the authorization problem

1, a small number of friends in the call to extract the API prompts 12007 error, this error is because there is no authorization, directly call the API caused. After opening the product, you need to bind the terminal IP authorization or switch the current authorization mode to "user name + password" authorization, and then generate the API extraction link to use.

2, a small number of friends using terminal IP authorization mode, found that all the proxy IP can not be used, after communication and understanding, found that the binding is not using the proxy terminal IP outside the network. remember: terminal IP authorization must be bound to use the proxy terminal IP, can not just bind an IP.

3、Some friends use terminal IP authorization mode, the use of proxy IP in the morning is very normal, to the afternoon suddenly found that all the proxy IP is invalid, after troubleshooting the problem, found that the bound terminal IP changed, need to be rebound in the background of the official website, if the terminal IP changes are more frequent, it is recommended to use the automatic binding terminal IP interface.

4, there are some friends in the process of using the 407 problem, this is the authorization error, terminal IP authorization friends check whether the binding of the correct IP, "username + password" authorization friends check whether the username and password is correct, not the site login username and password, it is recommended that you refer to the help document "how to use How to use HTTP(S) proxy with username and password authentication".

Second, concurrent problems

1, can not access the API: normal access to the API to obtain IP, after a period of time can not access the API, after understanding that the user violently called the API, was misjudged as an attack, was blocked IP. recommended strict adherence to the rules of the shortest extraction interval, can be sustained call API to obtain IP, if you need to multi-threaded call API to obtain IP to use, you can establish a local IP pool, the idea can be referred to How to realize the multi-threaded call API to obtain IP.

2、Access to the site is very slow: a user using a private proxy IP feedback access to a site is very slow or even timeout, after understanding that the user uses the proxy IP to send a request for the concurrency is too large, the maximum total concurrency of more than 4800, it is recommended to control the concurrency, reasonable use.

3, the proxy IP will soon fail: some users use a short-lived high-quality proxy IP to access the site, found that more than 10 seconds or dozens of seconds, the proxy IP can not access the site, through the browser to set up a proxy test will not soon fail. In this case, the concurrency may be too large for a short period of time, the frequency of visits is too high, and it is possible that the target site's anti-crawl strategy is triggered.

Third, API extraction problems

1, the return format is incomplete: many friends view the API to find the return format is very detailed, there is online time, there is expected to be the remaining survival time, there is the IP geographic location, when in the background to generate the extraction link to find that only the return of the IP and the port, where it thought there was a problem. This problem is very good to solve, you can set the extraction format in the background of the product management there, customize or check the parameters you want.

2, no IP under the current filtering conditions: many friends often encounter this problem, some friends are a private agent IP filtering repeated extraction, a short period of time to filter a number of times, the update speed can not keep up, so there will be this tip; some friends are short-lived high-quality proxy IP in the IP generated by the extraction of the link there to specify the IP's geographic location, some of the more remote areas do not have an IP, but also to return to this tip. It is recommended that a handful of private agents within a short period of time do not filter the extraction too quickly, or empty the day filter library and then extract the IP; short-term high-quality proxy IP can be filtered IP more areas, you can refer to the node distribution map (can turn the page oh).

3, akey error: some friends often encounter akey error, they read the API document, take the password to encrypt, often get the wrong akey. akey is derived from the product password through 16-bit MD5 encryption, some friends are taking the site login password to encrypt, some friends are not 16-bit MD5 encryption. In fact, akey can be obtained directly by generating the extraction link there.

Well, today is summarized here, the above is the user in the process of using the proxy IP often encountered some problems, encounter problems do not panic, they first think about where the problem is, and then solve the problem, really can not think of where the problem, then contact customer service to assist in solving.