#8352 All error for edge-tts 403, message='Invalid response status', url='wss://speech.platform.bing.com/consumer/speech/synt

2001**6b60 Posted at: 1 hour ago

All error for edge-tts 403, message='Invalid response status', url='wss://speech.platform.bing.com/consumer/speech/synthesize/readaloud/edge/v1?TrustedClientToken=6A5AA1D4EAFF4E9FB37E23D68491D6F4&ConnectionId=367fa358be5c4651b34c47bd7c500b71&Sec-MS-GEC=F89C586055529AE9C01B3E220EF3D887C2FDA6257737DBB942E47C236D479C19&Sec-MS-GEC-Version=1-143.0.3650.75'
Traceback (most recent call last):
File "videotrans\tts\_base.py", line 84, in run
RuntimeError: no running event loop

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "videotrans\task\only_one.py", line 86, in run
File "videotrans\task\trans_create.py", line 667, in dubbing
File "videotrans\task\trans_create.py", line 990, in _tts
File "videotrans\tts\__init__.py", line 192, in run
File "videotrans\tts\_base.py", line 88, in run
File "asyncio\base_events.py", line 649, in run_until_complete
File "videotrans\tts\_edgetts.py", line 200, in _exec
videotrans.configure.excepts.DubbingSrtError: All error for edge-tts 403, message='Invalid response status', url='wss://speech.platform.bing.com/consumer/speech/synthesize/readaloud/edge/v1?TrustedClientToken=6A5AA1D4EAFF4E9FB37E23D68491D6F4&ConnectionId=367fa358be5c4651b34c47bd7c500b71&Sec-MS-GEC=F89C586055529AE9C01B3E220EF3D887C2FDA6257737DBB942E47C236D479C19&Sec-MS-GEC-Version=1-143.0.3650.75'

cfg=[TaskCfgVTT]当前工作模式: 翻译视频或音频单视频模式
原始输入文件名: D:/0-video de Manhwa/quiero una familia/1-29.quiero una familia.mp4,
输出结果保存到文件夹: C:/Users/Rafael Hilario/Desktop/0-video de Manhwa/doblaje/1-29.quiero una familia-mp4,
临时文件夹: C:/doblaje/tmp/16796/ef1c7eca5b
未选清理已存在
已选启用CUDA加速
未选降噪
ASR Channel:faster-whisper(LocalBuilt-in), model_name: large-v3-turbo, 发音语言: Spanish, 断句方式:默认断句
Trans Channel:M2M100(LocalBuilt-in),原始语言:Spanish,目标语言:English, 已选 Send SRT
Dubb Channel:Edge-TTS(Free), 角色:WilliamMultilingual(Male/AU), 配音语言:English, 未选二次语音识别
音量:+50%, 语速:+0%, 未选音频加速, 已选视频慢速
字幕: No Subs
已选仅输出mp4
代理地址:

=
system:Windows-10-10.0.26200-SP0
version:v4.03
frozen:True
language:en
root_dir:C:/doblaje

#1 DeepSeek reply at 1 hour ago

This is the known Edge-TTS 403 blocking caused by Microsoft changing the token validation on its free Edge-TTS endpoint. Your version v4.03 is too old and uses the obsolete request logic, so the server rejects every connection with Invalid response status.

Fix

Upgrade to v4.16 — this is the definitive fix; v4.16 rebuilds the Edge-TTS 403 handling.
- Download the full package (~2.7 GB) or the patch (~360 MB) from https://pyvideotrans.com/downpackage and fully overwrite your existing install folder C:/doblaje (overwrite all files/folders, especially sp.exe and _internal).
- Your config files in videotrans/ (params.json, cfg.json) are preserved and can be overwritten safely.
If you run a source deployment (not your case, but for reference), run:
```
uv add git+https://github.com/rany2/edge-tts.git
```
If it errors, first run uv remove edge-tts, then re-run the above.

After upgrading, to avoid further rate-limit/blocking

Go to Menu → Tools/Options → Advanced Options → Subtitle Dubbing.
Set EdgeTTS concurrent dubbing threads to 1.
Set Pause (s) after each dubbing request to 5–10.
If you use a VPN/proxy and still get connection errors, create an empty file named edgetts-noproxy.txt in the software root directory (C:/doblaje) to force Edge-TTS to bypass the proxy.

Note on your current task setup

Your config shows proxy address is empty and Audio speedup is unchecked while Slow video is checked — after upgrading, re-enable Audio speedup for better alignment, and ensure Clear Output is checked when re-running the same video.

Also consider a fallback TTS channel if Edge-TTS remains unstable: Qwen3-TTS(内置), OmniVoice-TTS, or Confucius-TTS (all support English).

#8352 All error for edge-tts 403, message='Invalid response status', url='wss://speech.platform.bing.com/consumer/speech/synt

1 Replies

Please refer to the relevant documentation:

Post Your Reply

Related resource