When using proxy IP, you often encounter some problems, such as putting the API extraction link into the software, and finding that the proxy IP cannot be extracted, or the proxy IP cannot be used. What is the reason?

1. Failed to obtain proxy IP

1. The proxy IP return format does not match. Different software has different requirements for proxy IP formats. Some require usernames and passwords, some require text format, some require json format, and some even require some non-mainstream formats. If the proxy IP return format does not match, the proxy IP cannot be obtained.

Proxy IP supports 3 return formats, namely text format, json format and xml format. It also supports custom formats, even non-mainstream formats, which can be customized. The three proxy IP return formats are selected when generating API extraction links. The custom format is set in "Set Extraction Format" under instance management.

2. Multiple software extract proxy IPs simultaneously or without intervals. The current proxy IP packages generally have a minimum extraction interval, such as 10 seconds for short-term high-quality proxies and 1 second for exclusive IP pools. The purpose of this is to ensure the stability of the server. However, some software does not have the function of calling API to extract intervals, and can only call API without intervals; some users open multiple software and call API to extract proxy IP at the same time.

Both of these situations will result in the failure to extract proxy IP. What are the solutions? If the software can only extract proxy IP without intervals, then you can establish an IP pool locally, obtain proxy IP at intervals and store it in the local IP pool, and then establish an API interface for the local IP pool, and use the proxy IP without intervals through the local API interface; if multiple software call API to obtain proxy IP at the same time, you can buy an API for each software, or you can establish a local IP pool.

2. No available proxy IP at present

1. Incorrect authorization Generally, high-quality proxy IPs need authorization to be used. If the authorization is incorrect or there is no authorization, the proxy IP cannot be used. The software may prompt "No available proxy IP at present" or other error messages.

There are generally two types of proxy IP authorization modes. One is "terminal IP authorization", which is commonly known as binding IP whitelist, which requires binding the public network IP of the terminal using the proxy; the other is "user name + password" authorization. When using the proxy IP, account and password verification is required. It depends on whether the software supports this authorization mode.

2. Wrong protocol. Some software only supports http or https protocol, but the purchased socks5 proxy IP; some software only supports socks5 protocol, but the purchased https proxy IP; some software supports both protocols, but it is not set up properly when used, such as using http proxy IP, and selecting socks5 protocol on the software.

These situations will lead to the failure of using the proxy IP, and may prompt "No proxy IP is currently available" or other error messages. The above are several reasons why the software cannot use the proxy IP when connecting to the API. I hope it will be helpful to everyone. If you have other questions, you can always consult the website customer service.