> For the complete documentation index, see [llms.txt](https://docs.dataimpulse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataimpulse.com/dataimpulse-documentation-zh-cn/cuo-wu.md).

# 错误

使用 HTTP 代理时，错误会在使用服务后显示在代理服务器的响应中。使用 SOCKS5 时，错误会在创建连接和验证时通过状态码显示。所有错误均可在账户仪表板上查看。

**HTTP 错误列表：**

`400 Bad Request` - 发送到代理服务器的 CONNECT 请求创建不正确。\
`403 PORT_BLOCKED` - 连接尝试被发向被阻止的端口。\
`403 SITE_PERMANENTLY_BLOCKED` - 对指定站点的访问已被永久阻止。\
`403 HOST_BLOCKED` - 在当前计划设置中，用户已阻止对指定站点的访问。\
`407 NO_USER` - 用户的计划不存在。\
`407 TRAFFIC_EXHAUSTED` - 超出了计划的流量限制。\
`407 THREADS_EXHAUSTED` - 超出了计划的线程限制。\
`407 PORT_NOT_ALLOWED` - 所使用的 sticky sessions 端口在当前计划设置中不被允许。\
`407 USER_BLOCKED` - 用户的当前计划已被阻止。\
`500 INTERNAL_SERVER_ERROR` - 服务器遇到意外情况，导致无法完成请求。\
`502 NO_HOST_CONNECTION` - 与 CONNECT 请求中指定的主机没有连接。\
`503 NO_RAY` - 根据请求中指定的定位参数，没有可用的代理。\ <br>

**SOCKS5 错误列表：**

对于如下错误， `NO_USER`, `REQUESTS_EXHAUSTED`, `TRAFFIC_EXHAUSTED`, `THREADS_EXHAUSTED` 在尝试连接到代理服务器时，会返回带有 Denied 状态的不成功验证响应\
\
对于如下错误， `PORT_BLOCKED`, `NO_RAY`, `NO_HOST_CONNECTION` 将会通过验证，之后如果尝试建立 UDP 连接，代理连接将被重置，连接将被断开。&#x20;

`UDP_BIND_FAILED` – 无法绑定本地 UDP 端口，导致无法建立 UDP 连接。此错误类似于 `502 NO_HOST_CONNECTION`，但发生在使用 UDP 协议时。

有关这些错误的更多详细信息可在我们的博客中找到： [代理错误：类型、原因与解决方案](https://dataimpulse.com/blog/proxy-errors-types-causes-and-solutions/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dataimpulse.com/dataimpulse-documentation-zh-cn/cuo-wu.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.