CLI 0.80.0 -> LiteLLM 1.80.11 -> Azure OpenAI -> gpt-5.1-codex-max - The encrypted content could not be verified
What version of Codex is running?
codex-cli 0.80.0
What subscription do you have?
Azure MSDN
Which model were you using?
gpt-5.1-codex-max
What platform is your computer?
Linux 6.18.3-200.fc43.x86_64 x86_64 unknown
What issue are you seeing?
{"error":{"message":"litellm.BadRequestError: litellm.ContentPolicyViolationError: litellm.ContentPolicyViolationError: AzureException - {\n \"error\": {\n \"message\": \"The encrypted content gAAA...ehIc
could not be verified.\",\n \"type\": \"invalid_request_error\",\n \"param\": null,\n \"code\": \"invalid_encrypted_content\"\n }\n}\nmodel=gpt-5.1-codex-max. content_policy_fallback=None.
fallbacks=None.\n\nSet 'content_policy_fallback' - https://docs.litellm.ai/docs/routing#fallbacks. Received Model Group=gpt-5.1-codex-max\nAvailable Model Group
Fallbacks=None","type":null,"param":null,"code":"400","provider_specific_fields":{"innererror":null}}}
What steps can reproduce the bug?
Uploaded thread: 019bab3a-c0e8-7c00-8ea1-b3afaaf8b3ce
What is the expected behavior?
No error and completes the requested task in a timely manner
Additional information
_No response_
7 Comments
This looks like an Azure issue. Have you reported this to the Azure team?
Do you suspect that it's a regression in Codex? Has this worked in the past for you? Does the problem go away if you downgrade to an older version of Codex?
This is my first time using codex. I installed it, set the environment variables and invoked it in my project directory. Did a search and found issues with similar descriptions and used the
/feedbackas you posted here https://github.com/openai/codex/issues/8120#issuecomment-3662919194.Please provide your
config.tomlfile contents (with any personal details redacted).Oh, you are not using Azure endpoints as implied in your initial bug report. You're using the default OpenAI endpoints.
You said that you "set the environment variables". Which environment variables did you set?
Based on the symptoms you're seeing, this is likely a litellm proxy issue. Are you sure you're using the latest version of litellm? Does this work if you don't go through the litellm proxy?
OPENAI_API_KEYandOPENAI_BASE_URLThanks for your prompt replies, if I see anymore of the same errors I'll report back.
If it's working when you connect directly to Azure, then this is a litellm issue. You should report the problem to its maintainers.