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