Immutable solution version
DashScope realtime ASR: error ladder from websocket refusal to silent transcripts
Complete solution
DashScope realtime ASR: error ladder from websocket refusal to silent transcripts. client handshake failure means the relay or proxy is broken: wrong scheme, a thrown exception, or upstream refusal. Use when hitting this exact issue with DashScope realtime ASR. Not for unrelated errors or different features.
TL;DR
Client handshake failure means the relay or proxy is broken: wrong scheme, a thrown exception, or upstream refusal.
The error
error ladder from websocket refusal to silent transcriptsFix
Client handshake failure means the relay or proxy is broken: wrong scheme, a thrown exception, or upstream refusal. Expected: you can confirm this matches your situation.
Re-run the original operation and confirm the error is gone. Expected: no error, normal output.
When to use
- You hit this exact error with DashScope realtime ASR.
- The symptom matches: error ladder from websocket refusal to silent transcripts.
When NOT to use
- A different error message from DashScope realtime ASR; the cause here is specific to this error.
- Unrelated DashScope realtime ASR issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.
Compatibility
Reported against DashScope realtime ASR. Source: https://github.com/mhosseinab/skills/blob/HEAD/qwen-asr-realtime/SKILL.md.
Variant phrasings
error ladder from websocket refusal to silent transcripts
Why it happens
Realtime speech errors appear in a fixed order. Each layer names the next thing to fix, so climb the ladder instead of guessing.
Edge cases
- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.
Source
https://github.com/mhosseinab/skills/blob/HEAD/qwen-asr-realtime/SKILL.md
Evidence
Source: Realtime speech errors appear in a fixed order. Each layer names the next thing to fix, so climb the ladder instead of guessing.
Verified resolution: [mhosseinab/skills]: client handshake failure means the relay or proxy is broken: wrong scheme, a thrown exception, or upstream refusal. Upstream refused websocket with status 4xx is a URL, path, or key problem at DashScope: 401 or 403 means the key or a wrong-region key, 404 means the wrong path. ModelNotFound is a region or catalog mismatch, and AccessDenied is usually a region mismatch for legacy models. If the session is created but no transcripts arrive, check the audio path: 16 kHz mono PCM16, Base64-in-JSON not binary, and VAD threshold and silence settings. Verify credentials and endpoint independently with a minimal script before debugging app code.
Source URL: https://github.com/mhosseinab/skills/blob/HEAD/qwen-asr-realtime/SKILL.md
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_fe1BXQGGXq2gam9Op7lOYg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">DashScope realtime ASR: error ladder from websocket refusal to silent transcripts <span>— Vectle</span></a>