[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-strapi-article:zh:replicate-api-proxy-timeout-model-startup-retries":3,"blog-article:\u002Fblog\u002Freplicate-api-proxy-timeout-model-startup-retries":519,"blog-related:\u002Fblog\u002Freplicate-api-proxy-timeout-model-startup-retries":520,"blog-translations:\u002Fblog\u002Freplicate-api-proxy-timeout-model-startup-retries":521},{"available":4,"article":5,"relatedArticles":134,"translations":437},true,{"source":6,"id":7,"documentId":8,"translationKey":8,"locale":9,"slug":10,"path":11,"_path":11,"title":12,"description":13,"excerpt":13,"image":14,"publishedAt":15,"updatedAt":16,"author":17,"tags":18,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":23,"bodyHtml":133},"strapi",3374,"epucn428k2v6dxeycubzmw47","zh","replicate-api-proxy-timeout-model-startup-retries","\u002Fblog\u002Freplicate-api-proxy-timeout-model-startup-retries","Replicate API 代理请求超时怎么排查：模型启动、连接复用与重试","排查 Replicate API 请求超时时，先分开连接建立、模型冷启动、首字节和推理等待，再结合任务状态、连接复用与幂等性决定是否安全重试。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_Replicate_API_cover_637444c0be.webp","2026-10-15T08:28:58.710Z","2026-10-15T08:28:58.696Z","Global Proxies Team",[],false,0,2,"blocks",[24,30,35,39,43,47,52,56,60,64,68,72,76,80,84,88,93,97,101,105,109,113,117,121,125,129],{"type":25,"children":26},"paragraph",[27],{"text":28,"type":29},"Replicate API 的连接超时、模型冷启动、首字节等待和推理耗时不是同一问题。先记录各阶段时间与任务状态，再决定是否安全重试。","text",{"type":31,"level":21,"children":32},"heading",[33],{"text":34,"type":29},"如何区分连接、首字节和推理等待",{"type":25,"children":36},[37],{"text":38,"type":29},"记录 DNS、TCP、TLS、首字节、总耗时、请求 ID 和任务 ID。连接阶段失败先查网络与代理；连接成功但首字节慢，应查排队或模型启动状态；推理中断则结合响应进度和服务端任务状态判断。",{"type":25,"children":40},[41],{"text":42,"type":29},"连接层错误可参考[代理 timeout、connection refused 和 TLS 证书错误怎么排查](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-timeout-connection-refused-tls-error)。",{"type":25,"children":44},[45],{"text":46,"type":29},"下面把各阶段耗时对应到可观察字段和处理动作。",{"type":48,"children":49},"code",[50],{"text":51,"type":29},"| 阶段 | 观察字段 | 可能原因 | 下一步 |\n| --- | --- | --- | --- |\n| DNS\u002FTCP\u002FTLS | 解析、建连、握手耗时 | 网络、认证、证书 | 查连接层 |\n| 首字节前 | 等待时间、任务状态 | 冷启动或排队 | 查服务端状态 |\n| 推理中 | 响应进度、任务状态 | 模型仍在执行 | 查询任务进度 |\n| 客户端超时 | 请求 ID、任务 ID | 服务端可能仍运行 | 查询后再决定重试 |",{"type":25,"children":53},[54],{"text":55,"type":29},"先处理时间线中最早异常的阶段；创建类请求在确认任务状态前不要重复提交。",{"type":31,"level":21,"children":57},[58],{"text":59,"type":29},"客户端超时后如何查询任务状态",{"type":25,"children":61},[62],{"text":63,"type":29},"客户端超时不代表服务端未收到请求。创建任务或可能产生费用的请求，先查询任务状态，确认未执行后再决定是否重试；对幂等读取才设置有限重试。连接复用问题可通过新建连接与复用连接对照，具体任务查询字段和 API 路径按当前官方文档核验，不推断端点。",{"type":31,"level":21,"children":65},[66],{"text":67,"type":29},"连接复用异常和请求超时怎么定位",{"type":25,"children":69},[70],{"text":71,"type":29},"记录 DNS、TCP、TLS、首字节、总耗时、请求 ID、任务 ID和服务端任务状态。连接阶段失败查网络和代理；首字节前等待查排队或冷启动；推理中等待查任务进度；客户端超时先确认服务端是否仍在运行。",{"type":25,"children":73},[74],{"text":75,"type":29},"连接池和并发设置可参考[代理 IP 并发、QPS 和连接池怎么规划](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-ip-concurrency-qps-connection-pool)。",{"type":31,"level":21,"children":77},[78],{"text":79,"type":29},"重试前如何确认任务没有重复执行",{"type":25,"children":81},[82],{"text":83,"type":29},"创建任务或可能产生费用的请求超时后，不要立即重复提交。先按当前官方文档查询任务状态，确认未执行或可安全重试；只有幂等读取才适合有限退避。连接复用问题可用新建连接与复用连接对照，不把冷启动直接归因于代理。",{"type":25,"children":85},[86],{"text":87,"type":29},"重试策略和故障转移边界可参考[代理请求超时、失败重试和故障转移怎么设计](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-retry-timeout-failover-strategy)。",{"type":31,"level":89,"children":90},3,[91],{"text":92,"type":29},"超时后记录请求和任务状态",{"type":25,"children":94},[95],{"text":96,"type":29},"每次请求记录 `request_start`、`connect_end`、`first_byte`、任务 ID 和最终状态；代理只影响连接阶段。例如连接 150ms、首字节 28s、任务状态仍为 processing 时，不要立即重复提交，应按当前 Replicate 文档查询同一任务状态；只有确认请求未创建或操作可幂等时才重试。",{"type":31,"level":21,"children":98},[99],{"text":100,"type":29},"FAQ",{"type":31,"level":89,"children":102},[103],{"text":104,"type":29},"模型冷启动慢是否应该先更换代理？",{"type":25,"children":106},[107],{"text":108,"type":29},"不应先更换；先区分连接建立慢和服务端排队\u002F启动慢。",{"type":31,"level":89,"children":110},[111],{"text":112,"type":29},"连接超时和模型推理等待如何区分？",{"type":25,"children":114},[115],{"text":116,"type":29},"查看 DNS\u002FTCP\u002FTLS、首字节和总耗时。连接阶段失败属于网络建连问题；连接成功后首字节或推理等待较长，应结合任务状态检查服务端处理。",{"type":31,"level":89,"children":118},[119],{"text":120,"type":29},"创建任务后客户端超时，如何避免重复提交？",{"type":25,"children":122},[123],{"text":124,"type":29},"先按当前服务文档查询任务状态，确认请求是否已创建或仍在处理，再决定是否重试。",{"type":31,"level":89,"children":126},[127],{"text":128,"type":29},"哪些请求适合自动重试？",{"type":25,"children":130},[131],{"text":132,"type":29},"确认幂等的读取请求可以有限退避；创建任务或可能产生费用的请求应先查服务端状态。","",[135,218,336],{"source":6,"id":136,"documentId":137,"translationKey":137,"locale":9,"slug":138,"path":139,"_path":139,"title":140,"description":141,"excerpt":141,"image":142,"publishedAt":143,"updatedAt":144,"author":17,"tags":145,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":146,"bodyHtml":133},3476,"di2d61b0ntbxfkmt4rkgunhp","gemini-cli-proxy-http-socks5-environment-variables","\u002Fblog\u002Fgemini-cli-proxy-http-socks5-environment-variables","Gemini CLI 代理怎么设置：HTTP_PROXY 与 HTTPS_PROXY","了解 Gemini CLI 的 HTTP(S) 代理设置方式，按当前版本配置 HTTPS_PROXY、HTTP_PROXY，并验证主模型请求是否经过代理。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_gemini_cli_http_socks5_cover_3bd4a7598d.webp","2026-10-20T09:43:02.426Z","2026-10-20T09:43:02.393Z",[],[147,151,155,159,163,167,171,175,179,183,187,191,195,199,202,206,210,214],{"type":31,"level":148,"children":149},1,[150],{"text":140,"type":29},{"type":25,"children":152},[153],{"text":154,"type":29},"配置 Gemini CLI 代理 IP 前，先确认当前版本读取的代理环境变量及支持的协议，再从设置变量的同一终端启动 CLI。代理环境变量决定请求是否尝试经由指定网络出口连接；HTTP、HTTPS、SOCKS5 是接入协议，不代表代理 IP 的住宅属性或质量。",{"type":31,"level":21,"children":156},[157],{"text":158,"type":29},"先确认当前 Gemini CLI 版本读取哪些代理变量",{"type":25,"children":160},[161],{"text":162,"type":29},"先记录 Gemini CLI 版本、操作系统和安装方式，再查看该版本文档或帮助信息，确认它实际读取哪些代理变量以及支持哪些协议。不要预设 `HTTP_PROXY`、`HTTPS_PROXY`、`ALL_PROXY` 或 SOCKS5 一定可用；官方配置说明见 [Gemini CLI 配置文档](https:\u002F\u002Fgeminicli.com\u002Fdocs\u002Freference\u002Fconfiguration\u002F)。",{"type":31,"level":21,"children":164},[165],{"text":166,"type":29},"为当前终端的 Gemini CLI 主模型请求设置 HTTP(S) 代理",{"type":25,"children":168},[169],{"text":170,"type":29},"以下示例针对 Gemini CLI 主模型请求的 HTTP(S) 代理环境变量；不据此推断 MCP、沙箱或工具子进程一定继承同一设置。先记录安装版本，并确认该版本支持相应变量，再从设置变量的同一终端启动 CLI：",{"type":25,"children":172},[173],{"text":174,"type":29},"```powershell\n$env:HTTPS_PROXY = \"http:\u002F\u002F主机:端口\"\n$env:HTTP_PROXY = \"http:\u002F\u002F主机:端口\"\ngemini --help\ngemini\n```",{"type":25,"children":176},[177],{"text":178,"type":29},"```bash\nexport HTTPS_PROXY=\"http:\u002F\u002F主机:端口\"\nexport HTTP_PROXY=\"http:\u002F\u002F主机:端口\"\ngemini --help\ngemini\n```",{"type":25,"children":180},[181],{"text":182,"type":29},"以上分别是 PowerShell 与 Linux\u002FmacOS shell 设置当前终端变量的示例。是否读取变量取决于 Gemini CLI 版本；核实版本文档与 `gemini --help` 后，再用低风险主模型请求及代理日志验证。不要把含凭证 URL 写入共享脚本、命令历史或截图。本节不提供 SOCKS5\u002F`ALL_PROXY` 配置承诺，因为当前可核实的官方读取链未确认支持它们。",{"type":25,"children":184},[185],{"text":186,"type":29},"临时使用后可清除本节设置的变量：PowerShell 用 `Remove-Item Env:HTTP_PROXY,Env:HTTPS_PROXY -ErrorAction SilentlyContinue`；Linux\u002FmacOS 用 `unset HTTP_PROXY HTTPS_PROXY`。若变量原本已存在，先记录原值并在结束后恢复。",{"type":31,"level":21,"children":188},[189],{"text":190,"type":29},"检查 Gemini CLI 是否经过代理并连通服务",{"type":25,"children":192},[193],{"text":194,"type":29},"从设置变量的同一终端发起一条低风险主模型请求，结合代理侧连接日志确认该请求是否经过代理。MCP、沙箱和工具子进程需分别验证各自网络路径。CLI 无法连接代理时，可参照已发布的[代理 IP 连接排查表](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-ip-connection-troubleshooting)检查主机、端口和认证。",{"type":48,"children":196},[197],{"text":198,"type":29},"| 现象 | 检查项 | 下一步 |\n| --- | --- | --- |\n| CLI 未读代理设置 | 变量名称、大小写、启动终端及版本行为 | 对照当前版本官方说明 |\n| 代理认证失败 | 主机、端口、凭证格式和凭证字符转义 | 修正接入参数并保护凭证 |\n| 网络正常但服务报错 | CLI\u002FAPI 认证、配额、服务状态和请求参数 | 按服务端错误分层排查 |",{"type":31,"level":21,"children":200},[201],{"text":100,"type":29},{"type":31,"level":89,"children":203},[204],{"text":205,"type":29},"设置 `HTTPS_PROXY` 后，怎么确认 Gemini CLI 确实走了代理？",{"type":25,"children":207},[208],{"text":209,"type":29},"从设置变量的同一终端启动 CLI，发起一条低风险请求，并结合进程环境、客户端或代理日志、出口检测确认请求路径。仅看到变量已设置，不能证明当前版本的 CLI 已读取它。",{"type":31,"level":89,"children":211},[212],{"text":213,"type":29},"HTTP 和 SOCKS5 哪个更适合？",{"type":25,"children":215},[216],{"text":217,"type":29},"本文示例使用 HTTP(S) 代理变量。当前版本是否支持其它代理协议，应查该版本文档；设置未确认读取的变量不能证明请求已使用相应代理。协议本身也不能说明代理 IP 的住宅\u002F机房属性或业务结果。",{"source":6,"id":219,"documentId":220,"translationKey":220,"locale":9,"slug":221,"path":222,"_path":222,"title":223,"description":224,"excerpt":224,"image":225,"publishedAt":226,"updatedAt":227,"author":17,"tags":228,"featured":19,"sortOrder":20,"readingTime":89,"bodyType":22,"bodyBlocks":229,"bodyHtml":133},3475,"x4a9q0bme23m2tka73ym65lm","nginx-websocket-400-502-504-troubleshooting","\u002Fblog\u002Fnginx-websocket-400-502-504-troubleshooting","Nginx WebSocket 反向代理排查：400、502、504 与超时","Nginx WebSocket 反向代理返回 400、502 或 504 时，按 Upgrade 握手、上游连接和超时日志逐项排查，并用 curl 与 websocat 验证配置。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_nginx_websocket_400_502_504_cover_a2295cdc39.webp","2026-10-20T09:42:46.326Z","2026-10-20T09:42:46.313Z",[],[230,234,238,242,246,250,254,258,262,266,270,274,278,282,286,290,294,298,302,305,309,313,317,321,324,328,332],{"type":25,"children":231},[232],{"text":233,"type":29},"Nginx WebSocket 反向代理返回 400、502 或 504 时，先记录响应状态并对照 Nginx 和上游日志。本文排查的是 Nginx 到上游的反向代理链路；400 优先检查请求或握手，502 检查上游连接与响应，504 检查上游响应时间和超时设置。状态码只能指示排查方向，根因要结合日志确认。",{"type":31,"level":21,"children":235},[236],{"text":237,"type":29},"配好 Upgrade 和 Connection 转发头",{"type":25,"children":239},[240],{"text":241,"type":29},"先确认客户端是否发送 WebSocket 握手请求。Nginx 反向代理通常需要使用 HTTP\u002F1.1，并将 Upgrade 与 Connection 头转给上游。配置结构如下，需放在正确的 `http`、`server` 或 `location` 层级，并按实际上游调整。",{"type":25,"children":243},[244],{"text":245,"type":29},"可对照 [Nginx 官方 WebSocket 代理说明](https:\u002F\u002Fnginx.org\u002Fen\u002Fdocs\u002Fhttp\u002Fwebsocket.html)检查 Upgrade 转发行为；具体指令以部署版本文档为准。",{"type":25,"children":247},[248],{"text":249,"type":29},"```nginx\nproxy_http_version 1.1;\nproxy_set_header Upgrade $http_upgrade;\nproxy_set_header Connection $connection_upgrade;\nproxy_set_header Host $host;\nproxy_connect_timeout 5s;\nproxy_read_timeout 60s;\n```",{"type":25,"children":251},[252],{"text":253,"type":29},"上例假设已在 `http` 层用 `map $http_upgrade $connection_upgrade { default upgrade; '' close; }` 定义 `$connection_upgrade`，并配置了对应 `proxy_pass` 和上游；按实际上游替换。`5s` 与 `60s` 只是示例值，需依据网络和心跳要求调整。`proxy_connect_timeout` 限制建立上游连接的等待时间；`proxy_read_timeout` 限制两次从上游读取数据之间的空闲间隔，不能修复连接拒绝或错误握手。",{"type":25,"children":255},[256],{"text":257,"type":29},"超时指令的版本和上下文限制见 [Nginx 官方 proxy 模块文档](https:\u002F\u002Fnginx.org\u002Fen\u002Fdocs\u002Fhttp\u002Fngx_http_proxy_module.html#proxy_read_timeout)。",{"type":25,"children":259},[260],{"text":261,"type":29},"随后查看客户端网络面板，确认失败发生在握手阶段还是握手之后。",{"type":31,"level":21,"children":263},[264],{"text":265,"type":29},"看 400、502、504 判断请求卡在哪一环",{"type":48,"children":267},[268],{"text":269,"type":29},"| 状态码 | 优先检查 | 证据位置 | 后续动作 |\n| --- | --- | --- | --- |\n| 400 | 请求路径、Upgrade\u002FConnection 头、上游对握手的校验 | 客户端请求、Nginx access log、上游响应 | 对照协议要求和上游路由，不盲目延长超时 |\n| 502 | 上游地址\u002F端口、连接拒绝、DNS 解析及上游进程状态 | Nginx error log、上游服务日志 | 先从 Nginx 主机验证到上游的连接 |\n| 504 | 上游处理时间、连接\u002F读取超时设置、服务负载 | error log 时间戳、上游耗时和负载 | 找出等待发生在哪一跳，再评估超时配置 |",{"type":25,"children":271},[272],{"text":273,"type":29},"用 access log 中的时间、URI、状态码及上游状态\u002F耗时字段找到请求，再查看对应的 error log 和上游日志，确认请求是否到达上游、在哪一跳失败。不同版本和上游实现的返回状态可能不同，应沿同一请求的日志链路判断。",{"type":31,"level":21,"children":275},[276],{"text":277,"type":29},"用客户端和两端日志复现并定位故障",{"type":25,"children":279},[280],{"text":281,"type":29},"记录 Nginx 版本、脱敏后的相关配置、目标路径、发生时间、响应状态、请求 ID 和上游日志。先验证客户端到 Nginx，再验证 Nginx 到上游；每次只调整一个配置项后复测。不要公开 token、Cookie、Authorization 头或内网敏感地址。",{"type":25,"children":283},[284],{"text":285,"type":29},"配置变更后先检查语法，再平滑重载，并分别验证普通 HTTP 与 WebSocket 握手。以下命令需在 Nginx 主机执行，域名和路径按环境替换：",{"type":25,"children":287},[288],{"text":289,"type":29},"```bash\nsudo nginx -t\nsudo nginx -s reload\ncurl -i https:\u002F\u002Fexample.com\u002Fws\nwebsocat -v wss:\u002F\u002Fexample.com\u002Fws\n```",{"type":25,"children":291},[292],{"text":293,"type":29},"`nginx -t` 失败时不要 reload。普通 curl 通常没有发送完整 Upgrade 握手，不能用它判定 WebSocket 成功；`websocat` 应完成握手并建立连接，成功响应为 `101 Switching Protocols`。结合 Nginx access\u002Ferror log 中的 `$upstream_status`、`$upstream_connect_time` 和 `$upstream_response_time` 定位失败阶段。",{"type":31,"level":21,"children":295},[296],{"text":297,"type":29},"根据日志区分握手失败、上游连接失败和响应超时",{"type":25,"children":299},[300],{"text":301,"type":29},"请求未到达上游时，检查 Nginx 配置、DNS 和连接；上游返回 400 时核对 Upgrade\u002FConnection 请求头、路径和上游校验；上游连接被拒绝或出现 502 时检查地址、端口及服务状态；只有日志显示请求已到达上游且等待超过当前限制时，才按官方 proxy 模块文档评估超时。每次只改一个配置项，并用相同路径复测。",{"type":31,"level":21,"children":303},[304],{"text":100,"type":29},{"type":31,"level":89,"children":306},[307],{"text":308,"type":29},"`proxy_read_timeout` 调大后仍返回 504，下一步看什么？",{"type":25,"children":310},[311],{"text":312,"type":29},"按正文日志分支确认请求是否到达上游、等待发生在哪一跳，再检查上游耗时和服务负载；不要只通过继续增大超时处理上游不可用或链路异常。",{"type":31,"level":89,"children":314},[315],{"text":316,"type":29},"`curl` 返回 200 就能证明 WebSocket 正常吗？",{"type":25,"children":318},[319],{"text":320,"type":29},"不能。普通 curl 请求不一定发送 WebSocket Upgrade 握手；应使用 WebSocket 客户端验证，并确认握手成功返回 `101 Switching Protocols`，再观察连接是否按预期维持。",{"type":25,"children":322},[323],{"text":133,"type":29},{"type":25,"children":325},[326],{"text":327,"type":29},"---",{"type":31,"level":21,"children":329},[330],{"text":331,"type":29},"对照日志复测 WebSocket 修复结果",{"type":25,"children":333},[334],{"text":335,"type":29},"按失败请求的时间戳复核 access\u002Ferror log 与上游日志，再用相同路径确认握手是否返回 101、连接能否维持。若故障发生在客户端代理 IP 到 Nginx 之前，应另查客户端到代理的连接链路。",{"source":6,"id":337,"documentId":338,"translationKey":338,"locale":9,"slug":339,"path":340,"_path":340,"title":341,"description":342,"excerpt":342,"image":343,"publishedAt":344,"updatedAt":345,"author":17,"tags":346,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":347,"bodyHtml":133},3474,"k1c5f17zwlsh9vx5sz4dolif","websocket-proxy-connection-troubleshooting","\u002Fblog\u002Fwebsocket-proxy-connection-troubleshooting","WebSocket 代理 IP 连接失败怎么办：认证、TLS 与 Upgrade 排查","WebSocket 通过代理 IP 连接失败时，可按代理连接、认证、TLS 隧道和 Upgrade 握手逐步排查，并用最小验证确认故障环节。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_websocket_cover_3f066ac782.webp","2026-10-20T09:42:30.996Z","2026-10-20T09:42:30.971Z",[],[348,352,356,360,364,368,372,376,380,384,388,392,396,400,404,407,411,415,419,423,426,429,433],{"type":25,"children":349},[350],{"text":351,"type":29},"WebSocket 通过代理 IP 连接失败时，先确定使用的是客户端正向代理还是服务端反向代理，再判断失败发生在 TCP 连接、代理认证、TLS 还是 WebSocket Upgrade 阶段。按时间戳保存客户端错误、代理日志和目标服务响应；只有证据指向代理连接或会话问题时，才继续调整代理参数。",{"type":31,"level":21,"children":353},[354],{"text":355,"type":29},"先确认失败在代理连接、TLS 还是 WebSocket 握手",{"type":25,"children":357},[358],{"text":359,"type":29},"常见路径是客户端连接代理，再通过代理到达目标服务，随后完成 TLS（如使用 WSS）和 WebSocket 握手。若 Nginx 在服务端作为反向代理，应按 Nginx 反向代理链路单独排查；不要把两种代理角色混为一谈。主机、端口、认证或连接问题可参考已发布的[代理 IP 连接排查表](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-ip-connection-troubleshooting)。",{"type":31,"level":21,"children":361},[362],{"text":363,"type":29},"从客户端错误判断连接失败在哪一步",{"type":48,"children":365},[366],{"text":367,"type":29},"| 现象 | 可能阶段 | 检查内容 | 下一步 |\n| --- | --- | --- | --- |\n| 无法连接代理地址 | 客户端到代理 | 主机、端口、协议、网络连通性 | 验证接入参数及本地网络 |\n| 407 或代理认证失败 | 代理认证 | 用户名、密码、认证类型和 URL 转义 | 修正凭证并避免在日志中泄露 |\n| TLS 错误或握手中断 | TLS\u002F隧道 | 客户端是否支持该代理协议及目标 TLS | 查看客户端错误和代理日志 |\n| HTTP 响应正常但 Upgrade 失败 | WebSocket 握手\u002F目标服务 | Upgrade 请求头、目标路径、服务端响应 | 核对客户端与目标服务配置 |\n| 连接建立后很快断开 | 会话\u002F网络链路 | 空闲超时、心跳、代理会话和目标端日志 | 固定条件复现并记录断开时间 |",{"type":25,"children":369},[370],{"text":371,"type":29},"HTTP、HTTPS、SOCKS5 是接入协议，不代表住宅或数据中心属性。客户端是否支持 WebSocket 通过特定代理协议，应查其当前文档；不要根据协议名称推断兼容性。",{"type":31,"level":21,"children":373},[374],{"text":375,"type":29},"从代理连接开始验证，直到收到 Upgrade 响应",{"type":25,"children":377},[378],{"text":379,"type":29},"记录客户端版本、脱敏后的目标 URL、代理协议、错误信息、发生时间和连接时长。先用客户端连接测试或受控目标确认目标服务可用，再对照[代理参数说明](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002Fintro)核对主机、端口和认证参数；随后分别验证代理认证、TLS 和 WebSocket Upgrade 响应。每轮只改一个变量，并保存客户端、代理和目标服务日志。遇到 403、429 或验证码时，按目标站规则停止或调整请求。",{"type":25,"children":381},[382],{"text":383,"type":29},"下面的 `proxy.example.com`、端口和 URL 都是占位值；命令用 curl 检查 HTTP(S) 代理连通性，不能单独证明 WebSocket Upgrade 成功。凭证优先通过受保护的环境变量传入，避免写进命令历史或截图：",{"type":25,"children":385},[386],{"text":387,"type":29},"```bash\ncurl -v --proxy http:\u002F\u002Fproxy.example.com:8080 \\\n--proxy-user \"$PROXY_USER:$PROXY_PASS\" \\\nhttps:\u002F\u002Fexample.com\u002F -o \u002Fdev\u002Fnull\n```",{"type":25,"children":389},[390],{"text":391,"type":29},"先看代理连接是否建立及是否出现 `407`。目标返回正常 HTTP 响应仅表示普通请求经代理完成，不代表 Upgrade 成功。WebSocket 验证应使用客户端连接实际 `wss:\u002F\u002F` 地址，并检查服务端是否返回 `101 Switching Protocols`；若收到 `400\u002F403` 等响应，记录状态和响应头，并按目标规则停止不必要重试。",{"type":25,"children":393},[394],{"text":395,"type":29},"curl 示例只验证普通 HTTP(S) 经代理的连接，不能代替 WebSocket 握手。实际 WSS 验证需使用明确支持 HTTP CONNECT 或 SOCKS 代理的 WebSocket 客户端，并连到自有测试端；核对代理认证成功、握手返回 `101`、消息可收发且连接可正常关闭。客户端及其代理参数因库和版本不同，只有核验具体客户端后才应给出可复制命令；不要把不确定支持代理的工具当作验证步骤。",{"type":31,"level":21,"children":397},[398],{"text":399,"type":29},"按连接阶段判断应该检查哪一端",{"type":25,"children":401},[402],{"text":403,"type":29},"代理连接或认证失败时，核对代理主机、端口、协议和认证；TLS 隧道失败时，查看客户端支持范围及 TLS 错误；代理已连通但 Upgrade 失败时，检查目标路径、握手请求和服务端响应；建立后很快断开时，检查空闲超时、心跳和会话规则。若问题发生在 Nginx 到上游的反向代理链路，应按对应 Nginx WebSocket 配置排查。每轮只调整一个变量。",{"type":31,"level":21,"children":405},[406],{"text":100,"type":29},{"type":31,"level":89,"children":408},[409],{"text":410,"type":29},"HTTP 代理也能承载 WebSocket 吗？",{"type":25,"children":412},[413],{"text":414,"type":29},"取决于客户端和代理是否支持相应的隧道或 Upgrade 流程。不要单凭协议名称判断兼容性；用实际客户端连接目标 `ws:\u002F\u002F` 或 `wss:\u002F\u002F` 地址，并检查握手响应及连接日志。",{"type":31,"level":89,"children":416},[417],{"text":418,"type":29},"连接失败时应先换代理 IP 吗？",{"type":25,"children":420},[421],{"text":422,"type":29},"先定位失败阶段。只有证据指向代理连接、认证或隧道问题时，才考虑调整代理；目标服务或应用层错误应检查对应配置。",{"type":25,"children":424},[425],{"text":133,"type":29},{"type":25,"children":427},[428],{"text":327,"type":29},{"type":31,"level":21,"children":430},[431],{"text":432,"type":29},"按故障位置复核 WebSocket 连接配置",{"type":25,"children":434},[435],{"text":436,"type":29},"把失败时间、代理协议、客户端版本、阶段、状态码和脱敏日志交给客户端或代理服务支持团队；若确认故障位于 Nginx 到上游链路，再按对应反向代理配置排查。",[438],{"source":6,"id":7,"documentId":8,"translationKey":8,"locale":9,"slug":10,"path":11,"_path":11,"title":12,"description":13,"excerpt":13,"image":14,"publishedAt":15,"updatedAt":16,"author":17,"tags":439,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":440,"bodyHtml":133},[],[441,444,447,450,453,456,459,462,465,468,471,474,477,480,483,486,489,492,495,498,501,504,507,510,513,516],{"type":25,"children":442},[443],{"text":28,"type":29},{"type":31,"level":21,"children":445},[446],{"text":34,"type":29},{"type":25,"children":448},[449],{"text":38,"type":29},{"type":25,"children":451},[452],{"text":42,"type":29},{"type":25,"children":454},[455],{"text":46,"type":29},{"type":48,"children":457},[458],{"text":51,"type":29},{"type":25,"children":460},[461],{"text":55,"type":29},{"type":31,"level":21,"children":463},[464],{"text":59,"type":29},{"type":25,"children":466},[467],{"text":63,"type":29},{"type":31,"level":21,"children":469},[470],{"text":67,"type":29},{"type":25,"children":472},[473],{"text":71,"type":29},{"type":25,"children":475},[476],{"text":75,"type":29},{"type":31,"level":21,"children":478},[479],{"text":79,"type":29},{"type":25,"children":481},[482],{"text":83,"type":29},{"type":25,"children":484},[485],{"text":87,"type":29},{"type":31,"level":89,"children":487},[488],{"text":92,"type":29},{"type":25,"children":490},[491],{"text":96,"type":29},{"type":31,"level":21,"children":493},[494],{"text":100,"type":29},{"type":31,"level":89,"children":496},[497],{"text":104,"type":29},{"type":25,"children":499},[500],{"text":108,"type":29},{"type":31,"level":89,"children":502},[503],{"text":112,"type":29},{"type":25,"children":505},[506],{"text":116,"type":29},{"type":31,"level":89,"children":508},[509],{"text":120,"type":29},{"type":25,"children":511},[512],{"text":124,"type":29},{"type":31,"level":89,"children":514},[515],{"text":128,"type":29},{"type":25,"children":517},[518],{"text":132,"type":29},null,[],[]]