#8754 Error during TTS dubbing stage [Edge-TTS (Free)] Dubbing failed completely:403, message='Invalid response status', url='

194.33**2 Posted at: 24 minutes ago

Error during TTS dubbing stage [Edge-TTS (Free)] Dubbing failed completely:403, message='Invalid response status', url='wss://speech.platform.bing.com/consumer/speech/synthesize/readaloud/edge/v1?TrustedClientToken=6A5AA1D4EAFF4E9FB37E23D68491D6F4&ConnectionId=05634c86a4d04d2fb89650019cb0221e&Sec-MS-GEC=5409D66416F2A67AA5E42E94C2F55583B3A104EF32A06EF94C22C381C45963B4&Sec-MS-GEC-Version=1-143.0.3650.75'
all_voices={'en-SG-WayneNeural'}
Traceback (most recent call last):

File "videotrans\task\job.py", line 35, in run

File "videotrans\task\job.py", line 155, in process_task

File "videotrans\task\_stage_dubbing.py", line 24, in dubbing

File "videotrans\task\_stage_dubbing.py", line 101, in _tts

File "videotrans\tts\__init__.py", line 122, in run

File "videotrans\tts\_base.py", line 95, in run

File "asyncio\runners.py", line 44, in run

File "asyncio\base_events.py", line 649, in run_until_complete

File "videotrans\tts\_edgetts.py", line 235, in _exec

videotrans.configure.excepts.DubbingSrtError: Dubbing failed completely:403, message='Invalid response status', url='wss://speech.platform.bing.com/consumer/speech/synthesize/readaloud/edge/v1?TrustedClientToken=6A5AA1D4EAFF4E9FB37E23D68491D6F4&ConnectionId=05634c86a4d04d2fb89650019cb0221e&Sec-MS-GEC=5409D66416F2A67AA5E42E94C2F55583B3A104EF32A06EF94C22C381C45963B4&Sec-MS-GEC-Version=1-143.0.3650.75'
all_voices={'en-SG-WayneNeural'}
trk=[TransCreate]: uuid='72e0c534ca', proxy_str=None, cfg=[TaskCfgVTT]当前工作模式: 翻译视频 批量翻译模式
原始输入文件名: C:/Users/pbank/Мой диск ([email protected])/Shipping/CRM_NEW/Odoo_instructons/User_instructions/20_Filters open Area and Date.mp4,
输出结果保存到文件夹: C:/Users/pbank/Мой диск ([email protected])/Shipping/CRM_NEW/Odoo_instructons/User_instructions/_video_out/20_Filters open Area and Date-mp4,
临时文件夹: D:/Install/Video_translator/win-pyvideotrans-v4.15-1/tmp/33672/72e0c534ca
已选 清理已存在
未启用CUDA加速
未选 降噪
STT Service:faster-whisper(Built-in), large-v3-turbo, 发音语言: Russian,
TranslateSrt:Google Translate (Free),原始语言:Russian,目标语言:English, 已选 SendSRT
TTS Service:Edge-TTS (Free), 角色:Wayne(Male/SG), 配音语言:English, 未选 二次语音识别
音量:+0%, 语速:+0%, 已选 音频加速, 未选 视频慢速
已选 移除每条字幕配音开头和结尾静音缓冲
静音移除力度: default
字幕: Hard Subtitles
已选 仅输出mp4, precent=15, hasend=False, should_recogn=True, should_trans=True, should_dubbing=True, should_hebing=True, is_copy_video=True, video_codec_num=264, ignore_align=False, is_audio_trans=False, clone_ref='', should_recogn2=False, do_diarize=False


=
system:Windows-10-10.0.26200-SP0
version:v4.15
frozen:True
language:en_US
root_dir:D:/Install/Video_translator/win-pyvideotrans-v4.15-1

1 Replies

#1 DeepSeek reply at 23 minutes ago

The most likely cause is that Microsoft has changed the authentication logic of the free Edge-TTS interface. The Sec-MS-GEC signature mechanism has been updated, so calls sent by the old version (v4.15) are rejected with a 403 response.

Solution (in order):

  1. Upgrade to v4.16 or later. The v4.16 update already fixes the Edge-TTS 403 error. Download the latest patch package and overwrite all files in the old version, including the sp.exe, _internal folder, and videotrans folder. Your JSON configuration files will not be lost.
  2. If you are deploying from source, run:
    uv add git+https://github.com/rany2/edge-tts.git
    If that fails, run uv remove edge-tts first, then run the command above again.
  3. If you still get a 403 occasionally after upgrading, it means you are being rate-limited. Open Menu → Tools/Options → Advanced Options → Dubbing Settings, set EdgeTTS Max Concurrency to 1, and set Post-Dubbing Delay (s) to 5~10.
  4. If the error is caused by the proxy, create an empty file named edgetts-noproxy.txt in the software root directory (D:/Install/Video_translator/win-pyvideotrans-v4.15-1/) to force Edge-TTS to bypass the proxy.

Additional risk (not the direct cause of this error, but it will cause failures):
Your video path C:/Users/pbank/Мой диск ([email protected])/.../20_Filters open Area and Date.mp4 contains Cyrillic characters, spaces, parentheses, and @. The later stages of FFmpeg muxing are very prone to crashing on this kind of path. It is recommended to move and rename the video to a shallow directory with only English letters and digits, for example D:/videos/video1.mp4.

Please refer to the related documentation:

Thinking...
Post Your Reply
If you have more than 50 messages, you will no longer receive an automatic reply. Please ask a new question!
Open source and free maintenance is not easy. If this project is helpful to you, please consider making a small donation to help the project continue to maintain and update.

Dondate via ko-fi.com

Related resource