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