[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-strapi-article:zh:github-clone-slow-proxy-settings":3,"blog-article:\u002Fblog\u002Fgithub-clone-slow-proxy-settings":709,"blog-related:\u002Fblog\u002Fgithub-clone-slow-proxy-settings":710,"blog-translations:\u002Fblog\u002Fgithub-clone-slow-proxy-settings":711},{"available":4,"article":5,"relatedArticles":178,"translations":594},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":177},"strapi",2553,"ud49a06o1bzvxeww4n87vqd7","zh","github-clone-slow-proxy-settings","\u002Fblog\u002Fgithub-clone-slow-proxy-settings","GitHub clone 慢和代理设置有什么关系？","GitHub clone 变慢不一定是代理 IP 导致，也可能与 DNS、HTTPS、SSH、LFS 或仓库体积有关。本文按协议和下载阶段拆解排查步骤，帮助判断代理是否真正改善速度。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_github_clone_cover_1eb79d48c0.webp","2026-09-08T02:05:55.939Z","2026-09-08T02:05:55.924Z","Global Proxies Team",[],false,0,3,"blocks",[24,30,36,40,44,48,52,56,60,64,68,72,76,81,85,89,93,97,101,105,109,113,117,121,125,129,133,137,141,145,149,153,157,161,165,169,173],{"type":25,"children":26},"paragraph",[27],{"text":28,"type":29},"GitHub clone 变慢不一定是代理 IP 的问题，也可能来自 DNS、仓库体积、LFS、HTTPS\u002FSSH 配置或本地网络。先用同一仓库比较直连与代理的延迟、吞吐和失败情况，再决定是否调整代理设置。","text",{"type":31,"level":32,"children":33},"heading",2,[34],{"text":35,"type":29},"GitHub clone 变慢通常卡在哪个环节",{"type":31,"level":21,"children":37},[38],{"text":39,"type":29},"域名解析阶段",{"type":25,"children":41},[42],{"text":43,"type":29},"先看 DNS 解析耗时和解析结果。所有仓库都变慢时，应优先排查本地 DNS、网络链路和代理解析方式。",{"type":31,"level":21,"children":45},[46],{"text":47,"type":29},"建立 HTTPS 或 SSH 连接阶段",{"type":25,"children":49},[50],{"text":51,"type":29},"如果只在 HTTPS 或 SSH 下变慢，应检查对应协议的代理配置、连接耗时和 SSH 握手情况。",{"type":31,"level":21,"children":53},[54],{"text":55,"type":29},"Git 对象下载阶段",{"type":25,"children":57},[58],{"text":59,"type":29},"小仓库正常而大仓库变慢时，重点检查对象数量、压缩处理、带宽和下载吞吐，不要直接归因于代理 IP。",{"type":31,"level":21,"children":61},[62],{"text":63,"type":29},"LFS 文件下载阶段",{"type":25,"children":65},[66],{"text":67,"type":29},"如果普通对象正常但 LFS 很慢，应单独检查 LFS 下载地址、配置、耗时和失败率。",{"type":31,"level":32,"children":69},[70],{"text":71,"type":29},"为什么 DNS、HTTPS、SSH 和 LFS 要分开测试",{"type":25,"children":73},[74],{"text":75,"type":29},"对上述四个阶段分别记录解析耗时、连接或握手耗时、下载吞吐、失败率和错误信息，确保测试指标与具体阶段对应。",{"type":77,"children":78},"code",[79],{"text":80,"type":29},"| 层级 | 应检查内容 | 对比指标 |\n| --- | --- | --- |\n| DNS | 域名解析链路 | 解析耗时、解析结果 |\n| HTTPS | Git 代理和连接配置 | 连接耗时、下载吞吐 |\n| SSH | SSH 配置文件和代理命令 | 握手时间、失败信息 |\n| LFS | LFS 独立下载地址和配置 | LFS 文件耗时、失败率 |",{"type":31,"level":32,"children":82},[83],{"text":84,"type":29},"Git、SSH 和系统代理冲突时先检查什么",{"type":25,"children":86},[87],{"text":88,"type":29},"检查 Git 的全局和项目级配置，以及 SSH 的独立配置文件。系统代理生效不代表 Git、SSH 或 LFS 一定继承，Git 单独设置代理也可能绕过系统代理。",{"type":31,"level":21,"children":90},[91],{"text":92,"type":29},"HTTPS：直接设置 Git 的代理 IP",{"type":25,"children":94},[95],{"text":96,"type":29},"```bash\ngit config --global http.proxy http:\u002F\u002Fuser:pass@host:port\ngit config --global https.proxy http:\u002F\u002Fuser:pass@host:port\ngit clone https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo.git\n```\n只想对当前仓库生效时去掉 `--global`；测试直连可用 `git config --global --unset http.proxy` 和 `git config --global --unset https.proxy`。",{"type":31,"level":21,"children":98},[99],{"text":100,"type":29},"SSH：在 `~\u002F.ssh\u002Fconfig` 使用 ProxyCommand",{"type":25,"children":102},[103],{"text":104,"type":29},"```sshconfig\nHost github.com\nHostName github.com\nUser git\nProxyCommand ncat --proxy host:port --proxy-type http %h %p\n```\n上例需要安装 Ncat；SSH 不会读取 Git 的 `http.proxy`，因此必须单独配置或明确走系统代理。",{"type":31,"level":32,"children":106},[107],{"text":108,"type":29},"代理什么时候能加快 clone，什么时候反而变慢",{"type":25,"children":110},[111],{"text":112,"type":29},"遇到 GitHub clone 慢时，当本地到目标站的网络质量较差、代理出口链路更稳定时，代理可能改善下载；如果代理距离更远、带宽不足或多了一层转发，速度反而可能下降，因此要用同一仓库和协议做对照。大仓库可先用 `git clone --depth 1 https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo.git` 做浅克隆；`git config --global http.postBuffer 524288000` 只用于应对部分大请求失败，不能替代带宽或链路优化。",{"type":31,"level":32,"children":114},[115],{"text":116,"type":29},"GitHub clone 很慢时应该按什么顺序排查",{"type":31,"level":21,"children":118},[119],{"text":120,"type":29},"出口与耗时记录示例：HTTPS、SSH 与代理开关",{"type":25,"children":122},[123],{"text":124,"type":29},"对同一仓库分别测试 HTTPS、SSH、LFS 及代理开关；记录 DNS 时间、TLS 建连、首字节、总耗时、吞吐和重试次数，并保留命令输出。下面是记录格式示例（数值为演示，不代表本文实测结论）：",{"type":77,"children":126},[127],{"text":128,"type":29},"| 方式 | DNS\u002FTLS | 总耗时 | 吞吐 | 结果 |\n| --- | ---: | ---: | ---: | --- |\n| 直连 HTTPS | 180\u002F420 ms | 96 s | 2.1 MB\u002Fs | 完成 |\n| 代理 IP HTTPS | 42\u002F160 ms | 58 s | 3.6 MB\u002Fs | 完成 |\n| 代理 IP SSH | —\u002F510 ms | 71 s | 2.9 MB\u002Fs | 完成 |",{"type":25,"children":130},[131],{"text":132,"type":29},"可用 `curl -w 'dns=%{time_namelookup} tls=%{time_appconnect} total=%{time_total}\\n' -o NUL -s https:\u002F\u002Fgithub.com` 记录 HTTPS 的 DNS、TLS 和总耗时。仓库地址与认证方式可对照 [GitHub 克隆仓库文档](https:\u002F\u002Fdocs.github.com\u002Fen\u002Frepositories\u002Fcreating-and-managing-repositories\u002Fcloning-a-repository)。\n1. 用小仓库和目标仓库分别做直连基线。\n2. 分别测试 DNS、HTTPS、SSH 和 LFS。\n3. 检查 Git、SSH、LFS 与系统代理的配置来源。\n4. 对比代理前后的延迟、吞吐、失败率和总下载时间。",{"type":31,"level":32,"children":134},[135],{"text":136,"type":29},"FAQ",{"type":31,"level":21,"children":138},[139],{"text":140,"type":29},"为什么浏览器访问 GitHub 正常，但 git clone 仍然很慢？",{"type":25,"children":142},[143],{"text":144,"type":29},"浏览器和 Git 可能使用不同的代理配置，clone 还涉及 HTTPS、SSH 或 LFS，应分别检查配置。",{"type":31,"level":21,"children":146},[147],{"text":148,"type":29},"如何判断代理是否让 clone 变快？",{"type":25,"children":150},[151],{"text":152,"type":29},"固定同一仓库、协议和时间窗口，比较解析耗时、连接耗时、吞吐、失败率和总下载时间。",{"type":31,"level":21,"children":154},[155],{"text":156,"type":29},"Git、SSH 和系统代理应该怎么排查？",{"type":25,"children":158},[159],{"text":160,"type":29},"先确认配置来源，再只启用一层代理做基线，确认实际出口和下载结果后再处理冲突。",{"type":31,"level":21,"children":162},[163],{"text":164,"type":29},"为什么小仓库正常，大仓库或 LFS 下载很慢？",{"type":25,"children":166},[167],{"text":168,"type":29},"大仓库可能受对象数量、压缩处理或 LFS 下载影响。应分别比较普通对象和 LFS 文件的耗时，不要只根据一次完整 clone 的总时间判断代理效果。",{"type":25,"children":170},[171],{"text":172,"type":29},"---",{"type":25,"children":174},[175],{"text":176,"type":29},"带走要点：先固定仓库和协议做直连基线，再分别配置 Git HTTPS 代理、SSH `ProxyCommand` 或环境变量；大仓库优先比较浅克隆与吞吐，并核对 DNS\u002FTLS 计时。只有代理 IP 的出口和耗时持续改善，才值得保留该配置。","",[179,314,468],{"source":6,"id":180,"documentId":181,"translationKey":181,"locale":9,"slug":182,"path":183,"_path":183,"title":184,"description":185,"excerpt":185,"image":186,"publishedAt":187,"updatedAt":188,"author":17,"tags":189,"featured":19,"sortOrder":20,"readingTime":32,"bodyType":22,"bodyBlocks":190,"bodyHtml":177},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",[],[191,195,199,203,224,228,232,236,240,244,248,252,256,260,264,268,272,275,279,283,287,291,295,299,303,307,310],{"type":25,"children":192},[193],{"text":194,"type":29},"动态住宅代理 IP 更适合短会话、多地区轮换、公开采样和批量测试；静态住宅代理 IP 更适合长期登录、店铺后台和广告账户。选择时先看业务能否接受出口变化，再比较地区、会话时长、协议、认证方式和成本。",{"type":31,"level":32,"children":196},[197],{"text":198,"type":29},"哪些业务适合动态住宅代理 IP",{"type":25,"children":200},[201],{"text":202,"type":29},"价格监测、广告展示核对、搜索结果观察、公开页面采样和多地区测试，通常更重视 IP 数量与轮换效率。动态住宅代理 IP 可按请求或粘性会话切换，适合彼此独立、无需保持同一出口的短会话。",{"type":204,"format":205,"children":206},"list","unordered",[207,212,216,220],{"type":208,"children":209},"list-item",[210],{"text":211,"type":29},"价格监测：每次请求可以使用不同出口，便于抽样多个地区和运营商，减少为保持单一身份而付出的会话成本。",{"type":208,"children":213},[214],{"text":215,"type":29},"广告展示核对：轮换出口能观察不同本地网络视角，适合发现广告素材、落地页或地区定向的变化；但预算、频控和 Cookie 仍要固定。",{"type":208,"children":217},[218],{"text":219,"type":29},"搜索结果观察：同一关键词在多个出口上采样，便于区分地区差异与单个出口的偶然结果，不需要让所有请求长期绑定一个 IP。",{"type":208,"children":221},[222],{"text":223,"type":29},"公开页面采样和多地区测试：请求彼此独立、失败后可换出口重试，轮换效率通常比长期保持同一出口更重要。",{"type":31,"level":32,"children":225},[226],{"text":227,"type":29},"哪些长期任务不适合使用动态住宅代理 IP？",{"type":25,"children":229},[230],{"text":231,"type":29},"长期登录、店铺后台、广告账户和支付后台更依赖稳定出口身份，通常优先测试静态住宅代理 IP，并保持设备指纹、语言、时区和操作节奏一致。静态住宅代理 IP 也不代表平台一定放行，仍需结合账号和环境判断。",{"type":31,"level":32,"children":233},[234],{"text":235,"type":29},"动态住宅代理 IP 和静态住宅代理 IP 怎么选",{"type":77,"children":237},[238],{"text":239,"type":29},"| 判断项 | 动态住宅代理 IP | 静态住宅代理 IP |\n| --- | --- | --- |\n| 主要任务 | 短时采样、多地区轮换 | 长期登录、稳定身份 |\n| 出口变化 | 可按请求或会话切换 | 在服务有效且配置不变时保持同一出口；异常更换或服务状态变化仍需核对 |\n| 重点确认 | 切换规则、会话时长、流量计费 | 独享性、持续可用性、周期计费 |",{"type":25,"children":241},[242],{"text":243,"type":29},"如果同时进行数据采样和账号操作，建议分别使用两套环境，避免出口变化互相干扰。",{"type":31,"level":32,"children":245},[246],{"text":247,"type":29},"购买动态或静态住宅代理 IP 前，要确认哪些产品参数？",{"type":25,"children":249},[250],{"text":251,"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":253},[254],{"text":255,"type":29},"动态住宅和静态住宅代理 IP 上线前，如何做对照验证？",{"type":25,"children":257},[258],{"text":259,"type":29},"固定账号、设备和目标网站，只改变代理 IP 类型；例如对短时采样记录每 100 次请求的地区跳变和验证码次数，对长期登录记录 24 小时内会话中断次数，再决定是否放量。",{"type":25,"children":261},[262],{"text":263,"type":29},"为了让记录可比较，可以先用下表的“示意区间”设计验收表，再替换成自己的真实观测值。数字仅演示记录格式，不是行业基准、供应商承诺或本文实测结论：",{"type":77,"children":265},[266],{"text":267,"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":269},[270],{"text":271,"type":29},"正式测试时应把每次出口、时间戳、状态码、地区库结果和截图一起保存；如果结果落在区间外，先复核目标站策略、Cookie、DNS\u002FWebRTC 和并发条件，再决定是否更换代理类型。",{"type":31,"level":32,"children":273},[274],{"text":136,"type":29},{"type":31,"level":21,"children":276},[277],{"text":278,"type":29},"并发和计费如何确认？",{"type":25,"children":280},[281],{"text":282,"type":29},"向购买页或客户经理确认并发上限、按流量还是按请求计费，以及失败请求是否计费，再用小样本核对账单口径。",{"type":31,"level":21,"children":284},[285],{"text":286,"type":29},"动态住宅代理 IP 和静态住宅代理 IP 怎么选？",{"type":25,"children":288},[289],{"text":290,"type":29},"能接受出口变化且需要轮换，优先测试动态住宅代理 IP；需要长期身份，优先测试静态住宅代理 IP。",{"type":31,"level":21,"children":292},[293],{"text":294,"type":29},"动态会话为什么不能保证精确时长？",{"type":25,"children":296},[297],{"text":298,"type":29},"会话可能受网络、资源回收和服务策略影响。查看产品支持请求切换还是粘性会话，并确认触发切换条件，不要按绝对在线时长理解。",{"type":31,"level":21,"children":300},[301],{"text":302,"type":29},"出现验证码就应该换成静态住宅代理 IP 吗？",{"type":25,"children":304},[305],{"text":306,"type":29},"不一定。先区分 IP、地区、设备环境、账号行为和平台规则，确认问题与出口变化有关后再切换。",{"type":25,"children":308},[309],{"text":172,"type":29},{"type":25,"children":311},[312],{"text":313,"type":29},"决策清单：能接受出口变化且任务是短会话采样，就先测动态资源；需要长期登录或同一身份，就先测静态资源；两者都先固定账号和设备做小样本验证，再按地区跳变、会话中断和验证码记录决定是否放量。",{"source":6,"id":315,"documentId":316,"translationKey":316,"locale":9,"slug":317,"path":318,"_path":318,"title":319,"description":320,"excerpt":320,"image":321,"publishedAt":322,"updatedAt":323,"author":17,"tags":324,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":325,"bodyHtml":177},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",[],[326,330,334,338,342,346,350,354,358,362,366,370,374,378,382,386,390,394,398,402,406,410,414,418,422,425,429,433,437,441,445,449,453,457,461,464],{"type":25,"children":327},[328],{"text":329,"type":29},"SSTap 代理模式怎么选，取决于你要接管的是全部流量、指定网站，还是某个进程。不同版本的 SSTap 可能将相关功能称为“全局”“规则”“进程”或“游戏模式”，具体名称应以当前客户端界面为准。下面按流量接管范围说明选择方法。模式决定哪些流量经过代理 IP，不能替代代理 IP 类型和出口地区的选择。",{"type":25,"children":331},[332],{"text":333,"type":29},"如果只是验证一个网页，先把目标域名加入规则；如果要判断整机出口，再短时间切到全局；游戏则单独确认进程是否被接管。SSTap 代理模式本身不会修复协议、端口或账号限制。",{"type":31,"level":32,"children":335},[336],{"text":337,"type":29},"SSTap 全局、规则与进程接管应该按什么场景选择？",{"type":25,"children":339},[340],{"text":341,"type":29},"三种模式的核心差别是“哪些流量会经过代理 IP”，而不是代理 IP 本身变了。选择时先按目标任务分流，再检查规则是否真正命中。",{"type":77,"children":343},[344],{"text":345,"type":29},"| 模式 | 影响范围 | 适合场景 | 注意事项 |\n| --- | --- | --- | --- |\n| 规则模式 | 指定域名或应用 | 单个网站、指定应用 | 依赖域名也要命中规则 |\n| 全局模式 | 更多系统流量 | 临时验证整机出口 | 增加流量消耗并影响无关应用 |\n| 进程接管（部分版本称游戏模式） | 指定进程及相关连接 | 游戏或应用连接测试 | 网页正常不代表目标进程已经经过代理 IP |",{"type":31,"level":21,"children":347},[348],{"text":349,"type":29},"什么时候应该使用全局模式？",{"type":25,"children":351},[352],{"text":353,"type":29},"全局模式会让更多系统流量经过代理，适合临时验证整机出口、排查某个应用是否受本地网络影响，或需要多个网页统一使用同一代理 IP 的情况。它也会影响无关应用，可能增加延迟和流量消耗，因此不适合长期无差别开启。",{"type":31,"level":21,"children":355},[356],{"text":357,"type":29},"只让指定网站或应用走代理时，怎么用规则模式？",{"type":25,"children":359},[360],{"text":361,"type":29},"规则模式按域名、程序或规则列表分流，适合只让指定网站或应用使用代理 IP。使用前要确认目标域名及其依赖域名都命中规则；如果网页能打开但登录、图片或接口失败，往往是依赖域名没有一起匹配。",{"type":31,"level":21,"children":363},[364],{"text":365,"type":29},"游戏连接时，什么时候应该使用进程接管？",{"type":25,"children":367},[368],{"text":369,"type":29},"部分版本把针对游戏的配置称为“游戏模式”，也有版本直接使用进程规则。应把目标游戏程序加入规则，确认进程路径和相关域名，并按游戏实际支持的代理协议和端口要求测试；无法在当前版本找到该名称时，以规则\u002F进程入口为准。",{"type":31,"level":21,"children":371},[372],{"text":373,"type":29},"第一次配置 SSTap，不确定选哪种模式怎么办？",{"type":25,"children":375},[376],{"text":377,"type":29},"只测试一个网页或应用，先用规则模式；需要确认整机是否统一经过代理，再短时间使用全局模式；主要解决游戏连接，则使用进程规则（部分版本称游戏模式）并单独验证游戏进程。测试完成后关闭不必要的全局代理，避免把本地其他流量一并转发。",{"type":31,"level":32,"children":379},[380],{"text":381,"type":29},"在 SSTap 中填写代理前，要先核对哪些信息？",{"type":25,"children":383},[384],{"text":385,"type":29},"先从代理服务商获取协议、主机、端口和认证信息。HTTP、HTTPS 或 SOCKS5 必须与服务商提供的格式一致，主机和端口不要混填；使用规则模式时还要确认规则文件已加载，使用进程规则（部分版本称游戏模式）时要确认目标进程路径正确。认证信息应以服务商提供的接入格式为准，不能把某一种认证方式当作所有 SSTap 配置的必填项。",{"type":31,"level":32,"children":387},[388],{"text":389,"type":29},"怎么确认网页和游戏真的走了代理 IP？",{"type":25,"children":391},[392],{"text":393,"type":29},"先在网页中记录出口 IP、地区和 DNS，再打开目标游戏或应用进行连接测试。网页正常、游戏失败时，优先检查游戏进程规则、协议兼容性和目标端口；网页和游戏都失败时，再回到主机、端口、认证和本地网络排查。每次只修改一个变量，并记录测试时间和错误提示，才方便判断是模式问题还是代理 IP 本身的问题。",{"type":31,"level":21,"children":395},[396],{"text":397,"type":29},"脱敏记录应该包含哪些字段？",{"type":25,"children":399},[400],{"text":401,"type":29},"下面是一份记录格式示例，版本、时间、出口 IP 和状态码均为演示值；`203.0.113.0\u002F24`、`198.51.100.0\u002F24` 属于文档保留地址，不能当作真实代理结果。发布前应替换为实际测试中脱敏后的值。",{"type":25,"children":403},[404],{"text":405,"type":29},"**测试条件（示例）**：SSTap 1.1.0（示例版本，需按当前客户端核对）、Windows 11 23H2、同一 SOCKS5 账号、同一网页和游戏服务器、测试时间 2026-09-10 14:00–14:20（UTC+8）。",{"type":77,"children":407},[408],{"text":409,"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":411},[412],{"text":413,"type":29},"记录时应同时保存时间戳、规则命中日志、出口 IP 查询结果和截图。示例中的“成功”或“超时”只说明如何填写，不能据此推断某个 SSTap 版本、协议或代理服务的真实表现。",{"type":31,"level":32,"children":415},[416],{"text":417,"type":29},"SSTap 模式选对后，什么时候还要评估静态住宅代理 IP？",{"type":25,"children":419},[420],{"text":421,"type":29},"短时网页测试、多地区采样或公开页面观察，可先测试动态住宅代理 IP；需要长期保持同一出口身份的登录或后台场景，再评估静态住宅代理 IP。模式选择解决的是流量范围，动态或静态解决的是出口变化方式，两者应分开判断。",{"type":31,"level":32,"children":423},[424],{"text":136,"type":29},{"type":31,"level":21,"children":426},[427],{"text":428,"type":29},"只想让一个网页走代理 IP，应选什么模式？",{"type":25,"children":430},[431],{"text":432,"type":29},"优先使用规则模式，并把目标域名及其登录、接口和静态资源域名一并纳入规则。",{"type":31,"level":21,"children":434},[435],{"text":436,"type":29},"全局模式下网页能打开但游戏不能连接怎么办？",{"type":25,"children":438},[439],{"text":440,"type":29},"检查游戏进程是否被 SSTap 接管、游戏要求的代理协议和端口是否匹配，再用同一代理 IP 做单独测试。",{"type":31,"level":21,"children":442},[443],{"text":444,"type":29},"如何确认没有 DNS 泄漏？",{"type":25,"children":446},[447],{"text":448,"type":29},"分别在网页和应用环境检查 DNS 解析结果，并结合出口 IP、地区和 WebRTC 检测。发现本地 DNS 或真实 IP 时，先检查 SSTap 接管范围和系统网络设置。",{"type":31,"level":21,"children":450},[451],{"text":452,"type":29},"SSTap 适合长期登录业务吗？",{"type":25,"children":454},[455],{"text":456,"type":29},"要看业务是否要求长期稳定的出口身份。长期登录通常应优先评估静态住宅代理 IP，并保持代理、浏览器环境、语言和时区的一致性。",{"type":25,"children":458},[459],{"text":460,"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":462},[463],{"text":172,"type":29},{"type":25,"children":465},[466],{"text":467,"type":29},"先按流量范围选择 SSTap 模式，再验证实际出口 IP、DNS 和网页或游戏连接。模式选对后，仍要根据业务是否需要长期稳定身份，评估动态住宅代理 IP 或静态住宅代理 IP。",{"source":6,"id":469,"documentId":470,"translationKey":470,"locale":9,"slug":471,"path":472,"_path":472,"title":473,"description":474,"excerpt":474,"image":475,"publishedAt":476,"updatedAt":477,"author":17,"tags":478,"featured":19,"sortOrder":20,"readingTime":32,"bodyType":22,"bodyBlocks":479,"bodyHtml":177},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",[],[480,484,488,492,496,500,504,508,512,516,520,524,528,532,536,540,544,547,551,555,559,563,567,571,575,579,583,587,590],{"type":25,"children":481},[482],{"text":483,"type":29},"Hubstudio 指纹浏览器检测代理 IP 失败时，先确认海外网络环境或加速通道，再检查套餐是否到期、流量是否用尽和资源状态，最后核对代理参数、Hubstudio 配置和认证方式。不要在未确认错误类型前反复更换代理 IP。",{"type":31,"level":32,"children":485},[486],{"text":487,"type":29},"Hubstudio 代理检测失败时，先区分超时、连接拒绝和认证失败",{"type":25,"children":489},[490],{"text":491,"type":29},"超时多与网络或端口有关，连接拒绝常见于协议或端口错误，认证失败则检查账号密码和认证方式。保留错误提示，便于后续与服务商核对。",{"type":77,"children":493},[494],{"text":495,"type":29},"| 错误类型 | 常见原因 | 优先检查 |\n| --- | --- | --- |\n| 超时 | 本机网络、端口不可达、资源失效 | 网络、主机、端口 |\n| 连接拒绝 | 协议或端口不匹配 | HTTP\u002FHTTPS\u002FSOCKS5 与对应端口 |\n| 认证失败 | 账号密码错误或认证方式不匹配 | 认证方式和凭证 |\n| 检测成功但出口异常 | 环境绑定或 DNS\u002FWebRTC 泄漏 | 出口 IP、地区、DNS\u002FWebRTC |",{"type":31,"level":32,"children":497},[498],{"text":499,"type":29},"如何核对 Hubstudio 的代理配置字段？",{"type":25,"children":501},[502],{"text":503,"type":29},"常见入口是“新建\u002F编辑环境 → 代理设置”。可以先按下面的字段映射逐项填写，再保存并启用环境：",{"type":31,"level":21,"children":505},[506],{"text":507,"type":29},"主机和端口",{"type":25,"children":509},[510],{"text":511,"type":29},"“主机”填写服务商提供的域名或 IP，例如 `proxy.example.com`；“端口”填写对应数字端口，例如 `10000`。不要把带协议前缀的完整 URL 粘进主机框，也不要把端口写进账号字段。",{"type":31,"level":21,"children":513},[514],{"text":515,"type":29},"协议",{"type":25,"children":517},[518],{"text":519,"type":29},"在“协议\u002F代理类型”中选择服务商实际提供的 HTTP、HTTPS 或 SOCKS5。示例：服务商给出 `SOCKS5 proxy.example.com:10000`，Hubstudio 就选择 SOCKS5、主机填 `proxy.example.com`、端口填 `10000`；协议选错时常见表现是连接被拒绝或握手失败。",{"type":31,"level":21,"children":521},[522],{"text":523,"type":29},"账号和密码",{"type":25,"children":525},[526],{"text":527,"type":29},"启用账号密码认证时，在“账号\u002F用户名”填 `demo_user`、在“密码”填服务商生成的密码，并确认没有复制换行或空格。不要在未要求时额外填写白名单、公网 IP 或二次认证字段。",{"type":25,"children":529},[530],{"text":531,"type":29},"保存后先用 IP 检测页验证出口国家\u002F城市、DNS 和 WebRTC，再判断环境是否真正可用。",{"type":31,"level":32,"children":533},[534],{"text":535,"type":29},"Hubstudio 代理检测失败时，如何按网络、代理参数和认证逐步验证？",{"type":25,"children":537},[538],{"text":539,"type":29},"先在本机确认海外网络或加速通道，再用同一组信息测试代理连通；随后在 Hubstudio 中保存并启用配置，重新检测，最后打开 IP 检测页确认出口和地区。超时继续查网络\u002F端口，连接拒绝查协议，`407 Proxy Authentication Required` 优先查账号、密码和认证方式。只有在服务商明确为“动态住宅代理 IP + API 提取”配置了来源白名单时，才核对当前公网出口是否在白名单内；普通账号密码接入不要默认要求白名单。出口异常再查环境绑定与 DNS\u002FWebRTC。",{"type":25,"children":541},[542],{"text":543,"type":29},"例如，Hubstudio 返回 `407 Proxy Authentication Required` 时，先用同一账号在服务商提供的接入方式重试：若仍为 407，通常是凭证失效、认证方式选错或账号未开通；若服务商确认该 API 提取方案启用了来源白名单，再补查公网出口是否匹配。若返回 `connection refused`，则优先把协议和端口与订单信息逐字对照，而不是反复改密码。",{"type":31,"level":32,"children":545},[546],{"text":136,"type":29},{"type":31,"level":21,"children":548},[549],{"text":550,"type":29},"主机端口都正确但仍失败怎么办？",{"type":25,"children":552},[553],{"text":554,"type":29},"继续核对协议、账号密码、认证方式和复制内容中的空格。只有服务商明确要求来源白名单（例如动态住宅代理 IP 的 API 提取场景）时，才确认当前公网出口是否已加入；账号密码模式不应默认配置白名单。",{"type":31,"level":21,"children":556},[557],{"text":558,"type":29},"不同认证方式可以同时使用吗？",{"type":25,"children":560},[561],{"text":562,"type":29},"通常应按服务商指定的单一认证方式配置，不要自行混用。",{"type":31,"level":21,"children":564},[565],{"text":566,"type":29},"检测通过后还要检查什么？",{"type":25,"children":568},[569],{"text":570,"type":29},"检查出口 IP、地区、DNS\u002FWebRTC 和目标网站访问；检测通过只代表代理连通。",{"type":31,"level":21,"children":572},[573],{"text":574,"type":29},"Hubstudio 中应选择动态还是静态住宅代理 IP？",{"type":25,"children":576},[577],{"text":578,"type":29},"短时、多地区任务可测试动态住宅代理 IP；长期登录更适合评估静态住宅代理 IP。",{"type":25,"children":580},[581],{"text":582,"type":29},"可参考[Hubstudio 代理设置教程](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002Fproxy-Settings\u002FFingerprint-Browser-Setting\u002FHubstudio)。",{"type":25,"children":584},[585],{"text":586,"type":29},"可同时参阅 [Hubstudio 官方帮助中心](https:\u002F\u002Fsupport-orig.hubstudio.cn\u002F)。如果当前版本没有完全相同的字段名称，以官方模板和客户端当前界面为准。",{"type":25,"children":588},[589],{"text":172,"type":29},{"type":25,"children":591},[592],{"text":593,"type":29},"定位并修复网络、代理参数或认证问题后，再验证出口 IP、地区、DNS\u002FWebRTC 和目标网站结果，不能只凭客户端的检测提示判断代理已经可用。",[595],{"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":596,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":597,"bodyHtml":177},[],[598,601,604,607,610,613,616,619,622,625,628,631,634,637,640,643,646,649,652,655,658,661,664,667,670,673,676,679,682,685,688,691,694,697,700,703,706],{"type":25,"children":599},[600],{"text":28,"type":29},{"type":31,"level":32,"children":602},[603],{"text":35,"type":29},{"type":31,"level":21,"children":605},[606],{"text":39,"type":29},{"type":25,"children":608},[609],{"text":43,"type":29},{"type":31,"level":21,"children":611},[612],{"text":47,"type":29},{"type":25,"children":614},[615],{"text":51,"type":29},{"type":31,"level":21,"children":617},[618],{"text":55,"type":29},{"type":25,"children":620},[621],{"text":59,"type":29},{"type":31,"level":21,"children":623},[624],{"text":63,"type":29},{"type":25,"children":626},[627],{"text":67,"type":29},{"type":31,"level":32,"children":629},[630],{"text":71,"type":29},{"type":25,"children":632},[633],{"text":75,"type":29},{"type":77,"children":635},[636],{"text":80,"type":29},{"type":31,"level":32,"children":638},[639],{"text":84,"type":29},{"type":25,"children":641},[642],{"text":88,"type":29},{"type":31,"level":21,"children":644},[645],{"text":92,"type":29},{"type":25,"children":647},[648],{"text":96,"type":29},{"type":31,"level":21,"children":650},[651],{"text":100,"type":29},{"type":25,"children":653},[654],{"text":104,"type":29},{"type":31,"level":32,"children":656},[657],{"text":108,"type":29},{"type":25,"children":659},[660],{"text":112,"type":29},{"type":31,"level":32,"children":662},[663],{"text":116,"type":29},{"type":31,"level":21,"children":665},[666],{"text":120,"type":29},{"type":25,"children":668},[669],{"text":124,"type":29},{"type":77,"children":671},[672],{"text":128,"type":29},{"type":25,"children":674},[675],{"text":132,"type":29},{"type":31,"level":32,"children":677},[678],{"text":136,"type":29},{"type":31,"level":21,"children":680},[681],{"text":140,"type":29},{"type":25,"children":683},[684],{"text":144,"type":29},{"type":31,"level":21,"children":686},[687],{"text":148,"type":29},{"type":25,"children":689},[690],{"text":152,"type":29},{"type":31,"level":21,"children":692},[693],{"text":156,"type":29},{"type":25,"children":695},[696],{"text":160,"type":29},{"type":31,"level":21,"children":698},[699],{"text":164,"type":29},{"type":25,"children":701},[702],{"text":168,"type":29},{"type":25,"children":704},[705],{"text":172,"type":29},{"type":25,"children":707},[708],{"text":176,"type":29},null,[],[]]