search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.31k stars 21.5k forks source link

Configure Speech containers - setting HTTP proxy can lead to broken text-to-speech and speech-to-text #112998

Closed msehnout closed 8 months ago

msehnout commented 1 year ago

Hi,

I stumbled upon an issue with the HTTP Proxy settings: https://learn.microsoft.com/en-us/azure/ai-services/speech-service/speech-container-configuration#http-proxy-credentials-settings

The proxy does not support HTTP/2 and I'm responsible only for deploying the Azure containers, not the proxy. This resulted in an issue when calling TTS:

details='Speech synthesis canceled: CancellationReason.Error
Details: TTS request failed: Internal service error (500). Error Details:  Synthesis failed. StatusCode: Internal, Details: Error starting gRPC call. HttpRequestException: Requesting HTTP version 2.0 with version policy RequestVersionOrHigher while unable to establish HTTP/2 connection.. Please check request details.'

(same for STT, but there was no error message to copy)

As I was unable to change the proxy configuration, I had to find an alternative solution. After few hours of investigation (~struggling), I found the root cause. The processes inside of the container communicate over localhost and they used the proxy as well even though there is no need for it. Setting NO_PROXY=localhost,127.0.0.1 in the environment fixed the issue.

I think it would be nice if the docs included a note about setting NO_PROXY for localhost. It is kind of a trap for people that need to deploy the containers into old corporate environments.

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

AjayBathini-MSFT commented 1 year ago

@msehnout Thanks for your feedback! We will investigate and update as appropriate.

Naveenommi-MSFT commented 1 year ago

Hi @msehnout Thank you for bringing this to our attention. I'm sorry to hear you have issues with the HTTP Proxy settings while deploying Azure containers. I understand that you were unable to adjust the proxy setup and had to find an alternative solution.

Based on your experience, you advise that the documentation add a note regarding setting NO_PROXY for localhost. I will forward this input to the appropriate team for consideration in future documentation updates.

Naveenommi-MSFT commented 1 year ago

@eric-urban Could you please review add comments on this, update as appropriate.

Naveenommi-MSFT commented 1 year ago

@msehnout Thank you for bringing this to our attention. I've delegated this to content author @eric-urban, who will review it and offer their insightful opinions.

msehnout commented 1 year ago

Perfect :+1:

eric-urban commented 8 months ago

@msehnout - Got it! We have an internal work item for tracking, so I'll close this GitHub issue. Thanks.

eric-urban commented 8 months ago

please-close