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