#8301 Dubbing failed completely:403, message='Invalid response status', url='wss://speech.platform.bing.com/consumer/speech/sy

187.13**1 Posted at: 1 hour ago

Dubbing failed completely:403, message='Invalid response status', url='wss://speech.platform.bing.com/consumer/speech/synthesize/readaloud/edge/v1?TrustedClientToken=6A5AA1D4EAFF4E9FB37E23D68491D6F4&ConnectionId=b1fd4d12f4ec41b2bc39f6448471f6d1&Sec-MS-GEC=A2DCDE93AD20562154F00022AAD1CF4BA8B37A5E485A1B8E8CA88D6FFECDA3BB&Sec-MS-GEC-Version=1-143.0.3650.75'
all_voices={'pt-BR-AntonioNeural'}
Traceback (most recent call last):
File "videotrans\task\only_one.py", line 107, in run
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 118, in run
File "videotrans\tts\_base.py", line 92, 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 228, 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=b1fd4d12f4ec41b2bc39f6448471f6d1&Sec-MS-GEC=A2DCDE93AD20562154F00022AAD1CF4BA8B37A5E485A1B8E8CA88D6FFECDA3BB&Sec-MS-GEC-Version=1-143.0.3650.75'
all_voices={'pt-BR-AntonioNeural'}

cfg=[TaskCfgVTT]当前工作模式: 翻译视频 单视频模式
原始输入文件名: D:/CETP/CETP/Module 9 (Attack on ETW)/106 - ETW_UserMode hide01.ir.mp4,
输出结果保存到文件夹: D:/CETP/CETP/Module 9 (Attack on ETW)/D/106 - ETW_UserMode hide01.ir-mp4,
临时文件夹: C:/Users/JOHN/Documents/DUBLADOR/win-pyvideotrans-v4.13-1/tmp/16348/2bdc5eaf43
已选 清理已存在
已启用CUDA加速
未选 降噪
STT Service:faster-whisper(Built-in), large-v3-turbo, 发音语言: English, 断句方式:默认断句
TranslateSrt:Microsoft Translate (Free),原始语言:English,目标语言:Portuguese (Brazilian), 已选 SendSRT
TTS Service:Edge-TTS (Free), 角色:Antonio(Male/BR), 配音语言:Portuguese (Brazilian), 已选 二次语音识别
音量:+0%, 语速:-10%, 未选 音频加速, 已选 视频慢速
字幕: No Subtitles
已选 仅输出mp4
video_duration_ms=876866


=
system:Windows-10-10.0.19045-SP0
version:v4.13
frozen:True
language:en_US
root_dir:C:/Users/JOHN/Documents/DUBLADOR/win-pyvideotrans-v4.13-1

1 Replies

#1 DeepSeek reply at 1 hour ago

This is the known Microsoft Edge-TTS authentication failure (HTTP 403). Microsoft changed the token/validation logic of its free Edge-TTS endpoint; Edge-TTS versions bundled with v4.13 and earlier no longer pass the handshake, so every dubbing request is rejected regardless of voice or language.

Fix:

  1. Upgrade to v4.16 (required for the pre-packaged Windows build). Download the v4.16 full package (~2.7GB) or the v4.16 patch (~360MB) from https://pyvideotrans.com/downpackage and fully overwrite your existing directory (win-pyvideotrans-v4.13-1). Do not copy only sp.exe; all files and the _internal / videotrans folders must be replaced. If problems persist after overwriting, search for __pycache__ inside _internal and delete all found copies, then overwrite again.
  2. Source deployment (macOS/Linux/Windows source) alternative to step 1: run
    uv add git+https://github.com/rany2/edge-tts.git
    If that errors, run uv remove edge-tts first, then repeat the command.
  3. Reduce request pressure (recommended even after upgrading): Menu → Tools/Options → Advanced Options → Dubbing, set Concurrent dubbing threads (EdgeTTS concurrency) to 1 and Pause after each dubbing request to 5–10 seconds.
  4. If you use a proxy/VPN: create an empty file named edgetts-noproxy.txt in the software root directory (same folder as sp.exe) to force Edge-TTS to bypass the proxy. A dirty proxy IP can also trigger 403.
  5. Temporary workaround for this task: switch TTS Service to another free/local channel (e.g., gTTS, or a built-in clone-capable channel such as Qwen3-TTS / OmniVoice) so the job can complete while you upgrade.

Note: since your selected subtitle type is No Subtitles plus Secondary STT was checked — after upgrading, re-run with Clear Output enabled so the previously failed dubbing cache is not reused.

Please refer to the 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