> 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).
# 错误
使用我们全面的错误代码参考来排查 DataImpulse 代理错误。了解每个错误的含义，并快速解决连接问题。
使用 HTTP 代理时，在使用服务后，错误会显示在代理服务器的响应中。使用 SOCKS5 时，在创建连接和认证时，错误会通过状态码显示。所有错误都可以在账户仪表板上查看。
**HTTP 错误列表：**
`400 错误请求` - 向代理服务器发出的 CONNECT 请求创建不正确。\
`403 PORT_BLOCKED` - 连接尝试发往被封锁的端口。\
`403 SITE_PERMANENTLY_BLOCKED` - 指定网站的访问已被永久封锁。\
`403 HOST_BLOCKED` - 指定网站的访问已由用户在当前套餐设置中封锁。\
`407 NO_USER` - 用户的套餐不存在。\
`407 TRAFFIC_EXHAUSTED` - 已超出套餐的流量限制。\
`407 THREADS_EXHAUSTED` - 已超出套餐的线程限制。\
`USER_RATE_LIMIT_EXCEEDED` - 已达到为套餐周期设置的流量限制。参见 [流量限制](/dataimpulse-documentation-zh-cn/liu-liang-xian-zhi.md).\
`407 PORT_NOT_ALLOWED` - 当前套餐设置不允许使用粘性会话端口。\
`407 USER_BLOCKED` - 用户当前套餐已被封锁。\
`500 INTERNAL_SERVER_ERROR` - 服务器遇到意外情况，无法完成请求。\
`502 NO_HOST_CONNECTION` - 与 CONNECT 请求中指定的主机没有连接。\
`503 NO_RAY` - 根据请求中指定的目标参数，没有可用的代理。\
**SOCKS5 错误列表：**
对于以下错误： `NO_USER`, `REQUESTS_EXHAUSTED`, `TRAFFIC_EXHAUSTED`, `THREADS_EXHAUSTED` 当尝试连接到代理服务器时，将返回 Denied 状态的认证失败响应。\
\
对于以下错误： `PORT_BLOCKED`, `NO_RAY`, `NO_HOST_CONNECTION` 认证将通过，随后如果尝试进行 UDP 连接，代理连接将被重置，连接将被断开。
`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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.dataimpulse.com/dataimpulse-documentation-zh-cn/cuo-wu.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.