[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-strapi-article:zh:crawler-429-too-many-requests-proxy":3,"blog-article:\u002Fblog\u002Fcrawler-429-too-many-requests-proxy":797,"blog-related:\u002Fblog\u002Fcrawler-429-too-many-requests-proxy":798,"blog-translations:\u002Fblog\u002Fcrawler-429-too-many-requests-proxy":799},{"available":4,"article":5,"relatedArticles":231,"translations":644},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":230},"strapi",2484,"e8solm25h3e0r6jbsq1peuf9","zh","crawler-429-too-many-requests-proxy","\u002Fblog\u002Fcrawler-429-too-many-requests-proxy","爬虫 429 Too Many Requests：判断频率还是代理 IP 池","爬虫遇到 429 Too Many Requests 时，先固定账号和代理出口做降频实验，再以低频基线更换代理 IP，区分频率、配额和代理 IP 池问题。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_429_too_many_requests_cover_978d5b6a35.webp","2026-09-03T03:46:20.903Z","2026-09-03T03:46:20.890Z","Global Proxies Team",[],false,0,3,"blocks",[24,30,36,40,73,77,81,85,89,93,97,102,106,110,114,118,122,126,130,134,138,142,146,150,154,158,162,166,170,174,178,182,186,190,194,198,202,206,210,214,218,222,226],{"type":25,"children":26},"paragraph",[27],{"text":28,"type":29},"遇到 429，先固定账号、URL、Header、Cookie 和代理 IP，只降低并发、延长请求间隔并遵守 `Retry-After`；如果 429 稳定下降，优先处理频率或账号\u002FAPI 配额。只有在低频基线下，错误仍稳定集中于少数出口，才继续检查代理 IP 池质量、地区识别或出口复用。","text",{"type":31,"level":32,"children":33},"heading",2,[34],{"text":35,"type":29},"先保存 429 的完整证据",{"type":25,"children":37},[38],{"text":39,"type":29},"429 表示请求过多，但限制维度可能是账号、API 密钥、接口、IP、设备或多项组合。保存：",{"type":41,"format":42,"children":43},"list","unordered",[44,49,53,57,61,65,69],{"type":45,"children":46},"list-item",[47],{"text":48,"type":29},"状态码与响应体摘要；",{"type":45,"children":50},[51],{"text":52,"type":29},"`Retry-After` 和其他限流响应头；",{"type":45,"children":54},[55],{"text":56,"type":29},"账号\u002FAPI 密钥的脱敏标识；",{"type":45,"children":58},[59],{"text":60,"type":29},"URL、接口、请求方法和参数摘要；",{"type":45,"children":62},[63],{"text":64,"type":29},"并发数、请求间隔、时间窗口；",{"type":45,"children":66},[67],{"text":68,"type":29},"代理出口 IP、国家\u002F城市；",{"type":45,"children":70},[71],{"text":72,"type":29},"请求总数、成功数、429 数量和耗时。",{"type":25,"children":74},[75],{"text":76,"type":29},"如果响应中包含 `X-RateLimit-Limit`、`X-RateLimit-Remaining` 或 `X-RateLimit-Reset` 等字段，也应一并保存；这些字段有助于判断限制是按账号、接口还是时间窗口计算。",{"type":25,"children":78},[79],{"text":80,"type":29},"HTTP 429 与 `Retry-After` 的语义可参考 [RFC 6585 第 4 节](https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc6585#section-4)。服务端没有义务说明采用哪一种计数维度，因此需要对照实验。",{"type":25,"children":82},[83],{"text":84,"type":29},"若同时出现 403 或验证码，可结合[爬虫 403\u002F429\u002F验证码排查](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fcrawler-403-429-captcha-proxy-ip-troubleshooting)分开记录，避免把不同错误合并成 429。",{"type":31,"level":32,"children":86},[87],{"text":88,"type":29},"阶段 A：固定代理 IP，逐步降低请求频率",{"type":25,"children":90},[91],{"text":92,"type":29},"保持账号、代理 IP、URL、Header、Cookie 和请求参数不变，按阶梯降低并发和请求频率。每一档使用相同样本量与观察时间，不要在中途换出口。",{"type":25,"children":94},[95],{"text":96,"type":29},"示例记录表：",{"type":98,"children":99},"code",[100],{"text":101,"type":29},"| 组别 | 并发 | 请求间隔 | 请求数 | 429 数 | 成功数 | 结论 |\n| --- | ---: | ---: | ---: | ---: | ---: | --- |\n| A1 | 当前值 | 当前值 | 同样本量 | 记录 | 记录 | 基线 |\n| A2 | 降低一档 | 延长一档 | 同样本量 | 记录 | 记录 | 与 A1 比较 |\n| A3 | 再降低一档 | 再延长一档 | 同样本量 | 记录 | 记录 | 验证趋势是否重复 |",{"type":25,"children":103},[104],{"text":105,"type":29},"若降频后 429 在连续时间窗口内都明显下降，而出口未变，主要矛盾更可能是频率、账号或接口配额。若响应带 `Retry-After`，等待时间应优先遵守服务端提示。",{"type":31,"level":32,"children":107},[108],{"text":109,"type":29},"阶段 B：保持低频基线，仅更换代理 IP",{"type":25,"children":111},[112],{"text":113,"type":29},"保持阶段 A 得到的低频基线，固定账号、URL、Header、Cookie、参数、并发和间隔，只替换同地区代理 IP。",{"type":98,"children":115},[116],{"text":117,"type":29},"| 结果模式 | 更可能的原因 | 下一步 |\n| --- | --- | --- |\n| 所有出口在同一时段都 429 | 账号、接口或全站限流 | 暂停并检查配额\u002F服务端提示 |\n| 同一账号跨多个出口都 429 | 账号或 API 密钥配额 | 换 IP 通常无效 |\n| 少数出口跨账号重复 429 | 出口复用或质量问题 | 隔离出口并扩大同地区样本 |\n| 更换出口短暂恢复，随后再次 429 | 频率策略仍不合适 | 回到阶段 A，降低总体负载 |\n| 429 响应实际是验证页面 | 状态分类错误 | 单独记录验证码\u002F挑战，不当作普通 429 |",{"type":31,"level":32,"children":119},[120],{"text":121,"type":29},"429 的重试与停止规则",{"type":31,"level":21,"children":123},[124],{"text":125,"type":29},"429 响应的基础退避代码",{"type":25,"children":127},[128],{"text":129,"type":29},"```python\nimport random\nimport time",{"type":25,"children":131},[132],{"text":133,"type":29},"def wait_before_retry(response, attempt):\nretry_after = response.headers.get(\"Retry-After\")\nif retry_after and retry_after.isdigit():\nwait = float(retry_after)\nelse:\nwait = min(2 ** attempt, 60)\ntime.sleep(wait + random.uniform(0, 0.5))\n```",{"type":31,"level":21,"children":135},[136],{"text":137,"type":29},"生产环境如何设置重试上限与共享限流",{"type":25,"children":139},[140],{"text":141,"type":29},"生产实现还应支持 HTTP 日期格式的 `Retry-After`，并设置：",{"type":25,"children":143},[144],{"text":145,"type":29},"1. 最大重试次数；\n2. 单任务总时限；\n3. 同账号或接口的共享限流器；\n4. 连续 429 后的暂停和报警；\n5. 重试队列的容量上限。",{"type":25,"children":147},[148],{"text":149,"type":29},"不要让多个工作进程各自判断后立即重试，否则总体流量仍可能超过限制。账号或 API 密钥维度的限流，应在所有工作进程之间共享状态。",{"type":31,"level":32,"children":151},[152],{"text":153,"type":29},"把 403、429、验证码和空结果分开",{"type":98,"children":155},[156],{"text":157,"type":29},"| 结果 | 主要含义 | 是否按 429 重试 |\n| --- | --- | --- |\n| 429 | 请求过多或配额限制 | 按服务端提示有限重试 |\n| 403 | 权限、账号、地区或访问策略 | 不直接套用 429 退避 |\n| 验证码\u002F挑战页 | 环境、会话或请求行为变化 | 暂停并单独诊断 |\n| HTTP 200 但空结果 | 业务无数据或解析问题 | 不应计为请求成功或 429 |\n| 5xx | 临时服务端错误 | 可有限重试，单独统计 |",{"type":25,"children":159},[160],{"text":161,"type":29},"把所有失败合并为一个错误率，会导致错误扩容代理 IP 池或错误提高重试次数。",{"type":25,"children":163},[164],{"text":165,"type":29},"建议把每个实验窗口固定为相同请求数，例如每组 100 次，并记录窗口开始和结束时间。只有在多个窗口都出现同样趋势时，才把“降频有效”或“少数出口异常”当作可复用结论。",{"type":31,"level":32,"children":167},[168],{"text":169,"type":29},"评估代理 IP 池容量的方法",{"type":25,"children":171},[172],{"text":173,"type":29},"评估代理 IP 池容量时，应使用单个代理 IP 的安全承载量、基线成功率、冷却占比和重试放大，而不是用“总请求量÷IP 数”直接估算。",{"type":31,"level":32,"children":175},[176],{"text":177,"type":29},"用脱敏复测数据区分频率限制与代理池因素",{"type":25,"children":179},[180],{"text":181,"type":29},"以下为脱敏记录示例（接口、账号和 IP 已隐去，数字为示例、非 SLA）：同一账号与单一出口、并发 5 时 50 次请求出现 429 12 次；降至并发 1、间隔 8 秒后为 2 次；保持低频改用 5 个出口仍为 2 次。该对照更支持频率因素，不能据此断言代理池无问题。",{"type":25,"children":183},[184],{"text":185,"type":29},"429 状态码与 `Retry-After` 可核对 [RFC 6585](https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc6585.html)，HTTP 语义可核对 [RFC 9110](https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc9110.html)；并发、间隔和样本量属于经验设计。",{"type":31,"level":32,"children":187},[188],{"text":189,"type":29},"FAQ",{"type":31,"level":21,"children":191},[192],{"text":193,"type":29},"429 和 403 是同一种问题吗？",{"type":25,"children":195},[196],{"text":197,"type":29},"不是。429 主要表示请求过多或配额限制；403 还可能涉及权限、账号、地区或访问策略。",{"type":31,"level":21,"children":199},[200],{"text":201,"type":29},"没有 Retry-After 怎么办？",{"type":25,"children":203},[204],{"text":205,"type":29},"采用指数退避和随机抖动，并设置最大次数与任务总时限。仍持续 429 时暂停任务。",{"type":31,"level":21,"children":207},[208],{"text":209,"type":29},"账号配额会导致 429 吗？",{"type":25,"children":211},[212],{"text":213,"type":29},"会。若限制绑定账号或 API 密钥，更换代理 IP 通常不会解除配额限制。",{"type":31,"level":21,"children":215},[216],{"text":217,"type":29},"单次 429 能判断代理 IP 池质量吗？",{"type":25,"children":219},[220],{"text":221,"type":29},"不能。至少要完成降频实验，并在低频基线下比较多个同地区出口和时间窗口。",{"type":25,"children":223},[224],{"text":225,"type":29},"---",{"type":25,"children":227},[228],{"text":229,"type":29},"确认问题确实集中在出口后，再按任务规模评估[动态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fdynamic-residential)。","",[232,364,518],{"source":6,"id":233,"documentId":234,"translationKey":234,"locale":9,"slug":235,"path":236,"_path":236,"title":237,"description":238,"excerpt":238,"image":239,"publishedAt":240,"updatedAt":241,"author":17,"tags":242,"featured":19,"sortOrder":20,"readingTime":32,"bodyType":22,"bodyBlocks":243,"bodyHtml":230},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",[],[244,248,252,256,274,278,282,286,290,294,298,302,306,310,314,318,322,325,329,333,337,341,345,349,353,357,360],{"type":25,"children":245},[246],{"text":247,"type":29},"动态住宅代理 IP 更适合短会话、多地区轮换、公开采样和批量测试；静态住宅代理 IP 更适合长期登录、店铺后台和广告账户。选择时先看业务能否接受出口变化，再比较地区、会话时长、协议、认证方式和成本。",{"type":31,"level":32,"children":249},[250],{"text":251,"type":29},"哪些业务适合动态住宅代理 IP",{"type":25,"children":253},[254],{"text":255,"type":29},"价格监测、广告展示核对、搜索结果观察、公开页面采样和多地区测试，通常更重视 IP 数量与轮换效率。动态住宅代理 IP 可按请求或粘性会话切换，适合彼此独立、无需保持同一出口的短会话。",{"type":41,"format":42,"children":257},[258,262,266,270],{"type":45,"children":259},[260],{"text":261,"type":29},"价格监测：每次请求可以使用不同出口，便于抽样多个地区和运营商，减少为保持单一身份而付出的会话成本。",{"type":45,"children":263},[264],{"text":265,"type":29},"广告展示核对：轮换出口能观察不同本地网络视角，适合发现广告素材、落地页或地区定向的变化；但预算、频控和 Cookie 仍要固定。",{"type":45,"children":267},[268],{"text":269,"type":29},"搜索结果观察：同一关键词在多个出口上采样，便于区分地区差异与单个出口的偶然结果，不需要让所有请求长期绑定一个 IP。",{"type":45,"children":271},[272],{"text":273,"type":29},"公开页面采样和多地区测试：请求彼此独立、失败后可换出口重试，轮换效率通常比长期保持同一出口更重要。",{"type":31,"level":32,"children":275},[276],{"text":277,"type":29},"哪些长期任务不适合使用动态住宅代理 IP？",{"type":25,"children":279},[280],{"text":281,"type":29},"长期登录、店铺后台、广告账户和支付后台更依赖稳定出口身份，通常优先测试静态住宅代理 IP，并保持设备指纹、语言、时区和操作节奏一致。静态住宅代理 IP 也不代表平台一定放行，仍需结合账号和环境判断。",{"type":31,"level":32,"children":283},[284],{"text":285,"type":29},"动态住宅代理 IP 和静态住宅代理 IP 怎么选",{"type":98,"children":287},[288],{"text":289,"type":29},"| 判断项 | 动态住宅代理 IP | 静态住宅代理 IP |\n| --- | --- | --- |\n| 主要任务 | 短时采样、多地区轮换 | 长期登录、稳定身份 |\n| 出口变化 | 可按请求或会话切换 | 在服务有效且配置不变时保持同一出口；异常更换或服务状态变化仍需核对 |\n| 重点确认 | 切换规则、会话时长、流量计费 | 独享性、持续可用性、周期计费 |",{"type":25,"children":291},[292],{"text":293,"type":29},"如果同时进行数据采样和账号操作，建议分别使用两套环境，避免出口变化互相干扰。",{"type":31,"level":32,"children":295},[296],{"text":297,"type":29},"购买动态或静态住宅代理 IP 前，要确认哪些产品参数？",{"type":25,"children":299},[300],{"text":301,"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":303},[304],{"text":305,"type":29},"动态住宅和静态住宅代理 IP 上线前，如何做对照验证？",{"type":25,"children":307},[308],{"text":309,"type":29},"固定账号、设备和目标网站，只改变代理 IP 类型；例如对短时采样记录每 100 次请求的地区跳变和验证码次数，对长期登录记录 24 小时内会话中断次数，再决定是否放量。",{"type":25,"children":311},[312],{"text":313,"type":29},"为了让记录可比较，可以先用下表的“示意区间”设计验收表，再替换成自己的真实观测值。数字仅演示记录格式，不是行业基准、供应商承诺或本文实测结论：",{"type":98,"children":315},[316],{"text":317,"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":319},[320],{"text":321,"type":29},"正式测试时应把每次出口、时间戳、状态码、地区库结果和截图一起保存；如果结果落在区间外，先复核目标站策略、Cookie、DNS\u002FWebRTC 和并发条件，再决定是否更换代理类型。",{"type":31,"level":32,"children":323},[324],{"text":189,"type":29},{"type":31,"level":21,"children":326},[327],{"text":328,"type":29},"并发和计费如何确认？",{"type":25,"children":330},[331],{"text":332,"type":29},"向购买页或客户经理确认并发上限、按流量还是按请求计费，以及失败请求是否计费，再用小样本核对账单口径。",{"type":31,"level":21,"children":334},[335],{"text":336,"type":29},"动态住宅代理 IP 和静态住宅代理 IP 怎么选？",{"type":25,"children":338},[339],{"text":340,"type":29},"能接受出口变化且需要轮换，优先测试动态住宅代理 IP；需要长期身份，优先测试静态住宅代理 IP。",{"type":31,"level":21,"children":342},[343],{"text":344,"type":29},"动态会话为什么不能保证精确时长？",{"type":25,"children":346},[347],{"text":348,"type":29},"会话可能受网络、资源回收和服务策略影响。查看产品支持请求切换还是粘性会话，并确认触发切换条件，不要按绝对在线时长理解。",{"type":31,"level":21,"children":350},[351],{"text":352,"type":29},"出现验证码就应该换成静态住宅代理 IP 吗？",{"type":25,"children":354},[355],{"text":356,"type":29},"不一定。先区分 IP、地区、设备环境、账号行为和平台规则，确认问题与出口变化有关后再切换。",{"type":25,"children":358},[359],{"text":225,"type":29},{"type":25,"children":361},[362],{"text":363,"type":29},"决策清单：能接受出口变化且任务是短会话采样，就先测动态资源；需要长期登录或同一身份，就先测静态资源；两者都先固定账号和设备做小样本验证，再按地区跳变、会话中断和验证码记录决定是否放量。",{"source":6,"id":365,"documentId":366,"translationKey":366,"locale":9,"slug":367,"path":368,"_path":368,"title":369,"description":370,"excerpt":370,"image":371,"publishedAt":372,"updatedAt":373,"author":17,"tags":374,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":375,"bodyHtml":230},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",[],[376,380,384,388,392,396,400,404,408,412,416,420,424,428,432,436,440,444,448,452,456,460,464,468,472,475,479,483,487,491,495,499,503,507,511,514],{"type":25,"children":377},[378],{"text":379,"type":29},"SSTap 代理模式怎么选，取决于你要接管的是全部流量、指定网站，还是某个进程。不同版本的 SSTap 可能将相关功能称为“全局”“规则”“进程”或“游戏模式”，具体名称应以当前客户端界面为准。下面按流量接管范围说明选择方法。模式决定哪些流量经过代理 IP，不能替代代理 IP 类型和出口地区的选择。",{"type":25,"children":381},[382],{"text":383,"type":29},"如果只是验证一个网页，先把目标域名加入规则；如果要判断整机出口，再短时间切到全局；游戏则单独确认进程是否被接管。SSTap 代理模式本身不会修复协议、端口或账号限制。",{"type":31,"level":32,"children":385},[386],{"text":387,"type":29},"SSTap 全局、规则与进程接管应该按什么场景选择？",{"type":25,"children":389},[390],{"text":391,"type":29},"三种模式的核心差别是“哪些流量会经过代理 IP”，而不是代理 IP 本身变了。选择时先按目标任务分流，再检查规则是否真正命中。",{"type":98,"children":393},[394],{"text":395,"type":29},"| 模式 | 影响范围 | 适合场景 | 注意事项 |\n| --- | --- | --- | --- |\n| 规则模式 | 指定域名或应用 | 单个网站、指定应用 | 依赖域名也要命中规则 |\n| 全局模式 | 更多系统流量 | 临时验证整机出口 | 增加流量消耗并影响无关应用 |\n| 进程接管（部分版本称游戏模式） | 指定进程及相关连接 | 游戏或应用连接测试 | 网页正常不代表目标进程已经经过代理 IP |",{"type":31,"level":21,"children":397},[398],{"text":399,"type":29},"什么时候应该使用全局模式？",{"type":25,"children":401},[402],{"text":403,"type":29},"全局模式会让更多系统流量经过代理，适合临时验证整机出口、排查某个应用是否受本地网络影响，或需要多个网页统一使用同一代理 IP 的情况。它也会影响无关应用，可能增加延迟和流量消耗，因此不适合长期无差别开启。",{"type":31,"level":21,"children":405},[406],{"text":407,"type":29},"只让指定网站或应用走代理时，怎么用规则模式？",{"type":25,"children":409},[410],{"text":411,"type":29},"规则模式按域名、程序或规则列表分流，适合只让指定网站或应用使用代理 IP。使用前要确认目标域名及其依赖域名都命中规则；如果网页能打开但登录、图片或接口失败，往往是依赖域名没有一起匹配。",{"type":31,"level":21,"children":413},[414],{"text":415,"type":29},"游戏连接时，什么时候应该使用进程接管？",{"type":25,"children":417},[418],{"text":419,"type":29},"部分版本把针对游戏的配置称为“游戏模式”，也有版本直接使用进程规则。应把目标游戏程序加入规则，确认进程路径和相关域名，并按游戏实际支持的代理协议和端口要求测试；无法在当前版本找到该名称时，以规则\u002F进程入口为准。",{"type":31,"level":21,"children":421},[422],{"text":423,"type":29},"第一次配置 SSTap，不确定选哪种模式怎么办？",{"type":25,"children":425},[426],{"text":427,"type":29},"只测试一个网页或应用，先用规则模式；需要确认整机是否统一经过代理，再短时间使用全局模式；主要解决游戏连接，则使用进程规则（部分版本称游戏模式）并单独验证游戏进程。测试完成后关闭不必要的全局代理，避免把本地其他流量一并转发。",{"type":31,"level":32,"children":429},[430],{"text":431,"type":29},"在 SSTap 中填写代理前，要先核对哪些信息？",{"type":25,"children":433},[434],{"text":435,"type":29},"先从代理服务商获取协议、主机、端口和认证信息。HTTP、HTTPS 或 SOCKS5 必须与服务商提供的格式一致，主机和端口不要混填；使用规则模式时还要确认规则文件已加载，使用进程规则（部分版本称游戏模式）时要确认目标进程路径正确。认证信息应以服务商提供的接入格式为准，不能把某一种认证方式当作所有 SSTap 配置的必填项。",{"type":31,"level":32,"children":437},[438],{"text":439,"type":29},"怎么确认网页和游戏真的走了代理 IP？",{"type":25,"children":441},[442],{"text":443,"type":29},"先在网页中记录出口 IP、地区和 DNS，再打开目标游戏或应用进行连接测试。网页正常、游戏失败时，优先检查游戏进程规则、协议兼容性和目标端口；网页和游戏都失败时，再回到主机、端口、认证和本地网络排查。每次只修改一个变量，并记录测试时间和错误提示，才方便判断是模式问题还是代理 IP 本身的问题。",{"type":31,"level":21,"children":445},[446],{"text":447,"type":29},"脱敏记录应该包含哪些字段？",{"type":25,"children":449},[450],{"text":451,"type":29},"下面是一份记录格式示例，版本、时间、出口 IP 和状态码均为演示值；`203.0.113.0\u002F24`、`198.51.100.0\u002F24` 属于文档保留地址，不能当作真实代理结果。发布前应替换为实际测试中脱敏后的值。",{"type":25,"children":453},[454],{"text":455,"type":29},"**测试条件（示例）**：SSTap 1.1.0（示例版本，需按当前客户端核对）、Windows 11 23H2、同一 SOCKS5 账号、同一网页和游戏服务器、测试时间 2026-09-10 14:00–14:20（UTC+8）。",{"type":98,"children":457},[458],{"text":459,"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":461},[462],{"text":463,"type":29},"记录时应同时保存时间戳、规则命中日志、出口 IP 查询结果和截图。示例中的“成功”或“超时”只说明如何填写，不能据此推断某个 SSTap 版本、协议或代理服务的真实表现。",{"type":31,"level":32,"children":465},[466],{"text":467,"type":29},"SSTap 模式选对后，什么时候还要评估静态住宅代理 IP？",{"type":25,"children":469},[470],{"text":471,"type":29},"短时网页测试、多地区采样或公开页面观察，可先测试动态住宅代理 IP；需要长期保持同一出口身份的登录或后台场景，再评估静态住宅代理 IP。模式选择解决的是流量范围，动态或静态解决的是出口变化方式，两者应分开判断。",{"type":31,"level":32,"children":473},[474],{"text":189,"type":29},{"type":31,"level":21,"children":476},[477],{"text":478,"type":29},"只想让一个网页走代理 IP，应选什么模式？",{"type":25,"children":480},[481],{"text":482,"type":29},"优先使用规则模式，并把目标域名及其登录、接口和静态资源域名一并纳入规则。",{"type":31,"level":21,"children":484},[485],{"text":486,"type":29},"全局模式下网页能打开但游戏不能连接怎么办？",{"type":25,"children":488},[489],{"text":490,"type":29},"检查游戏进程是否被 SSTap 接管、游戏要求的代理协议和端口是否匹配，再用同一代理 IP 做单独测试。",{"type":31,"level":21,"children":492},[493],{"text":494,"type":29},"如何确认没有 DNS 泄漏？",{"type":25,"children":496},[497],{"text":498,"type":29},"分别在网页和应用环境检查 DNS 解析结果，并结合出口 IP、地区和 WebRTC 检测。发现本地 DNS 或真实 IP 时，先检查 SSTap 接管范围和系统网络设置。",{"type":31,"level":21,"children":500},[501],{"text":502,"type":29},"SSTap 适合长期登录业务吗？",{"type":25,"children":504},[505],{"text":506,"type":29},"要看业务是否要求长期稳定的出口身份。长期登录通常应优先评估静态住宅代理 IP，并保持代理、浏览器环境、语言和时区的一致性。",{"type":25,"children":508},[509],{"text":510,"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":512},[513],{"text":225,"type":29},{"type":25,"children":515},[516],{"text":517,"type":29},"先按流量范围选择 SSTap 模式，再验证实际出口 IP、DNS 和网页或游戏连接。模式选对后，仍要根据业务是否需要长期稳定身份，评估动态住宅代理 IP 或静态住宅代理 IP。",{"source":6,"id":519,"documentId":520,"translationKey":520,"locale":9,"slug":521,"path":522,"_path":522,"title":523,"description":524,"excerpt":524,"image":525,"publishedAt":526,"updatedAt":527,"author":17,"tags":528,"featured":19,"sortOrder":20,"readingTime":32,"bodyType":22,"bodyBlocks":529,"bodyHtml":230},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",[],[530,534,538,542,546,550,554,558,562,566,570,574,578,582,586,590,594,597,601,605,609,613,617,621,625,629,633,637,640],{"type":25,"children":531},[532],{"text":533,"type":29},"Hubstudio 指纹浏览器检测代理 IP 失败时，先确认海外网络环境或加速通道，再检查套餐是否到期、流量是否用尽和资源状态，最后核对代理参数、Hubstudio 配置和认证方式。不要在未确认错误类型前反复更换代理 IP。",{"type":31,"level":32,"children":535},[536],{"text":537,"type":29},"Hubstudio 代理检测失败时，先区分超时、连接拒绝和认证失败",{"type":25,"children":539},[540],{"text":541,"type":29},"超时多与网络或端口有关，连接拒绝常见于协议或端口错误，认证失败则检查账号密码和认证方式。保留错误提示，便于后续与服务商核对。",{"type":98,"children":543},[544],{"text":545,"type":29},"| 错误类型 | 常见原因 | 优先检查 |\n| --- | --- | --- |\n| 超时 | 本机网络、端口不可达、资源失效 | 网络、主机、端口 |\n| 连接拒绝 | 协议或端口不匹配 | HTTP\u002FHTTPS\u002FSOCKS5 与对应端口 |\n| 认证失败 | 账号密码错误或认证方式不匹配 | 认证方式和凭证 |\n| 检测成功但出口异常 | 环境绑定或 DNS\u002FWebRTC 泄漏 | 出口 IP、地区、DNS\u002FWebRTC |",{"type":31,"level":32,"children":547},[548],{"text":549,"type":29},"如何核对 Hubstudio 的代理配置字段？",{"type":25,"children":551},[552],{"text":553,"type":29},"常见入口是“新建\u002F编辑环境 → 代理设置”。可以先按下面的字段映射逐项填写，再保存并启用环境：",{"type":31,"level":21,"children":555},[556],{"text":557,"type":29},"主机和端口",{"type":25,"children":559},[560],{"text":561,"type":29},"“主机”填写服务商提供的域名或 IP，例如 `proxy.example.com`；“端口”填写对应数字端口，例如 `10000`。不要把带协议前缀的完整 URL 粘进主机框，也不要把端口写进账号字段。",{"type":31,"level":21,"children":563},[564],{"text":565,"type":29},"协议",{"type":25,"children":567},[568],{"text":569,"type":29},"在“协议\u002F代理类型”中选择服务商实际提供的 HTTP、HTTPS 或 SOCKS5。示例：服务商给出 `SOCKS5 proxy.example.com:10000`，Hubstudio 就选择 SOCKS5、主机填 `proxy.example.com`、端口填 `10000`；协议选错时常见表现是连接被拒绝或握手失败。",{"type":31,"level":21,"children":571},[572],{"text":573,"type":29},"账号和密码",{"type":25,"children":575},[576],{"text":577,"type":29},"启用账号密码认证时，在“账号\u002F用户名”填 `demo_user`、在“密码”填服务商生成的密码，并确认没有复制换行或空格。不要在未要求时额外填写白名单、公网 IP 或二次认证字段。",{"type":25,"children":579},[580],{"text":581,"type":29},"保存后先用 IP 检测页验证出口国家\u002F城市、DNS 和 WebRTC，再判断环境是否真正可用。",{"type":31,"level":32,"children":583},[584],{"text":585,"type":29},"Hubstudio 代理检测失败时，如何按网络、代理参数和认证逐步验证？",{"type":25,"children":587},[588],{"text":589,"type":29},"先在本机确认海外网络或加速通道，再用同一组信息测试代理连通；随后在 Hubstudio 中保存并启用配置，重新检测，最后打开 IP 检测页确认出口和地区。超时继续查网络\u002F端口，连接拒绝查协议，`407 Proxy Authentication Required` 优先查账号、密码和认证方式。只有在服务商明确为“动态住宅代理 IP + API 提取”配置了来源白名单时，才核对当前公网出口是否在白名单内；普通账号密码接入不要默认要求白名单。出口异常再查环境绑定与 DNS\u002FWebRTC。",{"type":25,"children":591},[592],{"text":593,"type":29},"例如，Hubstudio 返回 `407 Proxy Authentication Required` 时，先用同一账号在服务商提供的接入方式重试：若仍为 407，通常是凭证失效、认证方式选错或账号未开通；若服务商确认该 API 提取方案启用了来源白名单，再补查公网出口是否匹配。若返回 `connection refused`，则优先把协议和端口与订单信息逐字对照，而不是反复改密码。",{"type":31,"level":32,"children":595},[596],{"text":189,"type":29},{"type":31,"level":21,"children":598},[599],{"text":600,"type":29},"主机端口都正确但仍失败怎么办？",{"type":25,"children":602},[603],{"text":604,"type":29},"继续核对协议、账号密码、认证方式和复制内容中的空格。只有服务商明确要求来源白名单（例如动态住宅代理 IP 的 API 提取场景）时，才确认当前公网出口是否已加入；账号密码模式不应默认配置白名单。",{"type":31,"level":21,"children":606},[607],{"text":608,"type":29},"不同认证方式可以同时使用吗？",{"type":25,"children":610},[611],{"text":612,"type":29},"通常应按服务商指定的单一认证方式配置，不要自行混用。",{"type":31,"level":21,"children":614},[615],{"text":616,"type":29},"检测通过后还要检查什么？",{"type":25,"children":618},[619],{"text":620,"type":29},"检查出口 IP、地区、DNS\u002FWebRTC 和目标网站访问；检测通过只代表代理连通。",{"type":31,"level":21,"children":622},[623],{"text":624,"type":29},"Hubstudio 中应选择动态还是静态住宅代理 IP？",{"type":25,"children":626},[627],{"text":628,"type":29},"短时、多地区任务可测试动态住宅代理 IP；长期登录更适合评估静态住宅代理 IP。",{"type":25,"children":630},[631],{"text":632,"type":29},"可参考[Hubstudio 代理设置教程](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002Fproxy-Settings\u002FFingerprint-Browser-Setting\u002FHubstudio)。",{"type":25,"children":634},[635],{"text":636,"type":29},"可同时参阅 [Hubstudio 官方帮助中心](https:\u002F\u002Fsupport-orig.hubstudio.cn\u002F)。如果当前版本没有完全相同的字段名称，以官方模板和客户端当前界面为准。",{"type":25,"children":638},[639],{"text":225,"type":29},{"type":25,"children":641},[642],{"text":643,"type":29},"定位并修复网络、代理参数或认证问题后，再验证出口 IP、地区、DNS\u002FWebRTC 和目标网站结果，不能只凭客户端的检测提示判断代理已经可用。",[645],{"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":646,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":647,"bodyHtml":230},[],[648,651,654,657,680,683,686,689,692,695,698,701,704,707,710,713,716,719,722,725,728,731,734,737,740,743,746,749,752,755,758,761,764,767,770,773,776,779,782,785,788,791,794],{"type":25,"children":649},[650],{"text":28,"type":29},{"type":31,"level":32,"children":652},[653],{"text":35,"type":29},{"type":25,"children":655},[656],{"text":39,"type":29},{"type":41,"format":42,"children":658},[659,662,665,668,671,674,677],{"type":45,"children":660},[661],{"text":48,"type":29},{"type":45,"children":663},[664],{"text":52,"type":29},{"type":45,"children":666},[667],{"text":56,"type":29},{"type":45,"children":669},[670],{"text":60,"type":29},{"type":45,"children":672},[673],{"text":64,"type":29},{"type":45,"children":675},[676],{"text":68,"type":29},{"type":45,"children":678},[679],{"text":72,"type":29},{"type":25,"children":681},[682],{"text":76,"type":29},{"type":25,"children":684},[685],{"text":80,"type":29},{"type":25,"children":687},[688],{"text":84,"type":29},{"type":31,"level":32,"children":690},[691],{"text":88,"type":29},{"type":25,"children":693},[694],{"text":92,"type":29},{"type":25,"children":696},[697],{"text":96,"type":29},{"type":98,"children":699},[700],{"text":101,"type":29},{"type":25,"children":702},[703],{"text":105,"type":29},{"type":31,"level":32,"children":705},[706],{"text":109,"type":29},{"type":25,"children":708},[709],{"text":113,"type":29},{"type":98,"children":711},[712],{"text":117,"type":29},{"type":31,"level":32,"children":714},[715],{"text":121,"type":29},{"type":31,"level":21,"children":717},[718],{"text":125,"type":29},{"type":25,"children":720},[721],{"text":129,"type":29},{"type":25,"children":723},[724],{"text":133,"type":29},{"type":31,"level":21,"children":726},[727],{"text":137,"type":29},{"type":25,"children":729},[730],{"text":141,"type":29},{"type":25,"children":732},[733],{"text":145,"type":29},{"type":25,"children":735},[736],{"text":149,"type":29},{"type":31,"level":32,"children":738},[739],{"text":153,"type":29},{"type":98,"children":741},[742],{"text":157,"type":29},{"type":25,"children":744},[745],{"text":161,"type":29},{"type":25,"children":747},[748],{"text":165,"type":29},{"type":31,"level":32,"children":750},[751],{"text":169,"type":29},{"type":25,"children":753},[754],{"text":173,"type":29},{"type":31,"level":32,"children":756},[757],{"text":177,"type":29},{"type":25,"children":759},[760],{"text":181,"type":29},{"type":25,"children":762},[763],{"text":185,"type":29},{"type":31,"level":32,"children":765},[766],{"text":189,"type":29},{"type":31,"level":21,"children":768},[769],{"text":193,"type":29},{"type":25,"children":771},[772],{"text":197,"type":29},{"type":31,"level":21,"children":774},[775],{"text":201,"type":29},{"type":25,"children":777},[778],{"text":205,"type":29},{"type":31,"level":21,"children":780},[781],{"text":209,"type":29},{"type":25,"children":783},[784],{"text":213,"type":29},{"type":31,"level":21,"children":786},[787],{"text":217,"type":29},{"type":25,"children":789},[790],{"text":221,"type":29},{"type":25,"children":792},[793],{"text":225,"type":29},{"type":25,"children":795},[796],{"text":229,"type":29},null,[],[]]