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