new latest version with latest endpoint have issues

[iamliaqateagle]

I added the most recent version to the app, but most requests are denied and there is no audio or data received issue. The previous version was working perfectly fine, but with the new endpoint, most of the time there is no audio reception issue. Is there a character limit or something wrong with it?

[rany2]

Can you check if this happens with 7.2.3?

[iamliaqateagle]

ok let me test and will update you soon

[mvanec]

Using edge-tts 7.2.3, I get this error response:

aiohttp.client_exceptions.WSServerHandshakeError: 401, message='Invalid response status', 
url='wss://api.msedgeservices.com/tts/cognitiveservices/websocket/v1?Ocp-Apim-Subscription-Key=6A5AA1D4EAFF4E9FB37E23D68491D6F4&ConnectionId=7b4bd900c88f4caea14847894e792405&Sec-MS-GEC=533AF88EB3C7171D06B870C40855017A72A55D5FF17693C80255176B713ABD29&Sec-MS-GEC-Version=1-140.0.3485.14'

I was able to generate the error using this test script:

import asyncio
import edge_tts

async def test():
    communicate = edge_tts.Communicate("¡Hola, mundo!", "es-MX-DaliaNeural")
    with open("test.mp3", "wb") as f:
        async for chunk in communicate.stream():
            if chunk["type"] == "audio":
                f.write(chunk["data"])

asyncio.run(test())

I'm running Python 3.13.5.

When I backlevel to edge-tts 7.2.1, the script works without any errors.

[aizimuji]

why update the API , since the old still works

I am using 7.2.1, still works

[missdeer]

7.2.3 works for me, but 7.2.1 not

[RPG-fan]

This may help you.

"""
Diagnostic tool for Edge TTS authentication issue.

This script prints the current and proposed (old) endpoints for the edge-tts library.
This can be used to diagnose issues related to the 401 authentication error that
started appearing after the library was updated to use new endpoints.

The issue is tracked here: https://github.com/rany2/edge-tts/issues/416
The PR that introduced the new endpoints is here: https://github.com/rany2/edge-tts/pull/412
"""
import edge_tts.constants

def print_diagnostic_info():
    """
    Prints the current and proposed (old) endpoints for edge-tts.
    """
    
    print("--- Current Edge TTS Endpoints ---")
    print(f"BASE_URL: {edge_tts.constants.BASE_URL}")
    print(f"WSS_URL: {edge_tts.constants.WSS_URL}")
    print(f"VOICE_LIST: {edge_tts.constants.VOICE_LIST}")
    
    print("\n--- Proposed (Old) Edge TTS Endpoints ---")
    
    OLD_BASE_URL = "speech.platform.bing.com/consumer/speech/synthesize/readaloud"
    TRUSTED_CLIENT_TOKEN = "6A5AA1D4EAFF4E9FB37E23D68491D6F4"
    
    OLD_WSS_URL = f"wss://{OLD_BASE_URL}/edge/v1?TrustedClientToken={TRUSTED_CLIENT_TOKEN}"
    OLD_VOICE_LIST = f"https://{OLD_BASE_URL}/voices/list?trustedclienttoken={TRUSTED_CLIENT_TOKEN}"
    
    print(f"OLD_BASE_URL: {OLD_BASE_URL}")
    print(f"OLD_WSS_URL: {OLD_WSS_URL}")
    print(f"OLD_VOICE_LIST: {OLD_VOICE_LIST}")

if __name__ == "__main__":
    print_diagnostic_info()

[lamncn]

Is there any new update? I can use 2 versions fine now.

[numericOverflow]

Same issue here for me. For now I've downgraded to latest working ver for me
WORKS: 7.2.1
ERRORS: 7.2.2 & 7.2.3

@RPG-fan - I ran your diagnostic script (thanks for that, BTW), but not sure what to do with what it's telling me. Do you want to see the output, it provides or...? Sorry if that's an ignorant question :)

[rany2]

@numericOverflow That script isn't all that useful. We're aware of the change of endpoint URL. It doesn't do much of anything.

[numericOverflow]

@rany2 got it, thanks for the clarification.

[RPG-fan]

Same issue here for me. For now I've downgraded to latest working ver for me WORKS: 7.2.1 ERRORS: 7.2.2 & 7.2.3

@RPG-fan - I ran your diagnostic script (thanks for that, BTW), but not sure what to do with what it's telling me. Do you want to see the output, it provides or...? Sorry if that's an ignorant question :)

Copy the new endpoints from the output and do a codebase search for a match. Replace the new ones found in the search with the old endpoints the script returned and save the file. Should only take a minute or two (I didn't want to automate the fix in case there were subtle differences in the installed os). Been using it successfully with the old endpoints in place for ~2 weeks now.

[tritiumoxide]

Copy the new endpoints from the output and do a codebase search for a match. Replace the new ones found in the search with the old endpoints the script returned and save the file. Should only take a minute or two (I didn't want to automate the fix in case there were subtle differences in the installed os). Been using it successfully with the old endpoints in place for ~2 weeks now.

If you're going to revert to the old endpoints in the latest codebase, I'd roll back the Edge version in the code as well. Announcing yourself as the latest Edge that should be using the new endpoints while still using the old ones likely just makes your traffic way more suspicious, raising red flags with MS and potentially making this whole endeavor more precarious for all of us.

@rany2 Is there anything we can do to help test the new endpoints? I get nothing but 401 errors with them. Could it be a region issue? Do we need to extract our own API key from a live Edge install? While I suspect we'll probably be fine for a while on the old endpoints (I doubt they'd EOL any of those Edge versions all that soon) it would be nice to be able to get things working with the new ones before the old ones disappear or get blocked.

[rany2]

@tritiumoxide I'm not very sure why this is happening. It hasn't occurred for me so it might very well be a regional issue.

[kostianu4]

also happened with me today: errors 500 and 401.
responses become very short before error. I thought it's some IP ban, vpn make it a bit longer, but then also error, so if it was ban, VPN should fix, but no.

downgrade to 7.2.1 fixed the issue, thanks for recommendations.

[andresayac]

@kostianu4 @rany2 @tritiumoxide @numericOverflow @missdeer

Could you please watch this video? The idea is to verify the region on the endpoint so we can troubleshoot. I look forward to your help if you need it.

Video Guide
https://httptoolkit.com/