QWEN WEB RETURN EMPTY CONTENT ERROR

[yoursshadow50]

qwen-web/2b75d25b in=? out=3.228.31.30 proxy=direct status=success
[08:37:37] 📊 [USAGE] QWEN-WEB | in=289 | out=0 | account=2b75d25b... (estimated)
[08:37:37] 🌊 [STREAM] QWEN-WEB | qwen3.8-max-preview | 1167ms | error: Provider returned empty content

EVEN I USE ALL MODELS ...THE ERROR ARE SAME LIKE THAT

[diegosouzapw]

Hey @yoursshadow50! Let me help debug the empty content issue with Qwen Web.

The executor has been updated to use Qwen's v2 API (/api/v2/chats/new + /api/v2/chat/completions) since the v1 endpoint was retired. The v2 flow requires a valid browser cookie jar from a logged-in session at chat.qwen.ai.

First check: do you have valid Qwen Web credentials configured?

The Qwen Web provider needs a full cookie header captured from chat.qwen.ai after login. Go to Dashboard → Providers → Qwen Web and check:

1. Do you have a valid Cookie header pasted from your browser session?
2. Is the token field populated?

If credentials are set: the empty content usually means the upstream session expired. Qwen's v2 cookie tokens have a limited lifetime (typically 1-3 days for the free tier). Re-capture the cookies from chat.qwen.ai (after logging in again) and update the provider settings.

The log line you shared confirms the pattern:

[STREAM] QWEN-WEB | qwen3.8-max-preview | 1167ms | error: Provider returned empty content

The request reached Qwen successfully (1167ms, no 502/504) but the stream produced zero content tokens -- classic sign of an expired session that Qwen accepted but no longer authorizes to generate.

Try:

1. Log out and back into chat.qwen.ai in your browser
2. Re-capture the full Cookie header and token from developer tools
3. Update the Qwen Web provider settings in OmniRoute
4. Retry

If the problem persists after a fresh session capture, reply here with the provider ID (obfuscated account prefix) and I will check if there was an upstream API change.

[ccmks]

I got same error too. After fresh session, capture cookie and put it. Run test, still getting "Provider returned empty content"

It was working fine several days ago

[diegosouzapw]

Thanks @ccmks for the data point — two users with the same error after fresh cookies suggests something changed upstream.

@yoursshadow50 ^ this confirms the issue is not specific to one account/session.

What I suspect: Qwen's v2 API may have rolled a breaking change (the SPA version pin 0.2.66 in the executor may be out of date, or the WAF/baxia headers evolved).

To investigate I would need:

1. The exact HTTP status code when the executor hits the upstream (check OmniRoute logs: tail -f ~/.omniroute/logs/*.log or check the dashboard log viewer)
2. Whether the /api/v2/chats/new call succeeds (the executor logs errors from the chat creation step)
3. If you are comfortable with curl, disable OmniRoute's masking temporarily and try the upstream directly:

   curl -v -X POST "https://chat.qwen.ai/api/v2/chats/new" \
     -H "Cookie: <your-cookie>" \
     -H "User-Agent: Mozilla/5.0 ..."

In the meantime, a workaround: try using the Qwen API provider (not Qwen Web) with an API key from the Qwen developer portal, if you have one. The Web provider relies on the consumer chat session, which is inherently less stable.

If anyone can share sanitized logs showing the upstream response (HTTP status + first 500 chars of the response body), I can trace whether a protocol change needs shipping.

[diegosouzapw]

@ccmks @yoursshadow50 -- still hitting "Provider returned empty content" on the latest version? Otherwise I'll close this in 7 days for inactivity (the upstream v2/WAF investigation continues in #10361 / #9991 context).

[yoursshadow50]

still same error even i use omni v3.8.50 .......... ,"service":"omniroute","module":"sse","tag":"CHAT","model":"qwen-web/qwen3.7-max","msg":"Model 'qwen3.7-max' is not available in the active live catalog for provider 'qwen-web'."}
{"level":30,"time":"2026-08-24T17:34:21.124Z","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-24T17:34:21.136Z","service":"omniroute","module":"sse","tag":"ROUTING","msg":"Provider: qwen-web, Model: qwen3.8-max"}
{"level":30,"time":"2026-08-24T17:34:21.143Z","service":"omniroute","module":"sse","tag":"AUTH","msg":"session_key=input:sha256:60543... has no available affinity target"}
{"level":30,"time":"2026-08-24T17:34:21.143Z","service":"omniroute","module":"sse","tag":"AUTH","msg":"Using qwen-web account: ***..."}
{"level":30,"time":"2026-08-24T17:34:21.147Z","service":"omniroute","module":"sse","tag":"ALIAS","msg":"Model alias applied: qwen3.8-max → qwen3.8-max-preview"}
[17:34:22] 📊 [USAGE] QWEN-WEB | in=284 | out=0 | account=d36ced28... (estimated)
[17:34:22] 🌊 [STREAM] QWEN-WEB | qwen3.8-max | 1218ms | error: Provider returned empty content

AND WHY THIS URL CONTINOUSLY CHANGING THE COOKIE ... Request URL
https://chat.qwen.ai/api/v2/notifications/latest?type=memory

[ccmks]

@diegosouzapw how do I upgrade to version 3.8.50? I tried to run the install command still getting 3.8.49

[diegosouzapw]

@ccmks Upgrade path: npm i -g omniroute@latest, then verify with omniroute --version. If it still reports 3.8.49, clear npm's cache (npm cache clean --force) and reinstall -- stale caches are the usual cause of version pinning.

@yoursshadow50 Thanks for re-testing on 3.8.50. Two separate things in your log: the qwen3.7-max not available in active live catalog line means that connection's synced catalog is stale -- run Dashboard -> Providers -> Qwen Web -> Import/Auto-Sync. The underlying empty content remains the upstream v2/WAF issue tracked via #9991/#10361 context. Leaving this open since you're both still hitting it.