WWW.YOUINFO.SITE
标签聚合 ups

/tag/ups

LinuxDo 最新话题 · 2026-06-10 11:07:10+08:00 · tech

unexpected status 502 Bad Gateway: {“error”:{“message”:“Upstream request failed”,“type”:“upstream_error”}}event: response.failed data: {“type”:“response.failed”,“response”:{“id”:“resp_3d59569dfe714f778f4d3a86e03cd7a9”,“object”:“response”,“model”:“gpt-5.5” ,“status”:“failed”,“output”: ,“error”:{“code”:“upstream_error”,“message”:“Upstream request failed”}}}, url: https://qinghuan86.top/responses , request id: 3d59569d-fe71-4f77-8f4d-3a86e03cd7a9 unexpected status 502 Bad Gateway: error code: 502, url: https://sub.kedaya.xyz/responses , cf-ray: a0917ff36d08a0b0-HKG 我分别使用两家中转站,都报错,昨天突然出现,之前都还正常使用,有佬知道为什么吗。我用cc-switch管理的 2 个帖子 - 2 位参与者 阅读完整话题

LinuxDo 最新话题 · 2026-05-18 13:46:15+08:00 · tech

佬们有遇到么,CPA用gpt-5.5经常遇到empty_stream: upstream stream closed before first payload 这个需要怎么处理 === REQUEST INFO === Version: v7.1.10 URL: /v1/chat/completions Method: POST Downstream Transport: http Upstream Transport: http Timestamp: 2026-05-18T13:33:33.199643948+08:00 === HEADERS === X-Stainless-Timeout: 120 Content-Type: application/json X-Stainless-Arch: x64 Authorization: Bearer sk-Z…KWhS X-Stainless-Runtime: node Accept-Encoding: gzip User-Agent: axonhub/1.0 X-Stainless-Lang: js X-Stainless-Retry-Count: 2 Accept: text/event-stream Cache-Control: no-cache X-Stainless-Os: Linux X-Stainless-Runtime-Version: v22.22.2 Traceparent: 00-50dbbb4398e0dd067d36e2ef926a4cca-ceaf41ef5915d900-01 Content-Length: 1198682 Connection: keep-alive X-Stainless-Package-Version: 6.37.0 === REQUEST BODY === === API RESPONSE === Timestamp: 2026-05-18T13:33:44.38717663+08:00 {“error”:{“message”:“empty_stream: upstream stream closed before first payload”,“type”:“server_error”,“code”:“internal_server_error”}} === RESPONSE === Status: 500 Access-Control-Allow-Methods: GET, POST, PUT, PATCH, DELETE, OPTIONS Access-Control-Allow-Headers: * Content-Type: application/json Access-Control-Allow-Origin: * {“error”:{“message”:“empty_stream: upstream stream closed before first payload”,“type”:“server_error”,“code”:“internal_server_error”}} 6 个帖子 - 4 位参与者 阅读完整话题

LinuxDo 最新话题 · 2026-05-11 23:02:15+08:00 · tech

最近跑长任务用gpt-5.5经常性出现upstream stream closed before first payload错误,CPA里200多个认证文件一起报错,导致总是任务跑一半中断了;也搞不清楚是什么原因,切换其他模型比如gpt-5.4又好了,是5.5的bug吗?还是CPA配置的问题?有了解的吗? 这是CPA的配置: debug: false # 是否将日志重定向到日志文件中 # 默认启用,日志会保存在程序目录下的logs文件夹中 # 如果关闭的话,会在控制台显示日志 logging-to-file: false # 开关使用统计,默认启用 # 需要使用API来查看使用量,可以用WebUI来查看 usage-statistics-enabled: true # 当请求碰到403, 408, 500, 502, 503, 504这些错误码的时候,程序自动重试请求的次数 request-retry: 3 # 冷却中的凭据等待的最长时间(秒),超过则触发重试。 max-retry-interval: 30 # 模型受到限制之后的处理行为 quota-exceeded: # 多账号轮询的核心配置 # 设置为true时,例如一个账号触发了429,程序会自动切换到下一个账号重新发起请求 # 设置为false时,程序会把429的错误信息发给客户端,结束当前请求 # 也就是说,当设置为true时,只要轮询的账号里至少有一个号是正常的,客户端这里就不会报错 # 而设置false时,则需要客户端来进行重试或中止操作 switch-project: true # Gemini CLI独占配置,适用于Gemini 2.5 Pro和Gemini 2.5 Flash模型 # 当正式版配额用完之后,会自动切换到Preview模型,保持开启即可 switch-preview-model: true # 隐藏配置,可以关闭重试时的间隔时间,根据需要进行设置 # 例如某模型触发429后,程序会暂时停用它,且每次再触发都会增加停用时间,最多延长到30分钟 # 默认情况下,停用期内会跳过该模型 # 设置true后,无论该模型是否处于停用期,仍会每次都向该模型发起请求,不再跳过 disable-cooling: false commercial-mode: true streaming: keepalive-seconds: 15 bootstrap-retries: 1 1 个帖子 - 1 位参与者 阅读完整话题

LinuxDo 最新话题 · 2026-05-11 16:28:29+08:00 · tech

Hi everyone, Recently most promo sites, referral systems, and public/free AI access platforms seem to have stopped working or no longer provide free Claude model access. I wanted to ask if there are still any public welfare sites, educational platforms, research communities, or upstream providers that offer limited/free Claude API access for testing, development, or learning purposes. If anyone knows any active platforms, community projects, gateways, or provider programs, please share them. Thanks! 1 个帖子 - 1 位参与者 阅读完整话题