qwen-web models return "error: Provider returned empty content"

[yoursshadow50]

I am using v3.8.50 ...

","service":"omniroute","module":"sse","tag":"AUTH","msg":"Using qwen-web account: db27b32d..."}
[08:09:45] 📊 [USAGE] QWEN-WEB | in=284 | out=0 | account=db27b32d... (estimated)
[08:09:45] 🌊 [STREAM] QWEN-WEB | qwen3.8-max | 1646ms | error: Provider returned empty content
{"level":30,"time":"2026-08-14T08:09:47.974Z","service":"omniroute","module":"sse","tag":"HTTP","method":"POST","path":"/v1/chat/completions | qwen-web/qwen3.8-max-preview | 1 msgs","msg":"📥 POST /v1/chat/completions | qwen-web/qwen3.8-max-preview | 1 msgs"}
{"level":40,"time":"2026-08-14T08:09:47.977Z","service":"omniroute","module":"sse","tag":"CHAT","model":"qwen-web/qwen3.8-max-preview","msg":"Model 'qwen3.8-max-preview' is not available in the active live catalog for provider 'qwen-web'."}
{"level":30,"time":"2026-08-14T08:09:49.623Z","service":"omniroute","module":"sse","tag":"HTTP","method":"POST","path":"/v1/chat/completions | qwen-web/qwen3.7-max | 1 msgs","msg":"📥 POST /v1/chat/completions | qwen-web/qwen3.7-max | 1 msgs"}
{"level":30,"time":"2026-08-14T08:09:49.627Z","service":"omniroute","module":"sse","tag":"ROUTING","msg":"Provider: qwen-web, Model: qwen3.7-max"}
{"level":30,"time":"2026-08-14T08:09:49.629Z","service":"omniroute","module":"sse","tag":"AUTH","msg":"session_key=input:sha256:06667... has no available affinity target"}
{"level":30,"time":"2026-08-14T08:09:49.629Z","service":"omniroute","module":"sse","tag":"AUTH","msg":"Using qwen-web account: db27b32d..."}
[ProxyEgress] qwen-web/db27b32d in=? out=3.228.31.30 proxy=direct status=success
[08:09:50] 📊 [USAGE] QWEN-WEB | in=284 | out=0 | account=db27b32d... (estimated)
[08:09:50] 🌊 [STREAM] QWEN-WEB | qwen3.7-max | 1215ms | error: Provider returned empty content
{"level":30,"time":"2026-08-14T08:09:56.534Z","service":"omniroute","module":"sse","tag":"HTTP","method":"POST","path":"/v1/chat/completions | qwen-web/qwen3.7-plus | 1 msgs","msg":"📥 POST /v1/chat/completions | qwen-web/qwen3.7-plus | 1 msgs"}
{"level":30,"time":"2026-08-14T08:09:56.537Z","service":"omniroute","module":"sse","tag":"ROUTING","msg":"Provider: qwen-web, Model: qwen3.7-plus"}
{"level":30,"time":"2026-08-14T08:09:56.539Z","service":"omniroute","module":"sse","tag":"AUTH","msg":"session_key=input:sha256:8cb65... has no available affinity target"}
{"level":30,"time":"2026-08-14T08:09:56.539Z","service":"omniroute","module":"sse","tag":"AUTH","msg":"Using qwen-web account: db27b32d..."}
[ProxyEgress] qwen-web/db27b32d in=? out=3.228.31.30 proxy=direct status=success
[08:09:57] 📊 [USAGE] QWEN-WEB | in=284 | out=0 | account=db27b32d... (estimated)
[08:09:57] 🌊 [STREAM] QWEN-WEB | qwen3.7-plus | 1199ms | error: Provider returned empty content

[pacocartones]

This was answered about four hours before you posted, in a different thread you would not have seen: issue #9991, closed as an upstream limitation at 2026-08-14 04:00 UTC (closing comment). The short version of the maintainer's decision: chat.qwen.ai sits behind Alibaba's x5sec / RGV587 / FAIL_SYS_USER_VALIDATE challenge, the cookie-only web path cannot satisfy it, and routing qwen-web through the stealth browser subsystem would mean defeating those bot-detection controls, which is deliberately out of scope. So it is not your session and not your model ids — and no cookie re-capture will change it. That also settles your earlier #9583, where the ask was to re-capture the cookie jar: #9991 was reproduced on v3.8.50, the same version you are on, and its report states explicitly that the cause is not an expired session or a wrong model id.

Two things in your log are worth separating, because they are not the same failure.

The "empty content" lines are the challenge, not an empty answer. For qwen3.7-max and qwen3.7-plus your log shows [ProxyEgress] qwen-web/db27b32d ... status=success immediately before the error, and in=284 | out=0 at around 1.2 s — the request reached Alibaba and came back fine, it just carried nothing usable. The reason it surfaces as "Provider returned empty content" rather than as a challenge is a gap in the executor, and it is worth writing down because it is why nobody in #9583 could produce the HTTP status that was asked for:

• open-sse/executors/qwen-web.ts:203 treats the completion response as an error only when !upstream.ok || content-type includes text/html. A challenge served as HTTP 200 with a non-HTML body passes that check untouched.
• Consequently the body is never read at all: .text() runs only inside that branch (:204), so isWafResponse (:81-85, which looks for text/html, status 504, or aliyun_waf|baxia|<html in the body) is never even called on it. The upstream reason is discarded right there.
• The body then goes into the SSE parser, and parseSseDelta bails on line 474 for every line that does not start with data: — a plain JSON object has none.
• The client stream has already emitted its opening frame at :397, so downstream the watcher sees sawSseFrame() = true, sawContent() = false, and no terminal reason from the legit-empty set (length / tool_calls / content_filter / max_tokens / tool_use, open-sse/utils/streamReadiness.ts:158-164). open-sse/utils/streamHandler.ts:524-525 then returns exactly the string you pasted.

#9991 flagged the misleading test_status=active as an observability gap worth tracking; the discarded body at qwen-web.ts:203-204 is the same gap on the completion side.

The qwen3.8-max-preview line is a different thing and never left your machine. Note it has no [ProxyEgress] and no [STREAM] line at all, unlike the other three. It was refused before any network call by the live-catalog gate at src/sse/services/model.ts:352-359: when a provider's live catalog is authoritative, a model id absent from the synced catalog of an active connection is rejected up front. Your connection's synced catalog simply does not carry that id. Given the above it is moot, but it explains why that one entry in your log looks nothing like the others.

Practical read: qwen-web is not going to work through cookies, so the supported path is the Qwen API provider with a real API key. In #9991 another user linked a third-party workaround (encryptarun/qwen-api); I have not tested it and it is outside this project.

[backryun]

The model ID for qwen-3.8-max-preview has been changed to qwen-3.8-max.
I have already submitted a pull request regarding this change, and it is currently pending. #10226

[diegosouzapw]

Hey @yoursshadow50! Thanks for reporting this.

The Provider returned empty content error on qwen-web typically occurs when the web session cookie or token expires or gets challenged by anti-bot verification, returning an empty response body stream from the upstream web endpoint.

I traced the handler execution to open-sse/executors/qwen-web.ts:142.

Workaround / Fix steps:

1. Go to Dashboard -> Providers -> Qwen Web.
2. Refresh or re-authenticate your Qwen Web account credentials.
3. If using session cookies, extract fresh cookies from chat.qwenlm.ai in your browser.

Let me know if re-authenticating resolves the empty content stream for you!

[yoursshadow50]

