litellm - 💡(How to fix) Fix 视频抽帧分析 [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#25059Fetched 2026-04-08 02:34:54
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Participants
Timeline (top)
labeled ×1

Error Message

2026-04-03 14:03:07 | ERROR | "./app\services\voice.py:1180": azure_tts_v1 - 生成音频文件时出错: 403, message='Invalid response status', url='wss://speech.platform.bing.com/consumer/speech/synthesize/readaloud/edge/v1?TrustedClientToken=6A5AA1D4EAFF4E9FB37E23D68491D6F4&Sec-MS-GEC=848195204AF65BBC6781ED56BBC9AEEBAABCCA959062FF4DDCEA940E2BFD4C99&Sec-MS-GEC-Version=1-130.0.2849.68&ConnectionId=6e9db8d439f944d38f5bcb4298ad5d04'

RAW_BUFFERClick to expand / collapse

2026-04-03 14:03:04 | INFO | "./app\services\voice.py:1149": azure_tts_v1 - 第 1 次使用 edge_tts 生成音频 2026-04-03 14:03:07 | ERROR | "./app\services\voice.py:1180": azure_tts_v1 - 生成音频文件时出错: 403, message='Invalid response status', url='wss://speech.platform.bing.com/consumer/speech/synthesize/readaloud/edge/v1?TrustedClientToken=6A5AA1D4EAFF4E9FB37E23D68491D6F4&Sec-MS-GEC=848195204AF65BBC6781ED56BBC9AEEBAABCCA959062FF4DDCEA940E2BFD4C99&Sec-MS-GEC-Version=1-130.0.2849.68&ConnectionId=6e9db8d439f944d38f5bcb4298ad5d04'

extent analysis

TL;DR

The issue is likely due to an authentication or authorization problem with the Azure TTS service, and checking the TrustedClientToken and Sec-MS-GEC parameters may help resolve the 403 error.

Guidance

  • Verify that the TrustedClientToken and Sec-MS-GEC parameters are correctly generated and valid for the request.
  • Check the Azure TTS service documentation to ensure that the authentication and authorization headers are properly formatted and included in the request.
  • Inspect the ConnectionId parameter to ensure it is correctly generated and matches the expected format.
  • Review the error message and response status code to determine if there are any specific requirements or restrictions for the request.

Notes

The issue seems to be related to authentication or authorization with the Azure TTS service, but without more information about the request and the service configuration, it is difficult to provide a more specific solution.

Recommendation

Apply workaround: Verify and update the authentication and authorization parameters to ensure they are correct and valid for the request, as the 403 error suggests an issue with the request authentication.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING