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