no it not resolves still same error..........
{"level":30,"time":"2026-08-17T10:49:39.326Z","service":"omniroute","module":"sse","tag":"ROUTING","msg":"Provider: qwen-web, Model: qwen3.7-plus"}
{"level":30,"time":"2026-08-17T10:49:39.328Z","service":"omniroute","module":"sse","tag":"AUTH","msg":"session_key=input:sha256:b2e45... has no available affinity target"}
{"level":30,"time":"2026-08-17T10:49:39.328Z","service":"omniroute","module":"sse","tag":"AUTH","msg":"Using qwen-web account: 0af7b3e3..."}
{"level":30,"time":"2026-08-17T10:49:39.339Z","service":"omniroute","module":"sse","tag":"MODEL_TEST_ALL","providerId":"qwen-web","modelCount":1,"hasConnection":false,"respectRateLimit":true,"autoHideFailed":false,"msg":"Starting batch test for 1 model(s) on provider qwen-web"}
{"level":30,"time":"2026-08-17T10:49:39.340Z","service":"omniroute","module":"sse","tag":"HTTP","method":"POST","path":"/v1/chat/completions | qwen-web/qwen3.8-max-preview | 1 msgs","msg":"📥 POST /v1/chat/completions | qwen-web/qwen3.8-max-preview | 1 msgs"}
{"level":40,"time":"2026-08-17T10:49:39.342Z","service":"omniroute","module":"sse","tag":"CHAT","model":"qwen-web/qwen3.8-max-preview","msg":"Model 'qwen3.8-max-preview' is not available in the active live catalog for provider 'qwen-web'."}
{"level":30,"time":"2026-08-17T10:49:39.343Z","service":"omniroute","module":"sse","tag":"MODEL_TEST_ALL","providerId":"qwen-web","modelId":"qwen-web/qwen3.8-max-preview","latencyMs":3,"msg":"Tested qwen-web/qwen3.8-max-preview: error"}
{"level":30,"time":"2026-08-17T10:49:39.343Z","service":"omniroute","module":"sse","tag":"MODEL_TEST_ALL","providerId":"qwen-web","tested":1,"total":1,"stoppedEarly":false,"msg":"Batch test complete: 1/1 model(s)"}
[ProxyEgress] qwen-web/0af7b3e3 in=? out=54.145.250.53 proxy=direct status=success
[10:49:40] 📊 [USAGE] QWEN-WEB | in=284 | out=0 | account=0af7b3e3... (estimated)
[10:49:40] 🌊 [STREAM] QWEN-WEB | qwen3.7-max | 1221ms | error: Provider returned empty content
{"level":30,"time":"2026-08-17T10:49:40.542Z","service":"omniroute","module":"sse","tag":"MODEL_TEST_ALL","providerId":"qwen-web","modelId":"qwen-web/qwen3.7-max","latencyMs":1242,"msg":"Tested qwen-web/qwen3.7-max: error"}
{"level":30,"time":"2026-08-17T10:49:40.542Z","service":"omniroute","module":"sse","tag":"MODEL_TEST_ALL","providerId":"qwen-web","tested":1,"total":1,"stoppedEarly":false,"msg":"Batch test complete: 1/1 model(s)"}
[ProxyEgress] qwen-web/0af7b3e3 in=? out=54.145.250.53 proxy=direct status=success
[10:49:40] 📊 [USAGE] QWEN-WEB | in=284 | out=0 | account=0af7b3e3... (estimated)
[10:49:40] 🌊 [STREAM] QWEN-WEB | qwen3.7-plus | 1377ms | error: Provider returned empty content
{"level":30,"time":"2026-08-17T10:49:40.711Z","service":"omniroute","module":"sse","tag":"MODEL_TEST_ALL","providerId":"qwen-web","modelId":"qwen-web/qwen3.7-plus","latencyMs":1388,"msg":"Tested qwen-web/qwen3.7-plus: error"}
{"level":30,"time":"2026-08-17T10:49:40.711Z","service":"omniroute","module":"sse","tag":"MODEL_TEST_ALL","providerId":"qwen-web","tested":1,"total":1,"stoppedEarly":false,"msg":"Batch test complete: 1/1 model(s)"}
{"level":30,"time":"2026-08-17T10:49:41.021Z","service":"omniroute","module":"sse","tag":"MODEL_TEST_ALL","providerId":"qwen-web","modelCount":1,"hasConnection":false,"respectRateLimit":true,"autoHideFailed":false,"msg":"Starting batch test for 1 model(s) on provider qwen-web"}
{"level":30,"time":"2026-08-17T10:49:41.022Z","service":"omniroute","module":"sse","tag":"HTTP","method":"POST","path":"/v1/chat/completions | qwen-web/qwen3.8-max | 1 msgs","msg":"📥 POST /v1/chat/completions | qwen-web/qwen3.8-max | 1 msgs"}
{"level":30,"time":"2026-08-17T10:49:41.025Z","service":"omniroute","module":"sse","tag":"ROUTING","msg":"Provider: qwen-web, Model: qwen3.8-max"}
{"level":30,"time":"2026-08-17T10:49:41.026Z","service":"omniroute","module":"sse","tag":"AUTH","msg":"session_key=input:sha256:13217... has no available affinity target"}
{"level":30,"time":"2026-08-17T10:49:41.027Z","service":"omniroute","module":"sse","tag":"AUTH","msg":"Using qwen-web account: 0af7b3e3..."}
{"level":30,"time":"2026-08-17T10:49:41.094Z","service":"omniroute","module":"sse","tag":"MODEL_TEST_ALL","providerId":"qwen-web","modelCount":1,"hasConnection":false,"respectRateLimit":true,"autoHideFailed":false,"msg":"Starting batch test for 1 model(s) on provider qwen-web"}
{"level":30,"time":"2026-08-17T10:49:41.095Z","service":"omniroute","module":"sse","tag":"HTTP","method":"POST","path":"/v1/chat/completions | qwen-web/qwen3.6-plus | 1 msgs","msg":"📥 POST /v1/chat/completions | qwen-web/qwen3.6-plus | 1 msgs"}
{"level":40,"time":"2026-08-17T10:49:41.099Z","service":"omniroute","module":"sse","tag":"CHAT","model":"qwen-web/qwen3.6-plus","msg":"Model 'qwen3.6-plus' is not available in the active live catalog for provider 'qwen-web'."}
{"level":30,"time":"2026-08-17T10:49:41.099Z","service":"omniroute","module":"sse","tag":"MODEL_TEST_ALL","providerId":"qwen-web","modelId":"qwen-web/qwen3.6-plus","latencyMs":5,"msg":"Tested qwen-web/qwen3.6-plus: error"}
{"level":30,"time":"2026-08-17T10:49:41.099Z","service":"omniroute","module":"sse","tag":"MODEL_TEST_ALL","providerId":"qwen-web","tested":1,"total":1,"stoppedEarly":false,"msg":"Batch test complete: 1/1 model(s)"}
[ProxyEgress] qwen-web/0af7b3e3 in=? out=54.145.250.53 proxy=direct status=success
[10:49:42] 📊 [USAGE] QWEN-WEB | in=284 | out=0 | account=0af7b3e3... (estimated)
[10:49:42] 🌊 [STREAM] QWEN-WEB | qwen3.8-max | 1202ms | error: Provider returned empty content
{"level":30,"time":"2026-08-17T10:49:42.238Z","service":"omniroute","module":"sse","tag":"MODEL_TEST_ALL","providerId":"qwen-web","modelId":"qwen-web/qwen3.8-max","latencyMs":1216,"msg":"Tested qwen-web/qwen3.8-max: error"}
{"level":30,"time":"2026-08-17T10:49:42.238Z","service":"omniroute","module":"sse","tag":"MODEL_TEST_ALL","providerId":"qwen-web","tested":1,"total":1,"stoppedEarly":false,"msg":"Batch test complete: 1/1 model(s)"}
[HealthCheck] Skipping trae/hygtfrde45r6tgyubygvftr5t6 (refresh unsupported)

[pacocartones]

One note before you spend time re-capturing cookies: this exact failure was investigated in #9991 and closed as an upstream limitation — chat.qwen.ai sits behind Alibaba's anti-bot challenge, and the cookie-only web path cannot satisfy it, so a fresh cookie jar hits the same wall. That is also why the error reads "Provider returned empty content" instead of naming the challenge: qwen-web.ts:203-204 discards the upstream body before anything inspects it.

[diegosouzapw]

Thanks for digging up #9991, @pacocartones -- that's the right context. @yoursshadow50, this is confirmed as an upstream limitation: chat.qwen.ai's anti-bot challenge (x5sec/RGV587) blocks the cookie-only web path, so re-capturing cookies won't fix it -- it's not something OmniRoute can route around on the qwen-web connector. If you have an official Qwen API key, switching to the qwen (API) provider instead of qwen-web avoids this entirely.