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

88.227* Posted at: 4 days ago 👁30

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


=
system:Windows-10-10.0.19045-SP0
version:v3.89
frozen:True
language:en
root_dir:C:/Users/User/Desktop/Business/AI

1 Replies

This error indicates a connection issue with the Microsoft Edge-TTS service, likely due to network restrictions, regional blocking, or a temporary service outage.

To resolve this, please try the following steps in order:

  1. Check Your Network Connection: Ensure you have a stable internet connection. If you are using a VPN or proxy, try disabling it temporarily to see if it resolves the issue.
  2. Verify Regional Availability: The Edge-TTS service may be blocked or unstable in certain regions. If you are in a region where Microsoft services are restricted, you will need to use a different TTS service.
  3. Switch to an Alternative TTS Service: In the main interface of pyVideoTrans, go to the "Voiceover (TTS)" section (Line 4) and select a different, preferably local, TTS engine.

    • Recommended Free Local Options: VITS-cnen or piper-tts.
    • If you need online service: Try Azure TTS (requires an API key) or other available online APIs you have configured.
  4. Adjust Advanced Settings (if using Edge-TTS): If you must use Edge-TTS, go to Tools -> Options -> Advanced Options. In the "Voiceover Adjustments" section, reduce the "Concurrent voiceover threads" to 1 and increase the "Pause after voiceover (seconds)" to 5 or higher to reduce request frequency.

Since the error is a 403 (Forbidden) on a WebSocket connection to speech.platform.bing.com, the most likely cause is network-level blocking. Switching to a local TTS engine is the most reliable solution.

Please refer to the documentation for more details:

Post Your Reply