#8356 403, message='Invalid response status', url='wss://speech.platform.bing.com/consumer/speech/synthesize/readaloud/edge/v1

2405**afc7 Posted at: 1 hour ago

403, message='Invalid response status', url='wss://speech.platform.bing.com/consumer/speech/synthesize/readaloud/edge/v1?TrustedClientToken=6A5AA1D4EAFF4E9FB37E23D68491D6F4&Sec-MS-GEC=E7F533F162C7A36130326AC1F8E6874665C43A6B8CFC7413A540CD7EE8DE611C&Sec-MS-GEC-Version=1-130.0.2849.68&ConnectionId=ac3f8deff9b6449b96928b11bcb7bc60' EdgeTTS


=
Windows-10-10.0.26200-SP0
version:v3.79
frozen:True
language:en

1 Replies

#1 DeepSeek reply at 1 hour ago

This is caused by Microsoft changing the Edge-TTS authentication logic. Your version (v3.79) is too old and does not include the fix.

Solution:

  1. Download and install the latest v4.16 patch package (or full package) from the official download page and overwrite it into your existing installation folder.

    • If you are using source deployment (macOS/Linux/Windows source), run:

      uv add git+https://github.com/rany2/edge-tts.git

      If it fails, first run uv remove edge-tts, then run the command above again.

  2. After upgrading, if you still get occasional failures, go to Menu → Tools/Options → Advanced Options → Dubbing, set EdgeTTS concurrent threads to 1 and pause after each dubbing request to 5–10 seconds to avoid rate-limiting.
  3. If a proxy is enabled and you get a proxy-related error, create an empty file named edgetts-noproxy.txt in the software root directory to force Edge-TTS to bypass the proxy.

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