[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-strapi-article:zh:api-429-rate-limit-proxy-ip":3,"blog-article:\u002Fblog\u002Fapi-429-rate-limit-proxy-ip":86,"blog-related:\u002Fblog\u002Fapi-429-rate-limit-proxy-ip":698,"blog-translations:\u002Fblog\u002Fapi-429-rate-limit-proxy-ip":699},{"available":4,"article":5,"relatedArticles":260,"translations":568},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":124},"strapi",1133,"yt7goiy9dxlsuedchj03a24o","zh","api-429-rate-limit-proxy-ip","\u002Fblog\u002Fapi-429-rate-limit-proxy-ip","OpenAI API 429、GitHub API rate limit，换 IP 有用吗？","OpenAI API 429 和 GitHub rate limit 先按限额、Token、项目、并发、重试和缓存排查；只有程序侧数字稳定后，才用出口对照判断代理 IP 是否放大失败。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_api_429_rate_limit_proxy_ip_cover_f85daa45db.webp","2026-07-14T09:06:50.773Z","2026-07-14T09:06:50.751Z","Global Proxies Team",[],false,0,5,"blocks",[24,30,34,40,44,48,53,57,62,66,70,74,125,129,133,137,141,145,149,153,157,161,165,169,173,177,181,216,220,224,228,232,236,240,244,248,252,256],{"type":25,"children":26},"paragraph",[27],{"text":28,"type":29},"OpenAI API 429 和 GitHub API rate limit，不要先归因到代理 IP。真正要判断的是：平台限额有没有触顶、Token 是否被共用、程序是否把并发和重试打得太满。","text",{"type":25,"children":31},[32],{"text":33,"type":29},"换代理 IP 不是 OpenAI API 429 或 GitHub API rate limit 的第一步。先看控制台限额、响应头、Token 共用、项目限额、并发数、重试间隔和缓存命中率；这些数字稳定后，如果错误仍跟某个共享出口、地区识别或来源一起出现，再评估静态住宅代理 IP 或独享度更高的 IP 资源。",{"type":35,"level":36,"children":37},"heading",2,[38],{"text":39,"type":29},"OpenAI API 429 通常是额度限速，不是地区限制",{"type":25,"children":41},[42],{"text":43,"type":29},"`429` 通常表示请求频率或额度触顶，`rate limit` 是平台对调用次数、Token 消耗、并发或时间窗口设置的限制。OpenAI API 常见口径包括 RPM、TPM、项目限额和模型限速；GitHub API 则更常见于 Token 额度、请求频率、接口分类和账号权限。",{"type":25,"children":45},[46],{"text":47,"type":29},"先不要急着换代理 IP。第一轮只记录 6 个字段：接口、模型、项目、Token、并发数、429 出现时间。如果 429 集中在几秒内连发，通常先怀疑并发\u002FRPM；如果长文本、批量总结或大 `max_tokens` 任务更容易报错，优先看 TPM；如果同一 Token 被多个脚本、CI 或队友共用，就先查 Token 维度的消耗。",{"type":35,"level":49,"children":50},3,[51],{"text":52,"type":29},"RPM、TPM 和并发分别会触发什么限制？",{"type":25,"children":54},[55],{"text":56,"type":29},"RPM 看每分钟请求数，TPM 看每分钟输入和输出 Token 总量，并发看同一时间塞进接口的请求数。三者任何一个先触顶，都可能表现成 429，但日志现象不一样：",{"type":58,"children":59},"code",[60],{"text":61,"type":29},"| 报错表现 | 问题 | 设置修改 |\n| --- | --- | --- |\n| 429 在 1-5 秒内成串出现，单次请求很短 | 并发或 RPM 顶满 | 把并发从 20 降到 5，队列限速到每秒 1-2 个请求 |\n| 短请求没事，长文总结、批量翻译、大输出更容易失败 | TPM 顶满 | 降低 `max_tokens`，把长文拆段，记录每分钟 input\u002Foutput token |\n| 单人测试正常，多人、CI、定时任务一起跑就报错 | Token 或项目共用 | 给任务拆独立 Token\u002F项目，按项目看限额和用量 |\n| 第一次失败后重试越来越密，最后连续超时 | 重试策略错误 | 从固定 0.5s 重试改成指数退避 2\u002F4\u002F8s，并限制最大重试次数 |",{"type":25,"children":63},[64],{"text":65,"type":29},"OpenAI 的具体 RPM\u002FTPM 以控制台当前显示为准，不同模型、项目和账号层级会变；[OpenAI 帮助中心](https:\u002F\u002Fhelp.openai.com\u002Fen\u002Farticles\u002F5955604-how-can-i-solve-429-too-many-requests-errors)也建议用指数退避处理 429，并提醒失败请求同样会计入每分钟限制。比如你的控制台如果显示某模型 RPM 约 500、TPM 约 30 万，而脚本同时开 20 个 worker，每个 worker 失败后 0.5 秒就重试，几秒内打满 RPM 很正常；先把 worker 降到 5、重试改成 2\u002F4\u002F8 秒，再观察 10-15 分钟内 429 是否明显回落。",{"type":25,"children":67},[68],{"text":69,"type":29},"GitHub API 也要分认证方式看。[GitHub REST API rate limits 文档](https:\u002F\u002Fdocs.github.com\u002Fen\u002Frest\u002Fusing-the-rest-api\u002Frate-limits-for-the-rest-api)里，未认证请求常见上限是每小时 60 次，个人 Token 常见上限是每小时 5000 次；如果是 GitHub Actions 里的 `GITHUB_TOKEN`，还要按仓库维度看限额。排查时直接看响应头里的 `x-ratelimit-limit`、`x-ratelimit-remaining`、`x-ratelimit-reset`，不要只看报错文案。",{"type":25,"children":71},[72],{"text":73,"type":29},"下面这张图用于区分 429 限速和地区限制，帮助你先判断问题是额度、并发，还是代理 IP 出口。",{"type":75,"image":76,"children":122},"image",{"id":77,"ext":78,"url":79,"hash":80,"mime":81,"name":82,"size":83,"width":84,"height":85,"caption":86,"formats":87,"provider":119,"createdAt":120,"updatedAt":120,"documentId":121,"focalPoint":86,"previewUrl":86,"publishedAt":120,"alternativeText":86,"provider_metadata":86},1049,".webp","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_api_429_rate_limit_proxy_ip_1_44f922cdc5c5_bc6a81e0d0.webp","api_429_rate_limit_proxy_ip_1_44f922cdc5c5_bc6a81e0d0","image\u002Fwebp","api-429-rate-limit-proxy-ip-1-44f922cdc5c5.webp",44.34,1280,720,null,{"large":88,"small":95,"medium":103,"thumbnail":111},{"ext":78,"url":79,"hash":89,"mime":81,"name":90,"path":86,"size":91,"width":92,"height":93,"sizeInBytes":94},"large_api_429_rate_limit_proxy_ip_1_44f922cdc5c5_bc6a81e0d0","large_api-429-rate-limit-proxy-ip-1-44f922cdc5c5.webp",30.24,1000,562,30238,{"ext":78,"url":96,"hash":97,"mime":81,"name":98,"path":86,"size":99,"width":100,"height":101,"sizeInBytes":102},"https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Fsmall_api_429_rate_limit_proxy_ip_1_44f922cdc5c5_bc6a81e0d0.webp","small_api_429_rate_limit_proxy_ip_1_44f922cdc5c5_bc6a81e0d0","small_api-429-rate-limit-proxy-ip-1-44f922cdc5c5.webp",12.78,500,281,12782,{"ext":78,"url":104,"hash":105,"mime":81,"name":106,"path":86,"size":107,"width":108,"height":109,"sizeInBytes":110},"https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Fmedium_api_429_rate_limit_proxy_ip_1_44f922cdc5c5_bc6a81e0d0.webp","medium_api_429_rate_limit_proxy_ip_1_44f922cdc5c5_bc6a81e0d0","medium_api-429-rate-limit-proxy-ip-1-44f922cdc5c5.webp",21.45,750,422,21448,{"ext":78,"url":112,"hash":113,"mime":81,"name":114,"path":86,"size":115,"width":116,"height":117,"sizeInBytes":118},"https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Fthumbnail_api_429_rate_limit_proxy_ip_1_44f922cdc5c5_bc6a81e0d0.webp","thumbnail_api_429_rate_limit_proxy_ip_1_44f922cdc5c5_bc6a81e0d0","thumbnail_api-429-rate-limit-proxy-ip-1-44f922cdc5c5.webp",5.01,245,138,5008,"local","2026-07-14T04:16:11.972Z","jrsh5bpn7iz353gkq0lmrbwc",[123],{"text":124,"type":29},"",{"type":25,"children":126},[127],{"text":128,"type":29},"如果 429 已随并发下降而回落，问题基本不在代理 IP。只有在额度、Token 和重试策略都稳定后，错误仍明显集中在同一共享出口、同一地区识别或同一来源，才进入出口对照测试。",{"type":35,"level":36,"children":130},[131],{"text":132,"type":29},"429 排查按一条主线走",{"type":25,"children":134},[135],{"text":136,"type":29},"同一模型或同一 GitHub 接口突然连续报 429，可以按这条顺序处理：",{"type":25,"children":138},[139],{"text":140,"type":29},"1. 先看平台限额：OpenAI 看控制台里的模型、项目、RPM、TPM；GitHub 看 `\u002Frate_limit` 或响应头。\n2. 再拆 Token 和项目：一个批处理任务、一个线上服务、一个 CI 流程尽量分开统计，不让它们抢同一份额度。\n3. 然后压程序侧节流：先把并发降到原来的 1\u002F4，设置队列限速和指数退避，观察 10-15 分钟。\n4. 最后做出口对照：同一脚本、同一 Token、同一并发，只换共享出口和独享度更高的出口，看错误是否只跟来源一起移动。",{"type":25,"children":142},[143],{"text":144,"type":29},"这里最容易踩坑的是“重试放大”。一次请求失败后，如果 20 个 worker 都按 0.5 秒固定间隔重试，实际请求量会在短时间内翻倍，后面看到的连续 429 可能是程序自己打出来的。更稳的做法是：429 后等待 2 秒，再失败等 4 秒、8 秒，最多重试 3 次；如果响应头给了 reset 时间，就按 reset 时间恢复，而不是继续压接口。",{"type":25,"children":146},[147],{"text":148,"type":29},"缓存也要算进排查。比如同一批 GitHub repo 元数据、OpenAI 分类结果或翻译结果被重复请求，先把可复用结果缓存 10-60 分钟；缓存命中率从 0 提到 60% 以上后，如果 429 同步下降，说明瓶颈在请求量，不是代理 IP。",{"type":35,"level":36,"children":150},[151],{"text":152,"type":29},"账号异常不要和 429 混在一起归因",{"type":25,"children":154},[155],{"text":156,"type":29},"验证码、申诉、登录异常、付款审核和封禁，不等于 API 429。它们更常跟账号行为、登录设备、付款资料、历史请求和环境一致性有关；429 则要先看限额窗口、Token 消耗和并发。",{"type":25,"children":158},[159],{"text":160,"type":29},"实际排查时可以分两张表记录。限速表只放接口、Token、项目、RPM\u002FTPM、并发、重试次数和 429 时间；账号表只放登录设备、地区变化、验证码、申诉、封禁和付款状态。两张表分开后，才不容易把“账号需要审核”误判成“代理 IP 不够好”，也不容易把“程序重试过密”误判成“账号被风控”。",{"type":25,"children":162},[163],{"text":164,"type":29},"如果同时遇到 403、unsupported country 或验证码，再对照 [OpenAI API 403](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fopenai-api-403-unsupported-country-proxy) 和 [403\u002F429\u002F验证码排查](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-403-429-captcha-troubleshooting)。这类问题再进入代理 IP 出口、地区一致性和账号环境排查会更清楚。",{"type":35,"level":36,"children":166},[167],{"text":168,"type":29},"程序侧要能看到节流是否真的生效",{"type":25,"children":170},[171],{"text":172,"type":29},"同一接口短时间反复触发 429，先别只改配置名，要确认程序实际生效。至少打出 5 类日志：每分钟请求数、每分钟 Token 数、当前并发、重试次数、缓存命中率。只要这 5 个数字不可见，就很难判断换代理 IP 是否有价值。",{"type":25,"children":174},[175],{"text":176,"type":29},"下面是一个可照做的压测顺序：第一轮并发 20、固定 0.5 秒重试，记录 429 比例；第二轮并发 5、指数退避 2\u002F4\u002F8 秒，最大重试 3 次；第三轮加缓存，重复请求直接命中本地结果。如果第二轮 429 从连续成串变成零星出现，说明并发和重试已经是主因；如果第三轮继续下降，说明缓存能直接省额度。",{"type":25,"children":178},[179],{"text":180,"type":29},"不要连续立即重试，否则请求队列会越堆越高，最后变成连续 429、任务超时和成本放大。等程序侧数字稳定后，再做代理 IP 出口对照，结果才有参考价值。\n下面这张图用于把 API 调用放量前的程序侧检查项列成清单，适合在增加代理 IP 预算前先做自查。",{"type":75,"image":182,"children":214},{"id":183,"ext":78,"url":184,"hash":185,"mime":81,"name":186,"size":187,"width":84,"height":85,"caption":86,"formats":188,"provider":119,"createdAt":212,"updatedAt":212,"documentId":213,"focalPoint":86,"previewUrl":86,"publishedAt":212,"alternativeText":86,"provider_metadata":86},1050,"https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_api_429_rate_limit_proxy_ip_2_45fe7993cf87_1dcfdabb3f.webp","api_429_rate_limit_proxy_ip_2_45fe7993cf87_1dcfdabb3f","api-429-rate-limit-proxy-ip-2-45fe7993cf87.webp",42.03,{"large":189,"small":194,"medium":200,"thumbnail":206},{"ext":78,"url":184,"hash":190,"mime":81,"name":191,"path":86,"size":192,"width":92,"height":93,"sizeInBytes":193},"large_api_429_rate_limit_proxy_ip_2_45fe7993cf87_1dcfdabb3f","large_api-429-rate-limit-proxy-ip-2-45fe7993cf87.webp",28.43,28428,{"ext":78,"url":195,"hash":196,"mime":81,"name":197,"path":86,"size":198,"width":100,"height":101,"sizeInBytes":199},"https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Fsmall_api_429_rate_limit_proxy_ip_2_45fe7993cf87_1dcfdabb3f.webp","small_api_429_rate_limit_proxy_ip_2_45fe7993cf87_1dcfdabb3f","small_api-429-rate-limit-proxy-ip-2-45fe7993cf87.webp",11.97,11970,{"ext":78,"url":201,"hash":202,"mime":81,"name":203,"path":86,"size":204,"width":108,"height":109,"sizeInBytes":205},"https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Fmedium_api_429_rate_limit_proxy_ip_2_45fe7993cf87_1dcfdabb3f.webp","medium_api_429_rate_limit_proxy_ip_2_45fe7993cf87_1dcfdabb3f","medium_api-429-rate-limit-proxy-ip-2-45fe7993cf87.webp",20.24,20242,{"ext":78,"url":207,"hash":208,"mime":81,"name":209,"path":86,"size":210,"width":116,"height":117,"sizeInBytes":211},"https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Fthumbnail_api_429_rate_limit_proxy_ip_2_45fe7993cf87_1dcfdabb3f.webp","thumbnail_api_429_rate_limit_proxy_ip_2_45fe7993cf87_1dcfdabb3f","thumbnail_api-429-rate-limit-proxy-ip-2-45fe7993cf87.webp",4.97,4966,"2026-07-14T04:16:12.408Z","ruu6yykqwirhmiijdmwrlfu3",[215],{"text":124,"type":29},{"type":35,"level":36,"children":217},[218],{"text":219,"type":29},"FAQ",{"type":35,"level":49,"children":221},[222],{"text":223,"type":29},"代理 IP 买了还是一直报429，问题通常出在哪",{"type":25,"children":225},[226],{"text":227,"type":29},"先看控制台或响应头里的限额剩余量，再查 Token 是否被多人、CI、定时任务共用。并发降到 1\u002F4、重试改成 2\u002F4\u002F8 秒后仍集中在同一出口，再考虑代理 IP 变量。",{"type":35,"level":49,"children":229},[230],{"text":231,"type":29},"长期登录该选动态住宅代理 IP 还是静态住宅代理 IP",{"type":25,"children":233},[234],{"text":235,"type":29},"后台、店铺、广告账户更适合静态住宅代理 IP。",{"type":35,"level":49,"children":237},[238],{"text":239,"type":29},"机房代理 IP 什么时候能省成本，什么时候会买错",{"type":25,"children":241},[242],{"text":243,"type":29},"地区一致性要求不高、只做访问测试时，机房代理 IP 通常更省；需要多地区短时验证时，也可以对照 [动态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fdynamic-residential)。",{"type":35,"level":49,"children":245},[246],{"text":247,"type":29},"OpenAI API 429 换代理 IP 有用吗？",{"type":25,"children":249},[250],{"text":251,"type":29},"只有在限额、Token、项目、并发和重试策略都排过后，换代理 IP 才有判断价值。否则 429 多半会跟着同一套脚本继续出现。",{"type":25,"children":253},[254],{"text":255,"type":29},"---",{"type":25,"children":257},[258],{"text":259,"type":29},"如果你还在比较不同业务场景的适配边界，可以先[了解全球代理服务](https:\u002F\u002Fwww.quanqiudaili.com\u002F)，再结合官网购买页、后台展示或客户经理信息确认具体方案。GitHub 拉取、Copilot 和 API 限额混在一起时，可以对照 [GitHub clone 与 Copilot 排查](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fgithub-clone-copilot-proxy-troubleshooting)；已经进入接入设置阶段，可以继续看 [全球代理 FAQ](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002FFaq\u002F) 和 [代理设置帮助](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002Fproxy-Settings)。",[261,348,462],{"source":6,"id":262,"documentId":263,"translationKey":263,"locale":9,"slug":264,"path":265,"_path":265,"title":266,"description":267,"excerpt":267,"image":268,"publishedAt":269,"updatedAt":270,"author":17,"tags":271,"featured":19,"sortOrder":20,"readingTime":272,"bodyType":22,"bodyBlocks":273,"bodyHtml":124},2175,"hioeqohoh99p55q3dp4molr2","proxy-check-failed-troubleshooting","\u002Fblog\u002Fproxy-check-failed-troubleshooting","指纹浏览器代理 IP 检测失败的通用排查清单","指纹浏览器代理 IP 检测失败时，先核对协议、主机、端口、账号密码和配置启用状态，再用 curl 或其他客户端对照，区分字段错误、网络不可达和浏览器规则冲突。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_ip_cover_1_3ab32dc39c.webp","2026-08-24T08:20:59.237Z","2026-08-24T08:20:59.221Z",[],1,[274,278,282,286,290,294,298,302,306,310,314,317,321,325,329,333,336,340,344],{"type":25,"children":275},[276],{"text":277,"type":29},"指纹浏览器显示代理检测失败，不等于代理资源必然不可用。应先核对配置文件中的协议、主机、端口和认证，再用外部工具复测，区分字段错误、网络不可达和检测规则差异。",{"type":35,"level":36,"children":279},[280],{"text":281,"type":29},"配置文件中的协议、主机、端口和认证是否正确？",{"type":25,"children":283},[284],{"text":285,"type":29},"打开出现问题的浏览器配置文件，重新填写 HTTP、HTTPS 或 SOCKS5 协议、主机、端口、用户名和密码。不要把 API 链接或 `IP:端口` 整段粘贴到单独字段中。保存后完全关闭并重新打开该配置文件。",{"type":25,"children":287},[288],{"text":289,"type":29},"指纹浏览器通常按配置文件单独保存代理，不一定跟随系统代理。只有一个配置文件失败时，应先对比另一配置文件，而不是直接判断整组代理资源失效。",{"type":35,"level":36,"children":291},[292],{"text":293,"type":29},"外部工具成功但指纹浏览器失败说明什么？",{"type":25,"children":295},[296],{"text":297,"type":29},"在 curl、系统网络工具或另一客户端中使用同一组主机、端口、协议和凭据测试。外部工具成功而指纹浏览器失败，重点查配置文件是否启用代理、扩展冲突和客户端字段映射。",{"type":58,"children":299},[300],{"text":301,"type":29},"| 现象 | 优先检查 | 结论 |\n|---|---|---|\n| 配置保存后仍显示本地 IP | 配置文件是否启用代理 | 请求可能没有经过代理 |\n| 返回 407 | 用户名、密码和认证方式 | 连接已到达入口但认证失败 |\n| 外部工具成功、浏览器失败 | 配置文件、扩展、规则 | 指纹浏览器接管范围异常 |\n| 出口 IP 正确但目标站异常 | 时区、语言、WebRTC 和站点规则 | 不一定是代理检测失败 |",{"type":35,"level":36,"children":303},[304],{"text":305,"type":29},"出口 IP 通过后还要检查哪些浏览器环境？",{"type":25,"children":307},[308],{"text":309,"type":29},"代理检测通过后，再检查浏览器时区、语言、DNS 和 WebRTC 是否与出口地区明显冲突。不要为了“检测通过”同时更换账号、设备和代理，否则无法判断是哪一项导致结果变化。",{"type":25,"children":311},[312],{"text":313,"type":29},"检测失败与目标平台验证码是两个问题：前者先查配置和代理连通，后者再查账号历史、设备环境和行为风险。长期登录可评估[静态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fstatic-residential-standard)，多地区短时访问可了解[动态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fdynamic-residential)。",{"type":35,"level":36,"children":315},[316],{"text":219,"type":29},{"type":35,"level":49,"children":318},[319],{"text":320,"type":29},"为什么出口 IP 正确，平台仍提示异常？",{"type":25,"children":322},[323],{"text":324,"type":29},"平台还会检查时区、语言、设备指纹、Cookie、账号历史和行为节奏。检测页通过只代表基础出口可见。",{"type":35,"level":49,"children":326},[327],{"text":328,"type":29},"提交给服务商前准备什么？",{"type":25,"children":330},[331],{"text":332,"type":29},"准备配置文件名称、目标站、协议、主机和端口、错误码、测试时间及截图；密码不要公开发送。",{"type":25,"children":334},[335],{"text":255,"type":29},{"type":35,"level":36,"children":337},[338],{"text":339,"type":29},"指纹浏览器代理 IP 检测失败时应该按什么顺序排查？",{"type":25,"children":341},[342],{"text":343,"type":29},"按“配置字段 → 认证方式 → 外部对照 → 浏览器环境 → 目标站规则”的顺序排查，能区分代理资源问题和指纹浏览器配置问题。",{"type":25,"children":345},[346],{"text":347,"type":29},"配置后仍失败时，可按上方清单整理脱敏信息，再通过[全球代理 FAQ](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002FFaq\u002F)继续排查。",{"source":6,"id":349,"documentId":350,"translationKey":350,"locale":9,"slug":351,"path":352,"_path":352,"title":353,"description":354,"excerpt":354,"image":355,"publishedAt":356,"updatedAt":357,"author":17,"tags":358,"featured":19,"sortOrder":20,"readingTime":272,"bodyType":22,"bodyBlocks":359,"bodyHtml":124},2133,"mxzjklqnw9bjlkwm3k4xwspl","ping-proxy-proxy-ip-guide","\u002Fblog\u002Fping-proxy-proxy-ip-guide","端口能 ping 通但代理不能用，是不是协议填错了？","主机能 ping 通不代表代理 IP 可用。通过 TCP 端口测试、HTTP\u002FHTTPS\u002FSOCKS5 协议核对、认证结果和目标网站对照，逐层定位连接失败原因。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_ping_cover_1_bbcb1574f4.webp","2026-08-20T09:26:43.967Z","2026-08-20T09:26:43.947Z",[],[360,364,368,372,376,380,384,388,392,396,400,404,408,412,415,419,423,427,431,435,439,443,447,450,454,458],{"type":25,"children":361},[362],{"text":363,"type":29},"协议填错是常见原因，但 ping 通并不能证明代理可用。ping 使用 ICMP，只能说明主机可能响应；代理还要通过指定 TCP 端口完成协议握手和认证。",{"type":25,"children":365},[366],{"text":367,"type":29},"严格来说，ping 通的是主机，不是端口。TCP 端口可达也只说明连接能够建立，仍需继续验证协议、认证和实际代理请求。",{"type":35,"level":36,"children":369},[370],{"text":371,"type":29},"主机能 ping 通后，怎么测试 TCP 端口？",{"type":25,"children":373},[374],{"text":375,"type":29},"使用系统或客户端的 TCP 连接测试确认主机和端口可达。端口不通时，先查本地网络、防火墙、主机和端口；不要直接修改账号密码或判断代理 IP 已失效。",{"type":35,"level":36,"children":377},[378],{"text":379,"type":29},"HTTP、HTTPS、SOCKS5 协议和字段怎么核对？",{"type":25,"children":381},[382],{"text":383,"type":29},"确认产品提供的是 HTTP、HTTPS 还是 SOCKS5，并在客户端选择对应协议。主机、端口、用户名和密码分别填写，不能把 `IP:端口`、API 链接或完整 URL 当成同一个字段。具体以产品和客户端字段说明为准。",{"type":25,"children":385},[386],{"text":387,"type":29},"代理协议与目标网址协议不是同一概念。访问 HTTPS 网站并不代表代理入口一定要选择 HTTPS；客户端仍要按产品提供的 HTTP、HTTPS 或 SOCKS5 接入方式完成握手，再处理目标网站的 HTTPS 连接。",{"type":35,"level":36,"children":389},[390],{"text":391,"type":29},"从 TCP 端口到目标网站怎么逐层复测？",{"type":25,"children":393},[394],{"text":395,"type":29},"1. 用正确协议建立代理连接。\n2. 填写用户名和密码，观察是否返回 407。\n3. 请求出口检测页，确认出口 IP 是否变化。\n4. 再访问目标网站，记录状态码、超时和页面结果。",{"type":25,"children":397},[398],{"text":399,"type":29},"如果客户端支持，可用同一组参数在 curl 或另一代理工具中复测。第二个工具成功时，优先检查原客户端的协议选择、字段映射和接管范围。",{"type":58,"children":401},[402],{"text":403,"type":29},"| 现象 | 优先检查 | 说明 |\n|---|---|---|\n| TCP 端口拒绝连接或超时 | 网络、主机、端口 | 尚未进入协议握手和认证 |\n| TCP 端口通但返回 407 | 用户名、密码和认证方式 | 连接已建立，认证失败 |\n| TCP 端口通但出现 TLS 错误 | 协议、CONNECT、客户端实现 | 端口可达但握手未完成 |\n| 出口 IP 未变化 | 客户端代理入口 | 请求可能绕过了代理 |\n| 出口已变化但返回 403\u002F429 | 请求特征、频率、目标站规则 | 不一定是协议错误 |",{"type":35,"level":36,"children":405},[406],{"text":407,"type":29},"什么时候更换代理 IP",{"type":25,"children":409},[410],{"text":411,"type":29},"只有主机、端口、协议、认证和出口都确认无误，且多个目标网址持续失败时，才考虑更换同地区代理 IP。单一网站或单一账号异常，应先查目标站规则和账号环境。",{"type":35,"level":36,"children":413},[414],{"text":219,"type":29},{"type":35,"level":49,"children":416},[417],{"text":418,"type":29},"ping 不通时，代理一定不能用吗？",{"type":25,"children":420},[421],{"text":422,"type":29},"不一定。服务器或网络可能禁止 ICMP 响应，但代理 TCP 端口仍可连接；应以端口测试和实际代理请求结果为准。",{"type":35,"level":49,"children":424},[425],{"text":426,"type":29},"HTTP、HTTPS 和 SOCKS5 可以随便选吗？",{"type":25,"children":428},[429],{"text":430,"type":29},"不可以。应按产品提供的接入协议和客户端字段选择，协议与端口不能凭名称猜测。",{"type":35,"level":49,"children":432},[433],{"text":434,"type":29},"返回 407 需要换 IP 吗？",{"type":25,"children":436},[437],{"text":438,"type":29},"通常不需要。407 优先指向认证失败，应先核对用户名、密码和认证方式。",{"type":35,"level":49,"children":440},[441],{"text":442,"type":29},"如何确认不是目标网站的问题？",{"type":25,"children":444},[445],{"text":446,"type":29},"用同一代理访问出口检测页和至少一个普通网站。只有某个目标站失败时，继续查该站的地区规则或账号状态。",{"type":25,"children":448},[449],{"text":255,"type":29},{"type":35,"level":36,"children":451},[452],{"text":453,"type":29},"ping 通但代理不能用时，应该按什么顺序排查？",{"type":25,"children":455},[456],{"text":457,"type":29},"速查顺序：TCP 端口 → 协议 → 认证 → 出口 IP → 目标网站。",{"type":25,"children":459},[460],{"text":461,"type":29},"仍无法定位时，带上主机、端口、协议、完整错误码和测试截图，通过[全球代理首页](https:\u002F\u002Fwww.quanqiudaili.com\u002F)咨询；不要公开发送完整密码。",{"source":6,"id":463,"documentId":464,"translationKey":464,"locale":9,"slug":465,"path":466,"_path":466,"title":467,"description":468,"excerpt":468,"image":469,"publishedAt":470,"updatedAt":471,"author":17,"tags":472,"featured":19,"sortOrder":20,"readingTime":272,"bodyType":22,"bodyBlocks":473,"bodyHtml":124},2132,"n4e0v2bagwqgcxp1on7axb1m","proxy-account-failed","\u002Fblog\u002Fproxy-account-failed","代理账号密码认证失败：大小写、过期和权限怎么查？","代理账号密码认证失败时，先区分 407 与端口超时，再检查大小写、空格、特殊字符、套餐有效期、流量余额、权限和客户端字段映射，减少无效更换代理 IP。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_cover_1_bbbf896121.webp","2026-08-20T09:26:24.470Z","2026-08-20T09:26:24.456Z",[],[474,478,482,486,490,494,498,502,506,510,514,518,521,525,529,533,537,541,545,549,553,557,560,564],{"type":25,"children":475},[476],{"text":477,"type":29},"代理账号密码认证失败时，先判断是否已经连接到代理入口。能连接但返回 407，优先检查用户名、密码和认证方式；连主机和端口都失败，则先查网络、主机和端口，不要反复修改密码。",{"type":35,"level":36,"children":479},[480],{"text":481,"type":29},"账号密码是否存在空格、大小写或特殊字符错误？",{"type":25,"children":483},[484],{"text":485,"type":29},"手动重新复制用户名和密码，去掉首尾空格，确认大小写、连字符和特殊字符没有变化。不要把带引号、带空格或整段代理链接直接粘贴到只接受用户名和密码的字段中。",{"type":35,"level":36,"children":487},[488],{"text":489,"type":29},"账号是否过期、流量用完或填错产品入口？",{"type":25,"children":491},[492],{"text":493,"type":29},"确认凭据属于当前代理产品、国家或地区和代理入口，并检查套餐有效期、流量余额、并发限制及子账号状态。不同产品的账号不能混用。",{"type":35,"level":36,"children":495},[496],{"text":497,"type":29},"407、端口超时和认证弹窗分别说明什么？",{"type":58,"children":499},[500],{"text":501,"type":29},"| 现象 | 优先检查 | 结论 |\n|---|---|---|\n| 返回 407 | 用户名、密码、认证方式 | 已到达代理入口，但认证未通过 |\n| 端口连接超时 | 网络、主机、端口 | 认证尚未开始，先查连接 |\n| 反复出现认证弹窗 | 凭据保存、字段映射、旧缓存 | 删除旧凭据后手动重填 |\n| 只有某个客户端失败 | 字段映射、协议和编码 | 代理资源未必失效 |\n| 账号突然失效 | 有效期、余额、权限和子账号 | 需核对资源状态 |",{"type":35,"level":36,"children":503},[504],{"text":505,"type":29},"代理认证失败应该按什么顺序复测？",{"type":25,"children":507},[508],{"text":509,"type":29},"1. 用同一主机、端口和协议手动填写用户名与密码。\n2. 在最小客户端中请求出口检测页，记录完整错误码。\n3. 用第二个客户端复测，但不要同时更换网络和代理参数。\n4. 仍返回 407 时，保存时间、产品、入口和截图，联系服务商核对账号状态。",{"type":25,"children":511},[512],{"text":513,"type":29},"脱敏复测记录示例：`2026-08-19 10:30`，入口 `proxy.example.com:PORT`，协议 `HTTP`，用户名 `user_***`，密码不记录；结果为 `407 Proxy Authentication Required`。随后按上表核对凭据、认证方式和账号状态。",{"type":25,"children":515},[516],{"text":517,"type":29},"能看到出口 IP 变化，只能证明代理接入成功，不代表目标网站一定放行；验证码、账号审核和站点权限仍需单独判断。",{"type":35,"level":36,"children":519},[520],{"text":219,"type":29},{"type":35,"level":49,"children":522},[523],{"text":524,"type":29},"大小写真的会导致认证失败吗？",{"type":25,"children":526},[527],{"text":528,"type":29},"会。用户名和密码应按服务端记录原样填写，尤其要注意大写字母、数字和特殊字符。",{"type":35,"level":49,"children":530},[531],{"text":532,"type":29},"返回 407 是端口问题吗？",{"type":25,"children":534},[535],{"text":536,"type":29},"通常不是。407 表示代理入口要求认证或认证未通过；端口完全不通时一般表现为超时或连接拒绝。",{"type":35,"level":49,"children":538},[539],{"text":540,"type":29},"什么时候需要更换代理 IP？",{"type":25,"children":542},[543],{"text":544,"type":29},"先确认账号、网络、主机、端口和协议都正确。只有同一目标站持续异常，才考虑更换同地区代理 IP。",{"type":35,"level":49,"children":546},[547],{"text":548,"type":29},"复测需要准备哪些信息？",{"type":25,"children":550},[551],{"text":552,"type":29},"准备目标站、代理主机和端口、协议、错误码、测试时间、客户端名称及截图，不要在公开渠道发送完整密码。",{"type":25,"children":554},[555],{"text":556,"type":29},"可通过[全球代理 FAQ](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002FFaq\u002F)核对认证问题；提交截图前应遮盖完整用户名、密码和其他敏感字段。",{"type":25,"children":558},[559],{"text":255,"type":29},{"type":35,"level":36,"children":561},[562],{"text":563,"type":29},"代理账号密码认证失败时应该先查什么？",{"type":25,"children":565},[566],{"text":567,"type":29},"认证失败的排查顺序是：连接是否建立 → 用户名密码格式 → 有效期和权限 → 产品入口 → 客户端差异。按层验证，比连续更换代理 IP 更容易定位原因。",[569],{"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":570,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":571,"bodyHtml":124},[],[572,575,578,581,584,587,590,593,596,599,602,605,614,617,620,623,626,629,632,635,638,641,644,647,650,653,656,665,668,671,674,677,680,683,686,689,692,695],{"type":25,"children":573},[574],{"text":28,"type":29},{"type":25,"children":576},[577],{"text":33,"type":29},{"type":35,"level":36,"children":579},[580],{"text":39,"type":29},{"type":25,"children":582},[583],{"text":43,"type":29},{"type":25,"children":585},[586],{"text":47,"type":29},{"type":35,"level":49,"children":588},[589],{"text":52,"type":29},{"type":25,"children":591},[592],{"text":56,"type":29},{"type":58,"children":594},[595],{"text":61,"type":29},{"type":25,"children":597},[598],{"text":65,"type":29},{"type":25,"children":600},[601],{"text":69,"type":29},{"type":25,"children":603},[604],{"text":73,"type":29},{"type":75,"image":606,"children":612},{"id":77,"ext":78,"url":79,"hash":80,"mime":81,"name":82,"size":83,"width":84,"height":85,"caption":86,"formats":607,"provider":119,"createdAt":120,"updatedAt":120,"documentId":121,"focalPoint":86,"previewUrl":86,"publishedAt":120,"alternativeText":86,"provider_metadata":86},{"large":608,"small":609,"medium":610,"thumbnail":611},{"ext":78,"url":79,"hash":89,"mime":81,"name":90,"path":86,"size":91,"width":92,"height":93,"sizeInBytes":94},{"ext":78,"url":96,"hash":97,"mime":81,"name":98,"path":86,"size":99,"width":100,"height":101,"sizeInBytes":102},{"ext":78,"url":104,"hash":105,"mime":81,"name":106,"path":86,"size":107,"width":108,"height":109,"sizeInBytes":110},{"ext":78,"url":112,"hash":113,"mime":81,"name":114,"path":86,"size":115,"width":116,"height":117,"sizeInBytes":118},[613],{"text":124,"type":29},{"type":25,"children":615},[616],{"text":128,"type":29},{"type":35,"level":36,"children":618},[619],{"text":132,"type":29},{"type":25,"children":621},[622],{"text":136,"type":29},{"type":25,"children":624},[625],{"text":140,"type":29},{"type":25,"children":627},[628],{"text":144,"type":29},{"type":25,"children":630},[631],{"text":148,"type":29},{"type":35,"level":36,"children":633},[634],{"text":152,"type":29},{"type":25,"children":636},[637],{"text":156,"type":29},{"type":25,"children":639},[640],{"text":160,"type":29},{"type":25,"children":642},[643],{"text":164,"type":29},{"type":35,"level":36,"children":645},[646],{"text":168,"type":29},{"type":25,"children":648},[649],{"text":172,"type":29},{"type":25,"children":651},[652],{"text":176,"type":29},{"type":25,"children":654},[655],{"text":180,"type":29},{"type":75,"image":657,"children":663},{"id":183,"ext":78,"url":184,"hash":185,"mime":81,"name":186,"size":187,"width":84,"height":85,"caption":86,"formats":658,"provider":119,"createdAt":212,"updatedAt":212,"documentId":213,"focalPoint":86,"previewUrl":86,"publishedAt":212,"alternativeText":86,"provider_metadata":86},{"large":659,"small":660,"medium":661,"thumbnail":662},{"ext":78,"url":184,"hash":190,"mime":81,"name":191,"path":86,"size":192,"width":92,"height":93,"sizeInBytes":193},{"ext":78,"url":195,"hash":196,"mime":81,"name":197,"path":86,"size":198,"width":100,"height":101,"sizeInBytes":199},{"ext":78,"url":201,"hash":202,"mime":81,"name":203,"path":86,"size":204,"width":108,"height":109,"sizeInBytes":205},{"ext":78,"url":207,"hash":208,"mime":81,"name":209,"path":86,"size":210,"width":116,"height":117,"sizeInBytes":211},[664],{"text":124,"type":29},{"type":35,"level":36,"children":666},[667],{"text":219,"type":29},{"type":35,"level":49,"children":669},[670],{"text":223,"type":29},{"type":25,"children":672},[673],{"text":227,"type":29},{"type":35,"level":49,"children":675},[676],{"text":231,"type":29},{"type":25,"children":678},[679],{"text":235,"type":29},{"type":35,"level":49,"children":681},[682],{"text":239,"type":29},{"type":25,"children":684},[685],{"text":243,"type":29},{"type":35,"level":49,"children":687},[688],{"text":247,"type":29},{"type":25,"children":690},[691],{"text":251,"type":29},{"type":25,"children":693},[694],{"text":255,"type":29},{"type":25,"children":696},[697],{"text":259,"type":29},[],[]]