API Key for german speech to text containers not working anymore

ta 20 Reputation points
2024-01-22T09:38:15.3933333+00:00

Hi there,

this night our speech to text containers crashed and are since then not properly restarting. According to the container logs it seems that the API Key is not working properly anymore. Weirdly, the same key is still working when using the cloud speech to text services.

Any suggestions or ideas? Is this a known problem? Apparently during last the Azure KeyVault had a malfunction?

This incident is affecting our production environment, so a quick reply would be appreciated.

Logs:

File: Start API connection
API Key may be mismatched for the following reason: [System.Net].Http.HttpConnectionResponseContent
fail: Microsoft.CloudAI.Containers.Http.CloudClient[0]
Container is not in a valid state. Subscription validation failed with status 'Mismatch'. You have provided an API Key or endpoint for the different kind of cognitive services resource. Find your API key and service region under Keys and Endpoint at your Azure Cognitive Services resource blade in the Azure Portal. For more information please visit https://aka.ms/cscontainers-faq.

Azure AI Speech
Azure AI Speech
An Azure service that integrates speech processing into apps and services.
1,713 questions
Azure Container Instances
Azure Container Instances
An Azure service that provides customers with a serverless container experience.
700 questions
Accepted answer
  1. navba-MSFT 24,270 Reputation points Microsoft Employee
    2024-01-24T08:32:58.67+00:00

    @ta We appreciate your patience on this. Here is the root cause for the issue:

    Cause:
    All the users who try to use the de-DE on-prem speech-to-text container got impacted with this issue. We could see this message in container logs: Service responded with error message: This container image is expired. The cause was due to the key that encrypts the de-de model is expired. I was able to repro the same issue using this container. .
    Fix:
    We had reached out to the Product Group team and they have mitigated this issue after extending the lifetime of the key.
    .
    You can try now again and it should work fine.

    **
    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    3 people found this answer helpful.
    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.