[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-strapi-article:zh:proxy-ip-geo-location-failed":3,"blog-article:\u002Fblog\u002Fproxy-ip-geo-location-failed":731,"blog-related:\u002Fblog\u002Fproxy-ip-geo-location-failed":732,"blog-translations:\u002Fblog\u002Fproxy-ip-geo-location-failed":733},{"available":4,"article":5,"relatedArticles":191,"translations":607},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":190},"strapi",2577,"e71zho51ev24tyfieuuhcame","zh","proxy-ip-geo-location-failed","\u002Fblog\u002Fproxy-ip-geo-location-failed","自动化脚本使用代理时如何记录 IP、地区和失败原因？","自动化脚本使用代理时，应同时记录出口 IP、地区、状态码、耗时和异常类型。本文给出日志字段、JSON 示例、验证步骤及 407、403、429 和超时的归因方法。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_ip_cover_4513e73b77.webp","2026-09-08T07:21:33.056Z","2026-09-08T07:21:33.041Z","Global Proxies Team",[],false,0,5,"blocks",[24,30,36,41,45,49,53,57,61,65,69,73,77,81,85,89,94,98,102,106,110,114,118,122,126,130,134,138,142,146,150,154,158,162,166,170,174,178,182,186],{"type":25,"children":26},"paragraph",[27],{"text":28,"type":29},"自动化脚本不能只记录“成功”或“失败”。至少要把目标 URL、代理 IP 类型、出口 IP、出口地区、协议、状态码、耗时、重试次数和异常类型写入同一条代理日志，才能区分接入错误、网络异常、地区识别偏差和目标站拒绝。开始放量前，先用 IP 检测页与真实目标页面完成一轮小样本验证。","text",{"type":31,"level":32,"children":33},"heading",2,[34],{"text":35,"type":29},"自动化脚本至少要记录哪些代理字段",{"type":37,"children":38},"code",[39],{"text":40,"type":29},"| 字段 | 作用 | 示例 |\n| --- | --- | --- |\n| timestamp | 对照失败时间和流量波动 | 2026-09-07T10:30:00+08:00 |\n| target_url | 确认失败是否只出现在某个站点 | https:\u002F\u002Fexample.com\u002Fpage |\n| proxy_type | 区分动态住宅、静态住宅或机房代理 IP | dynamic_residential |\n| protocol | 核对 HTTP、HTTPS 或 SOCKS5 接入 | http |\n| exit_ip | 判断请求是否经过代理及是否发生切换 | masked |\n| country \u002F city | 检查出口地区和业务目标是否一致 | 以检测结果为准 |\n| status_code | 区分认证、限流和目标站错误 | 200、403、407、429、5xx |\n| latency_ms | 判断超时或高延迟 | 毫秒值 |\n| error_type | 统一失败分类 | auth、timeout、blocked、network |\n| retry_count | 判断重试是否放大失败 | 0、1、2 |\n| session_id | 关联同一会话内的多次请求 | 使用脱敏标识 |",{"type":25,"children":42},[43],{"text":44,"type":29},"**日志中不要写入真实代理密码、token、Cookie 或完整账号信息。需要关联账号时，使用不可逆的脱敏标识。**",{"type":31,"level":32,"children":46},[47],{"text":48,"type":29},"为什么要用结构化日志记录请求",{"type":25,"children":50},[51],{"text":52,"type":29},"JSON 或 CSV 比纯文本错误信息更容易筛选和汇总。一条 JSON 日志可以采用下面的结构：",{"type":25,"children":54},[55],{"text":56,"type":29},"~~~json\n{\n\"timestamp\": \"2026-09-07T10:30:00+08:00\",\n\"target_url\": \"https:\u002F\u002Fexample.com\u002Fpage\",\n\"proxy_type\": \"dynamic_residential\",\n\"protocol\": \"http\",\n\"exit_ip\": \"masked\",\n\"country\": \"expected-country\",\n\"city\": \"detected-city\",\n\"status_code\": 429,\n\"latency_ms\": 1820,\n\"error_type\": \"rate_limited\",\n\"retry_count\": 1,\n\"session_id\": \"job-001\"\n}\n~~~",{"type":25,"children":58},[59],{"text":60,"type":29},"同一批任务要固定字段名和错误枚举，避免一部分日志写 timeout，另一部分写“连接超时”，导致后续无法统计。",{"type":25,"children":62},[63],{"text":64,"type":29},"一次脱敏运行记录（Python requests、单并发、同一目标 URL）如下：",{"type":25,"children":66},[67],{"text":68,"type":29},"```json\n{\"time\":\"2026-09-06T16:31:08+08:00\",\"url\":\"https:\u002F\u002Fexample.test\u002Fgeo\",\"proxy_type\":\"dynamic_residential\",\"exit_ip\":\"198.51.100.***\",\"country\":\"JP\",\"city\":\"Tokyo\",\"status\":200,\"latency_ms\":534,\"retry\":0,\"error\":null}\n{\"time\":\"2026-09-06T16:31:14+08:00\",\"url\":\"https:\u002F\u002Fexample.test\u002Fgeo\",\"proxy_type\":\"dynamic_residential\",\"exit_ip\":\"198.51.100.***\",\"country\":\"US\",\"city\":\"California\",\"status\":0,\"latency_ms\":3000,\"retry\":1,\"error\":\"read_timeout\",\"trace\":\"ReadTimeout: HTTPSConnectionPool(...): Read timed out\"}\n{\"time\":\"2026-09-06T16:31:22+08:00\",\"url\":\"https:\u002F\u002Fexample.test\u002Fgeo\",\"proxy_type\":\"dynamic_residential\",\"exit_ip\":\"198.51.100.***\",\"country\":\"JP\",\"city\":\"Tokyo\",\"status\":200,\"latency_ms\":612,\"retry\":2,\"error\":null}\n```",{"type":25,"children":70},[71],{"text":72,"type":29},"第一条成功、第二条地区跳变并超时、第三条复测恢复，说明应把“地区不一致”和“读取超时”分别归因，并通过出口 IP、重试次数和堆栈关联同一会话。",{"type":25,"children":74},[75],{"text":76,"type":29},"一个最小的记录流程可以写成下面这样。伪代码不绑定具体语言，实际接入时只需替换请求客户端和日志组件：",{"type":25,"children":78},[79],{"text":80,"type":29},"~~~text\nrequest_id = create_id()\nstart = now()\nexit_ip = null\ncountry = null\ncity = null\nlog(request_id, target_url, proxy_type, protocol, status=\"started\")",{"type":25,"children":82},[83],{"text":84,"type":29},"try:\nexit_ip, country, city = check_proxy_exit()\nresponse = request(target_url, proxy)\nlog(request_id, exit_ip, country, city,\nstatus_code=response.status, latency_ms=now()-start,\nerror_type=null, retry_count=retry_count)\nexcept Exception as error:\nlog(request_id, exit_ip, country, city,\nstatus_code=get_status(error), latency_ms=now()-start,\nerror_type=classify(error), retry_count=retry_count)\n~~~",{"type":25,"children":86},[87],{"text":88,"type":29},"无论请求成功还是失败，都应保留同一个 `request_id` 的完整记录；重试时新增记录并递增 `retry_count`，不要覆盖第一次失败。",{"type":31,"level":90,"children":91},3,[92],{"text":93,"type":29},"最小可用的日志字段",{"type":25,"children":95},[96],{"text":97,"type":29},"如果暂时不能记录完整链路，至少保留 `request_id`、`target_url`、`proxy_type`、`protocol`、`exit_ip`、`expected_country`、`detected_country`、`expected_city`、`detected_city`、`status_code`、`latency_ms`、`error_type` 和 `retry_count`。其中 `expected_*` 表示任务目标，`detected_*` 表示检测结果，二者分开保存，才能识别“代理出口正确但目标站仍未本地化”的情况。可以增加 DNS、连接和首字节耗时，敏感字段按前文字段表后的脱敏规则处理。",{"type":31,"level":32,"children":99},[100],{"text":101,"type":29},"请求前、请求中和请求后分别记录什么",{"type":25,"children":103},[104],{"text":105,"type":29},"1. 请求前记录任务编号、目标 URL、代理 IP 类型、协议和会话标识。\n2. 首次使用该代理信息时，访问 IP 检测页并记录出口 IP、国家和城市。\n3. 发起真实业务请求，记录状态码、耗时和响应类型。\n4. 捕获连接拒绝、DNS、TLS、认证和读取超时等异常。\n5. 发生重试时保留原失败记录，不要只保存最后一次结果。\n6. 任务结束后按目标站、状态码、出口地区和代理 IP 类型汇总。",{"type":25,"children":107},[108],{"text":109,"type":29},"代理主机、端口、账号、密码和协议应从对应产品后台或[代理参数说明](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002Fintro)获取，不要从第三方截图推断端口或认证方式。需要接入流程时可查看[获取代理帮助](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002FGet-Proxy\u002F)。",{"type":31,"level":32,"children":111},[112],{"text":113,"type":29},"不同失败表现应该怎么分类",{"type":37,"children":115},[116],{"text":117,"type":29},"| 表现 | 先检查 | 下一步 |\n| --- | --- | --- |\n| 出口 IP 未变化 | 代理是否启用、协议和端口是否正确 | 换 IP 检测页或客户端复测 |\n| 407 | 账号密码、认证方式、协议和端口 | 用同组参数在另一客户端复测 |\n| 403 | 目标站规则、Cookie、账号状态、出口地区 | 固定其他变量，只更换一个出口复测 |\n| 429 | 请求频率、并发、重试策略 | 降低频率并增加退避时间 |\n| 超时或连接拒绝 | 本地网络、代理端口、目标站响应 | 分别测试 IP 检测页和目标 URL |\n| 地区识别不一致 | IP 库、目标站识别、语言和 Cookie | 用多个检测源及目标页面交叉验证 |",{"type":25,"children":119},[120],{"text":121,"type":29},"不要把所有 403、429 或验证码都标记成“代理 IP 不可用”。只有完成对照实验后，才能判断应更换代理 IP、调整会话策略，还是转查目标站和脚本逻辑。",{"type":31,"level":90,"children":123},[124],{"text":125,"type":29},"记录到异常后应该怎么处理",{"type":25,"children":127},[128],{"text":129,"type":29},"例如，407 且每次请求都失败，通常先修正认证、协议或端口；代理检测成功但目标站持续 403，应固定其他变量后检查 Cookie、账号和目标站规则；429 在重试后比例上升，应降低频率并增加退避；出口地区正确但页面语言或内容不符，则要对照语言、时区、设备和 Cookie。日志的作用是缩小问题范围，不是自动证明代理 IP 一定失效。",{"type":31,"level":32,"children":131},[132],{"text":133,"type":29},"动态和静态代理 IP 分别要记录什么",{"type":25,"children":135},[136],{"text":137,"type":29},"动态住宅代理 IP 可能按请求或粘性会话切换，因此日志必须记录每次请求或每个会话的出口 IP。静态住宅代理 IP 更适合长期身份和连续会话，但仍要记录掉线、出口变化和会话中断。机房代理 IP 更适合住宅属性不是硬要求、重视速度或成本的公开访问测试，是否适用要由目标站实测决定。",{"type":31,"level":32,"children":139},[140],{"text":141,"type":29},"代理代码接入和日志排障怎么开始",{"type":25,"children":143},[144],{"text":145,"type":29},"前文已经分别给出日志字段、API 和接入说明；需要统一查看时，可进入[代理设置帮助](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002Fproxy-Settings)。",{"type":31,"level":32,"children":147},[148],{"text":149,"type":29},"FAQ",{"type":31,"level":90,"children":151},[152],{"text":153,"type":29},"自动化脚本最少需要记录哪些代理字段？",{"type":25,"children":155},[156],{"text":157,"type":29},"至少记录目标 URL、出口 IP、地区、协议、状态码、耗时、异常类型和重试次数。登录态任务还应增加脱敏会话标识，方便关联同一会话的请求。",{"type":31,"level":90,"children":159},[160],{"text":161,"type":29},"如何确认脚本真的走了代理？",{"type":25,"children":163},[164],{"text":165,"type":29},"先在脚本内访问 IP 检测页，再与直连出口对比。随后用同一组代理参数访问目标 URL，分别记录出口地区和响应结果。",{"type":31,"level":90,"children":167},[168],{"text":169,"type":29},"407、403 和 429 可以用同一种重试策略吗？",{"type":25,"children":171},[172],{"text":173,"type":29},"不可以。407 应先修正认证，403 要排查目标站规则和环境，429 应降低频率并设置退避；盲目重试可能放大问题。",{"type":31,"level":90,"children":175},[176],{"text":177,"type":29},"日志可以保存代理密码和 Cookie 吗？",{"type":25,"children":179},[180],{"text":181,"type":29},"不建议。日志应隐藏密码、token、Cookie 和账号信息，只保留排障所需的脱敏标识。",{"type":25,"children":183},[184],{"text":185,"type":29},"---",{"type":25,"children":187},[188],{"text":189,"type":29},"先用少量真实请求跑通“检测出口—访问目标—记录失败—分类汇总”的闭环，再根据日志中的地区命中率、状态码比例、延迟和重试结果决定是否扩大任务规模。错误码可继续查阅[代理 API 错误码和程序报错怎么查](https:\u002F\u002Fwww.quanqiudaili.com\u002Fdevelopers\u002Fproxy-error-codes\u002F)，并结合[代理请求超时、失败重试和故障转移怎么设计](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-retry-timeout-failover-strategy)优化重试策略；日志排查方法可参考[代理日志怎么帮助排查采集失败](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-troubleshooting-scraping-failed)。需要产品咨询时可前往[注册或咨询全球代理服务](https:\u002F\u002Fwww.quanqiudaili.com\u002Fsignup)。","",[192,327,481],{"source":6,"id":193,"documentId":194,"translationKey":194,"locale":9,"slug":195,"path":196,"_path":196,"title":197,"description":198,"excerpt":198,"image":199,"publishedAt":200,"updatedAt":201,"author":17,"tags":202,"featured":19,"sortOrder":20,"readingTime":32,"bodyType":22,"bodyBlocks":203,"bodyHtml":190},2627,"s72n0bjt3ja39uo12fljzmtq","dynamic-residential-proxy-ip-static-residential","\u002Fblog\u002Fdynamic-residential-proxy-ip-static-residential","动态住宅代理 IP 适合哪些业务？和静态住宅代理 IP 怎么选？","动态住宅代理 IP 适合多地区采样、价格监测与批量测试，静态住宅代理 IP 更适合长期登录和账号运营；上线前检查出口稳定性与连通性，选对方案再扩量。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_ip_cover_8edd536e12.webp","2026-09-10T06:35:36.797Z","2026-09-10T06:35:36.670Z",[],[204,208,212,216,237,241,245,249,253,257,261,265,269,273,277,281,285,288,292,296,300,304,308,312,316,320,323],{"type":25,"children":205},[206],{"text":207,"type":29},"动态住宅代理 IP 更适合短会话、多地区轮换、公开采样和批量测试；静态住宅代理 IP 更适合长期登录、店铺后台和广告账户。选择时先看业务能否接受出口变化，再比较地区、会话时长、协议、认证方式和成本。",{"type":31,"level":32,"children":209},[210],{"text":211,"type":29},"哪些业务适合动态住宅代理 IP",{"type":25,"children":213},[214],{"text":215,"type":29},"价格监测、广告展示核对、搜索结果观察、公开页面采样和多地区测试，通常更重视 IP 数量与轮换效率。动态住宅代理 IP 可按请求或粘性会话切换，适合彼此独立、无需保持同一出口的短会话。",{"type":217,"format":218,"children":219},"list","unordered",[220,225,229,233],{"type":221,"children":222},"list-item",[223],{"text":224,"type":29},"价格监测：每次请求可以使用不同出口，便于抽样多个地区和运营商，减少为保持单一身份而付出的会话成本。",{"type":221,"children":226},[227],{"text":228,"type":29},"广告展示核对：轮换出口能观察不同本地网络视角，适合发现广告素材、落地页或地区定向的变化；但预算、频控和 Cookie 仍要固定。",{"type":221,"children":230},[231],{"text":232,"type":29},"搜索结果观察：同一关键词在多个出口上采样，便于区分地区差异与单个出口的偶然结果，不需要让所有请求长期绑定一个 IP。",{"type":221,"children":234},[235],{"text":236,"type":29},"公开页面采样和多地区测试：请求彼此独立、失败后可换出口重试，轮换效率通常比长期保持同一出口更重要。",{"type":31,"level":32,"children":238},[239],{"text":240,"type":29},"哪些长期任务不适合使用动态住宅代理 IP？",{"type":25,"children":242},[243],{"text":244,"type":29},"长期登录、店铺后台、广告账户和支付后台更依赖稳定出口身份，通常优先测试静态住宅代理 IP，并保持设备指纹、语言、时区和操作节奏一致。静态住宅代理 IP 也不代表平台一定放行，仍需结合账号和环境判断。",{"type":31,"level":32,"children":246},[247],{"text":248,"type":29},"动态住宅代理 IP 和静态住宅代理 IP 怎么选",{"type":37,"children":250},[251],{"text":252,"type":29},"| 判断项 | 动态住宅代理 IP | 静态住宅代理 IP |\n| --- | --- | --- |\n| 主要任务 | 短时采样、多地区轮换 | 长期登录、稳定身份 |\n| 出口变化 | 可按请求或会话切换 | 在服务有效且配置不变时保持同一出口；异常更换或服务状态变化仍需核对 |\n| 重点确认 | 切换规则、会话时长、流量计费 | 独享性、持续可用性、周期计费 |",{"type":25,"children":254},[255],{"text":256,"type":29},"如果同时进行数据采样和账号操作，建议分别使用两套环境，避免出口变化互相干扰。",{"type":31,"level":32,"children":258},[259],{"text":260,"type":29},"购买动态或静态住宅代理 IP 前，要确认哪些产品参数？",{"type":25,"children":262},[263],{"text":264,"type":29},"动态住宅代理 IP 要确认切换规则、粘性会话、并发和流量计费；静态住宅代理 IP 要确认周期、独享性、地区、协议和异常更换规则。规格和价格以购买页、后台或客户经理确认为准。可参考[动态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fdynamic-residential)、[静态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fstatic-residential-standard)和[原生静态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fstatic-residential-native)。",{"type":31,"level":32,"children":266},[267],{"text":268,"type":29},"动态住宅和静态住宅代理 IP 上线前，如何做对照验证？",{"type":25,"children":270},[271],{"text":272,"type":29},"固定账号、设备和目标网站，只改变代理 IP 类型；例如对短时采样记录每 100 次请求的地区跳变和验证码次数，对长期登录记录 24 小时内会话中断次数，再决定是否放量。",{"type":25,"children":274},[275],{"text":276,"type":29},"为了让记录可比较，可以先用下表的“示意区间”设计验收表，再替换成自己的真实观测值。数字仅演示记录格式，不是行业基准、供应商承诺或本文实测结论：",{"type":37,"children":278},[279],{"text":280,"type":29},"| 指标（固定同一目标站） | 动态住宅代理 IP：示意记录 | 静态住宅代理 IP：示意记录 | 如何解读 |\n| --- | --- | --- | --- |\n| 每 100 次请求的地区跳变 | 约 60–90 次 | 约 0–5 次 | 动态是否达到轮换预期，静态是否保持地区稳定 |\n| 每 100 次请求的验证码触发 | 约 3–12 次 | 约 0–4 次 | 不能单独归因于 IP，还要记录账号、设备和请求节奏 |\n| 24 小时会话中断 | 不作为主要验收项，记录实际次数 | 约 0–2 次 | 静态长期任务重点看中断原因和恢复方式 |",{"type":25,"children":282},[283],{"text":284,"type":29},"正式测试时应把每次出口、时间戳、状态码、地区库结果和截图一起保存；如果结果落在区间外，先复核目标站策略、Cookie、DNS\u002FWebRTC 和并发条件，再决定是否更换代理类型。",{"type":31,"level":32,"children":286},[287],{"text":149,"type":29},{"type":31,"level":90,"children":289},[290],{"text":291,"type":29},"并发和计费如何确认？",{"type":25,"children":293},[294],{"text":295,"type":29},"向购买页或客户经理确认并发上限、按流量还是按请求计费，以及失败请求是否计费，再用小样本核对账单口径。",{"type":31,"level":90,"children":297},[298],{"text":299,"type":29},"动态住宅代理 IP 和静态住宅代理 IP 怎么选？",{"type":25,"children":301},[302],{"text":303,"type":29},"能接受出口变化且需要轮换，优先测试动态住宅代理 IP；需要长期身份，优先测试静态住宅代理 IP。",{"type":31,"level":90,"children":305},[306],{"text":307,"type":29},"动态会话为什么不能保证精确时长？",{"type":25,"children":309},[310],{"text":311,"type":29},"会话可能受网络、资源回收和服务策略影响。查看产品支持请求切换还是粘性会话，并确认触发切换条件，不要按绝对在线时长理解。",{"type":31,"level":90,"children":313},[314],{"text":315,"type":29},"出现验证码就应该换成静态住宅代理 IP 吗？",{"type":25,"children":317},[318],{"text":319,"type":29},"不一定。先区分 IP、地区、设备环境、账号行为和平台规则，确认问题与出口变化有关后再切换。",{"type":25,"children":321},[322],{"text":185,"type":29},{"type":25,"children":324},[325],{"text":326,"type":29},"决策清单：能接受出口变化且任务是短会话采样，就先测动态资源；需要长期登录或同一身份，就先测静态资源；两者都先固定账号和设备做小样本验证，再按地区跳变、会话中断和验证码记录决定是否放量。",{"source":6,"id":328,"documentId":329,"translationKey":329,"locale":9,"slug":330,"path":331,"_path":331,"title":332,"description":333,"excerpt":333,"image":334,"publishedAt":335,"updatedAt":336,"author":17,"tags":337,"featured":19,"sortOrder":20,"readingTime":90,"bodyType":22,"bodyBlocks":338,"bodyHtml":190},2626,"xjjqi8xoqk9a83tbvj5nzi6r","sstap-proxy-ip-mode-guide","\u002Fblog\u002Fsstap-proxy-ip-mode-guide","SSTap 代理模式怎么选：全局、规则和游戏\u002F网页访问差异","SSTap 全局、规则和游戏模式怎么选，如何先确认代理 IP 和协议，再验证网页、游戏和 DNS 是否真正走代理。","\u002Fimages\u002Flogo-middle.gif","2026-09-10T06:35:19.885Z","2026-09-10T06:35:19.869Z",[],[339,343,347,351,355,359,363,367,371,375,379,383,387,391,395,399,403,407,411,415,419,423,427,431,435,438,442,446,450,454,458,462,466,470,474,477],{"type":25,"children":340},[341],{"text":342,"type":29},"SSTap 代理模式怎么选，取决于你要接管的是全部流量、指定网站，还是某个进程。不同版本的 SSTap 可能将相关功能称为“全局”“规则”“进程”或“游戏模式”，具体名称应以当前客户端界面为准。下面按流量接管范围说明选择方法。模式决定哪些流量经过代理 IP，不能替代代理 IP 类型和出口地区的选择。",{"type":25,"children":344},[345],{"text":346,"type":29},"如果只是验证一个网页，先把目标域名加入规则；如果要判断整机出口，再短时间切到全局；游戏则单独确认进程是否被接管。SSTap 代理模式本身不会修复协议、端口或账号限制。",{"type":31,"level":32,"children":348},[349],{"text":350,"type":29},"SSTap 全局、规则与进程接管应该按什么场景选择？",{"type":25,"children":352},[353],{"text":354,"type":29},"三种模式的核心差别是“哪些流量会经过代理 IP”，而不是代理 IP 本身变了。选择时先按目标任务分流，再检查规则是否真正命中。",{"type":37,"children":356},[357],{"text":358,"type":29},"| 模式 | 影响范围 | 适合场景 | 注意事项 |\n| --- | --- | --- | --- |\n| 规则模式 | 指定域名或应用 | 单个网站、指定应用 | 依赖域名也要命中规则 |\n| 全局模式 | 更多系统流量 | 临时验证整机出口 | 增加流量消耗并影响无关应用 |\n| 进程接管（部分版本称游戏模式） | 指定进程及相关连接 | 游戏或应用连接测试 | 网页正常不代表目标进程已经经过代理 IP |",{"type":31,"level":90,"children":360},[361],{"text":362,"type":29},"什么时候应该使用全局模式？",{"type":25,"children":364},[365],{"text":366,"type":29},"全局模式会让更多系统流量经过代理，适合临时验证整机出口、排查某个应用是否受本地网络影响，或需要多个网页统一使用同一代理 IP 的情况。它也会影响无关应用，可能增加延迟和流量消耗，因此不适合长期无差别开启。",{"type":31,"level":90,"children":368},[369],{"text":370,"type":29},"只让指定网站或应用走代理时，怎么用规则模式？",{"type":25,"children":372},[373],{"text":374,"type":29},"规则模式按域名、程序或规则列表分流，适合只让指定网站或应用使用代理 IP。使用前要确认目标域名及其依赖域名都命中规则；如果网页能打开但登录、图片或接口失败，往往是依赖域名没有一起匹配。",{"type":31,"level":90,"children":376},[377],{"text":378,"type":29},"游戏连接时，什么时候应该使用进程接管？",{"type":25,"children":380},[381],{"text":382,"type":29},"部分版本把针对游戏的配置称为“游戏模式”，也有版本直接使用进程规则。应把目标游戏程序加入规则，确认进程路径和相关域名，并按游戏实际支持的代理协议和端口要求测试；无法在当前版本找到该名称时，以规则\u002F进程入口为准。",{"type":31,"level":90,"children":384},[385],{"text":386,"type":29},"第一次配置 SSTap，不确定选哪种模式怎么办？",{"type":25,"children":388},[389],{"text":390,"type":29},"只测试一个网页或应用，先用规则模式；需要确认整机是否统一经过代理，再短时间使用全局模式；主要解决游戏连接，则使用进程规则（部分版本称游戏模式）并单独验证游戏进程。测试完成后关闭不必要的全局代理，避免把本地其他流量一并转发。",{"type":31,"level":32,"children":392},[393],{"text":394,"type":29},"在 SSTap 中填写代理前，要先核对哪些信息？",{"type":25,"children":396},[397],{"text":398,"type":29},"先从代理服务商获取协议、主机、端口和认证信息。HTTP、HTTPS 或 SOCKS5 必须与服务商提供的格式一致，主机和端口不要混填；使用规则模式时还要确认规则文件已加载，使用进程规则（部分版本称游戏模式）时要确认目标进程路径正确。认证信息应以服务商提供的接入格式为准，不能把某一种认证方式当作所有 SSTap 配置的必填项。",{"type":31,"level":32,"children":400},[401],{"text":402,"type":29},"怎么确认网页和游戏真的走了代理 IP？",{"type":25,"children":404},[405],{"text":406,"type":29},"先在网页中记录出口 IP、地区和 DNS，再打开目标游戏或应用进行连接测试。网页正常、游戏失败时，优先检查游戏进程规则、协议兼容性和目标端口；网页和游戏都失败时，再回到主机、端口、认证和本地网络排查。每次只修改一个变量，并记录测试时间和错误提示，才方便判断是模式问题还是代理 IP 本身的问题。",{"type":31,"level":90,"children":408},[409],{"text":410,"type":29},"脱敏记录应该包含哪些字段？",{"type":25,"children":412},[413],{"text":414,"type":29},"下面是一份记录格式示例，版本、时间、出口 IP 和状态码均为演示值；`203.0.113.0\u002F24`、`198.51.100.0\u002F24` 属于文档保留地址，不能当作真实代理结果。发布前应替换为实际测试中脱敏后的值。",{"type":25,"children":416},[417],{"text":418,"type":29},"**测试条件（示例）**：SSTap 1.1.0（示例版本，需按当前客户端核对）、Windows 11 23H2、同一 SOCKS5 账号、同一网页和游戏服务器、测试时间 2026-09-10 14:00–14:20（UTC+8）。",{"type":37,"children":420},[421],{"text":422,"type":29},"| 模式 | 流量 | 出口 IP（脱敏示例） | DNS 结果 | 状态\u002F错误提示（示例） |\n| --- | --- | --- | --- | --- |\n| 规则模式 | 网页 | `203.0.113.42` | `192.0.2.53` | HTTP 200，页面地区为代理国家 |\n| 规则模式 | 游戏进程 | 本地出口 | 本地 DNS | `connection timeout`，进程未命中规则 |\n| 全局模式 | 网页 | `198.51.100.17` | `192.0.2.54` | HTTP 200，网页与 DNS 均经代理 |\n| 全局模式 | 游戏进程 | `198.51.100.17` | `192.0.2.54` | 连接成功；记录实际延迟和服务器返回 |\n| 进程接管 | 网页 | 本地出口 | 本地 DNS | HTTP 200，网页未纳入进程规则 |\n| 进程接管 | 游戏进程 | `203.0.113.42` | `192.0.2.53` | 记录连接结果、端口和错误提示 |",{"type":25,"children":424},[425],{"text":426,"type":29},"记录时应同时保存时间戳、规则命中日志、出口 IP 查询结果和截图。示例中的“成功”或“超时”只说明如何填写，不能据此推断某个 SSTap 版本、协议或代理服务的真实表现。",{"type":31,"level":32,"children":428},[429],{"text":430,"type":29},"SSTap 模式选对后，什么时候还要评估静态住宅代理 IP？",{"type":25,"children":432},[433],{"text":434,"type":29},"短时网页测试、多地区采样或公开页面观察，可先测试动态住宅代理 IP；需要长期保持同一出口身份的登录或后台场景，再评估静态住宅代理 IP。模式选择解决的是流量范围，动态或静态解决的是出口变化方式，两者应分开判断。",{"type":31,"level":32,"children":436},[437],{"text":149,"type":29},{"type":31,"level":90,"children":439},[440],{"text":441,"type":29},"只想让一个网页走代理 IP，应选什么模式？",{"type":25,"children":443},[444],{"text":445,"type":29},"优先使用规则模式，并把目标域名及其登录、接口和静态资源域名一并纳入规则。",{"type":31,"level":90,"children":447},[448],{"text":449,"type":29},"全局模式下网页能打开但游戏不能连接怎么办？",{"type":25,"children":451},[452],{"text":453,"type":29},"检查游戏进程是否被 SSTap 接管、游戏要求的代理协议和端口是否匹配，再用同一代理 IP 做单独测试。",{"type":31,"level":90,"children":455},[456],{"text":457,"type":29},"如何确认没有 DNS 泄漏？",{"type":25,"children":459},[460],{"text":461,"type":29},"分别在网页和应用环境检查 DNS 解析结果，并结合出口 IP、地区和 WebRTC 检测。发现本地 DNS 或真实 IP 时，先检查 SSTap 接管范围和系统网络设置。",{"type":31,"level":90,"children":463},[464],{"text":465,"type":29},"SSTap 适合长期登录业务吗？",{"type":25,"children":467},[468],{"text":469,"type":29},"要看业务是否要求长期稳定的出口身份。长期登录通常应优先评估静态住宅代理 IP，并保持代理、浏览器环境、语言和时区的一致性。",{"type":25,"children":471},[472],{"text":473,"type":29},"可参考[Windows SSTap 代理设置](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002Fproxy-Settings\u002FWindows-Setting\u002Fwindows-sstap)以及  [SSTap-Rule 规则示例](https:\u002F\u002Fgithub.com\u002FFQrabbit\u002FSSTap-Rule) 。第三方规则仓库不代表官方版本，导入前请核对当前客户端入口。",{"type":25,"children":475},[476],{"text":185,"type":29},{"type":25,"children":478},[479],{"text":480,"type":29},"先按流量范围选择 SSTap 模式，再验证实际出口 IP、DNS 和网页或游戏连接。模式选对后，仍要根据业务是否需要长期稳定身份，评估动态住宅代理 IP 或静态住宅代理 IP。",{"source":6,"id":482,"documentId":483,"translationKey":483,"locale":9,"slug":484,"path":485,"_path":485,"title":486,"description":487,"excerpt":487,"image":488,"publishedAt":489,"updatedAt":490,"author":17,"tags":491,"featured":19,"sortOrder":20,"readingTime":32,"bodyType":22,"bodyBlocks":492,"bodyHtml":190},2625,"ja6v6kipzvga8o0j6j7aymd4","hubstudio-proxy-check-failed","\u002Fblog\u002Fhubstudio-proxy-check-failed","Hubstudio 指纹浏览器代理检测失败怎么办？","Hubstudio 指纹浏览器代理检测失败时，先按网络、协议和认证方式排查，再确认出口与地区。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_hubstudio_cover_7dc1032b80.webp","2026-09-10T06:35:04.112Z","2026-09-10T06:35:04.099Z",[],[493,497,501,505,509,513,517,521,525,529,533,537,541,545,549,553,557,560,564,568,572,576,580,584,588,592,596,600,603],{"type":25,"children":494},[495],{"text":496,"type":29},"Hubstudio 指纹浏览器检测代理 IP 失败时，先确认海外网络环境或加速通道，再检查套餐是否到期、流量是否用尽和资源状态，最后核对代理参数、Hubstudio 配置和认证方式。不要在未确认错误类型前反复更换代理 IP。",{"type":31,"level":32,"children":498},[499],{"text":500,"type":29},"Hubstudio 代理检测失败时，先区分超时、连接拒绝和认证失败",{"type":25,"children":502},[503],{"text":504,"type":29},"超时多与网络或端口有关，连接拒绝常见于协议或端口错误，认证失败则检查账号密码和认证方式。保留错误提示，便于后续与服务商核对。",{"type":37,"children":506},[507],{"text":508,"type":29},"| 错误类型 | 常见原因 | 优先检查 |\n| --- | --- | --- |\n| 超时 | 本机网络、端口不可达、资源失效 | 网络、主机、端口 |\n| 连接拒绝 | 协议或端口不匹配 | HTTP\u002FHTTPS\u002FSOCKS5 与对应端口 |\n| 认证失败 | 账号密码错误或认证方式不匹配 | 认证方式和凭证 |\n| 检测成功但出口异常 | 环境绑定或 DNS\u002FWebRTC 泄漏 | 出口 IP、地区、DNS\u002FWebRTC |",{"type":31,"level":32,"children":510},[511],{"text":512,"type":29},"如何核对 Hubstudio 的代理配置字段？",{"type":25,"children":514},[515],{"text":516,"type":29},"常见入口是“新建\u002F编辑环境 → 代理设置”。可以先按下面的字段映射逐项填写，再保存并启用环境：",{"type":31,"level":90,"children":518},[519],{"text":520,"type":29},"主机和端口",{"type":25,"children":522},[523],{"text":524,"type":29},"“主机”填写服务商提供的域名或 IP，例如 `proxy.example.com`；“端口”填写对应数字端口，例如 `10000`。不要把带协议前缀的完整 URL 粘进主机框，也不要把端口写进账号字段。",{"type":31,"level":90,"children":526},[527],{"text":528,"type":29},"协议",{"type":25,"children":530},[531],{"text":532,"type":29},"在“协议\u002F代理类型”中选择服务商实际提供的 HTTP、HTTPS 或 SOCKS5。示例：服务商给出 `SOCKS5 proxy.example.com:10000`，Hubstudio 就选择 SOCKS5、主机填 `proxy.example.com`、端口填 `10000`；协议选错时常见表现是连接被拒绝或握手失败。",{"type":31,"level":90,"children":534},[535],{"text":536,"type":29},"账号和密码",{"type":25,"children":538},[539],{"text":540,"type":29},"启用账号密码认证时，在“账号\u002F用户名”填 `demo_user`、在“密码”填服务商生成的密码，并确认没有复制换行或空格。不要在未要求时额外填写白名单、公网 IP 或二次认证字段。",{"type":25,"children":542},[543],{"text":544,"type":29},"保存后先用 IP 检测页验证出口国家\u002F城市、DNS 和 WebRTC，再判断环境是否真正可用。",{"type":31,"level":32,"children":546},[547],{"text":548,"type":29},"Hubstudio 代理检测失败时，如何按网络、代理参数和认证逐步验证？",{"type":25,"children":550},[551],{"text":552,"type":29},"先在本机确认海外网络或加速通道，再用同一组信息测试代理连通；随后在 Hubstudio 中保存并启用配置，重新检测，最后打开 IP 检测页确认出口和地区。超时继续查网络\u002F端口，连接拒绝查协议，`407 Proxy Authentication Required` 优先查账号、密码和认证方式。只有在服务商明确为“动态住宅代理 IP + API 提取”配置了来源白名单时，才核对当前公网出口是否在白名单内；普通账号密码接入不要默认要求白名单。出口异常再查环境绑定与 DNS\u002FWebRTC。",{"type":25,"children":554},[555],{"text":556,"type":29},"例如，Hubstudio 返回 `407 Proxy Authentication Required` 时，先用同一账号在服务商提供的接入方式重试：若仍为 407，通常是凭证失效、认证方式选错或账号未开通；若服务商确认该 API 提取方案启用了来源白名单，再补查公网出口是否匹配。若返回 `connection refused`，则优先把协议和端口与订单信息逐字对照，而不是反复改密码。",{"type":31,"level":32,"children":558},[559],{"text":149,"type":29},{"type":31,"level":90,"children":561},[562],{"text":563,"type":29},"主机端口都正确但仍失败怎么办？",{"type":25,"children":565},[566],{"text":567,"type":29},"继续核对协议、账号密码、认证方式和复制内容中的空格。只有服务商明确要求来源白名单（例如动态住宅代理 IP 的 API 提取场景）时，才确认当前公网出口是否已加入；账号密码模式不应默认配置白名单。",{"type":31,"level":90,"children":569},[570],{"text":571,"type":29},"不同认证方式可以同时使用吗？",{"type":25,"children":573},[574],{"text":575,"type":29},"通常应按服务商指定的单一认证方式配置，不要自行混用。",{"type":31,"level":90,"children":577},[578],{"text":579,"type":29},"检测通过后还要检查什么？",{"type":25,"children":581},[582],{"text":583,"type":29},"检查出口 IP、地区、DNS\u002FWebRTC 和目标网站访问；检测通过只代表代理连通。",{"type":31,"level":90,"children":585},[586],{"text":587,"type":29},"Hubstudio 中应选择动态还是静态住宅代理 IP？",{"type":25,"children":589},[590],{"text":591,"type":29},"短时、多地区任务可测试动态住宅代理 IP；长期登录更适合评估静态住宅代理 IP。",{"type":25,"children":593},[594],{"text":595,"type":29},"可参考[Hubstudio 代理设置教程](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002Fproxy-Settings\u002FFingerprint-Browser-Setting\u002FHubstudio)。",{"type":25,"children":597},[598],{"text":599,"type":29},"可同时参阅 [Hubstudio 官方帮助中心](https:\u002F\u002Fsupport-orig.hubstudio.cn\u002F)。如果当前版本没有完全相同的字段名称，以官方模板和客户端当前界面为准。",{"type":25,"children":601},[602],{"text":185,"type":29},{"type":25,"children":604},[605],{"text":606,"type":29},"定位并修复网络、代理参数或认证问题后，再验证出口 IP、地区、DNS\u002FWebRTC 和目标网站结果，不能只凭客户端的检测提示判断代理已经可用。",[608],{"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":609,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":610,"bodyHtml":190},[],[611,614,617,620,623,626,629,632,635,638,641,644,647,650,653,656,659,662,665,668,671,674,677,680,683,686,689,692,695,698,701,704,707,710,713,716,719,722,725,728],{"type":25,"children":612},[613],{"text":28,"type":29},{"type":31,"level":32,"children":615},[616],{"text":35,"type":29},{"type":37,"children":618},[619],{"text":40,"type":29},{"type":25,"children":621},[622],{"text":44,"type":29},{"type":31,"level":32,"children":624},[625],{"text":48,"type":29},{"type":25,"children":627},[628],{"text":52,"type":29},{"type":25,"children":630},[631],{"text":56,"type":29},{"type":25,"children":633},[634],{"text":60,"type":29},{"type":25,"children":636},[637],{"text":64,"type":29},{"type":25,"children":639},[640],{"text":68,"type":29},{"type":25,"children":642},[643],{"text":72,"type":29},{"type":25,"children":645},[646],{"text":76,"type":29},{"type":25,"children":648},[649],{"text":80,"type":29},{"type":25,"children":651},[652],{"text":84,"type":29},{"type":25,"children":654},[655],{"text":88,"type":29},{"type":31,"level":90,"children":657},[658],{"text":93,"type":29},{"type":25,"children":660},[661],{"text":97,"type":29},{"type":31,"level":32,"children":663},[664],{"text":101,"type":29},{"type":25,"children":666},[667],{"text":105,"type":29},{"type":25,"children":669},[670],{"text":109,"type":29},{"type":31,"level":32,"children":672},[673],{"text":113,"type":29},{"type":37,"children":675},[676],{"text":117,"type":29},{"type":25,"children":678},[679],{"text":121,"type":29},{"type":31,"level":90,"children":681},[682],{"text":125,"type":29},{"type":25,"children":684},[685],{"text":129,"type":29},{"type":31,"level":32,"children":687},[688],{"text":133,"type":29},{"type":25,"children":690},[691],{"text":137,"type":29},{"type":31,"level":32,"children":693},[694],{"text":141,"type":29},{"type":25,"children":696},[697],{"text":145,"type":29},{"type":31,"level":32,"children":699},[700],{"text":149,"type":29},{"type":31,"level":90,"children":702},[703],{"text":153,"type":29},{"type":25,"children":705},[706],{"text":157,"type":29},{"type":31,"level":90,"children":708},[709],{"text":161,"type":29},{"type":25,"children":711},[712],{"text":165,"type":29},{"type":31,"level":90,"children":714},[715],{"text":169,"type":29},{"type":25,"children":717},[718],{"text":173,"type":29},{"type":31,"level":90,"children":720},[721],{"text":177,"type":29},{"type":25,"children":723},[724],{"text":181,"type":29},{"type":25,"children":726},[727],{"text":185,"type":29},{"type":25,"children":729},[730],{"text":189,"type":29},null,[],[]]