DALL-E 3 Image Generation on Azure OpenAI still not using PROXY

[alfo-dev]

What happened?

#8712 has not fully fixed that image generation is not using the PROXY env variable.

When DALL-E 3 via Azure OpenAI is used, the traffic is not routed via the proxy

Version Information

0.8.0-r2

Steps to Reproduce

1.) Define variables PROXY, DALLE3_API_KEY, DALLE3_BASEURL, DALLE3_AZURE_API_VERSION in .env
2.) use DALL-E plugin in agent
3.) image creation forces timeout - network logs show that traffic ist not routed via proxy

What browsers are you seeing the problem on?

No response

Relevant log output

.env
PROXY=http://proxy:8080
DALLE3_API_KEY=myKey
DALLE3_BASEURL=https://myAzureURL/openai/deployments/dall-e-3/
DALLE3_AZURE_API_VERSION=2024-02-01

Screenshots

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

I've reviewed the code, and the PROXY env. variable is in fact being used. Please make sure to update as recommended to ensure the latest codebase is used.

Updating Instructions (docker):
https://www.librechat.ai/docs/local/docker#update-librechat

1. The proxy variable is detected and configured:

2. Downstream code uses proxy agent:

3. Text proxy server logs request upon API request:

[2025-08-13T14:28:39.254Z] CONNECT api.openai.com:443 -> HTTPS Tunnel Request
Headers: {
  "host": "api.openai.com",
  "connection": "close",
  "proxy-authorization": "Basic dXNlcjpwYXNz"
}
Remote Address: ::ffff:127.0.0.1
Connection ID: 25
Event: connect-start
================================================================================

[2025-08-13T14:28:39.282Z] CONNECT api.openai.com:443 -> HTTPS Tunnel Established
Headers: {}
Remote Address: ::ffff:127.0.0.1
Connection ID: 25
Event: connect-established
================================================================================

[2025-08-13T14:28:39.292Z] Connection 25 - Client -> Server: 387 bytes
[2025-08-13T14:28:39.304Z] Connection 25 - Server -> Client: 1420 bytes
[2025-08-13T14:28:39.305Z] Connection 25 - Server -> Client: 1430 bytes
[2025-08-13T14:28:39.310Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.311Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.311Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.312Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.313Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.314Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.315Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.315Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.316Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.317Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.318Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.319Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.320Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.321Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.322Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.322Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.323Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.324Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.325Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.326Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.327Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.328Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.328Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.329Z] Connection 25 - Client -> Server: 65536 bytes
[2025-08-13T14:28:39.329Z] Connection 25 - Client -> Server: 3717 bytes
[2025-08-13T14:28:42.758Z] Connection 25 - Server -> Client: 1666 bytes
[2025-08-13T14:28:42.767Z] Connection 25 - Server -> Client: 389 bytes
[2025-08-13T14:28:42.799Z] Connection 25 - Server -> Client: 687 bytes
[2025-08-13T14:28:42.857Z] Connection 25 - Server -> Client: 687 bytes
[2025-08-13T14:28:42.882Z] Connection 25 - Server -> Client: 687 bytes
[2025-08-13T14:28:42.911Z] Connection 25 - Server -> Client: 687 bytes
[2025-08-13T14:28:42.946Z] Connection 25 - Server -> Client: 687 bytes
[2025-08-13T14:28:42.982Z] Connection 25 - Server -> Client: 687 bytes
[2025-08-13T14:28:43.074Z] Connection 25 - Server -> Client: 687 bytes
[2025-08-13T14:28:43.160Z] Connection 25 - Server -> Client: 687 bytes
[2025-08-13T14:28:43.278Z] Connection 25 - Server -> Client: 687 bytes
[2025-08-13T14:28:43.296Z] Connection 25 - Server -> Client: 671 bytes
[2025-08-13T14:28:43.305Z] Connection 25 - Server -> Client: 548 bytes
[2025-08-13T14:28:43.311Z] Connection 25 - Server -> Client: 55 bytes

Note about 1.5 MB is transmitted from request, which is roughly the DALL-E generation size.

4. image is generated:

[alfo-dev]

After some more testing, the situation seems to be as follows:

• env. vars PROXY + DALLE_API_KEY -> proxied (OpenAI Config)
• env. vars PROXY + DALLE3_API_KEY + DALLE3_AZURE_API_VERSION ->not proxied (Azure OpenAI config)
• env. vars PROXY + DALLE_API_KEY + DALLE3_API_KEY + DALLE3_AZURE_API_VERSION -> partly proxied

@danny-avila : Can you confirm this behavior or do you also have a proxied connection when using DALL-E 3 via Azure OpenAI?

[alfo-dev]

@danny-avila : Thank you for the fast fix regarding the proxy bypass for Azure Mistral OCR! I can confirm that it works in my environment.

However, in the same environment the DALL-E plugin on Azure OpenAI still produces almost the same proxy-related error as Azure Mistral OCR. I can also reproduce it with DALL-E on OpenAI (clarification to my statement above).

Steps to reproduce:
1.) Set up proxy, set PROXY env variable and isolate LibreChat from internet access (e.g. internal Docker network)
2.) Configure Dall-E plugin (DALLE3_API_KEY, DALLE3_BASEURL, DALLE3_AZURE_API_VERSION) and generate image
3.) Image generation fails (error in DALL-E result)
4.) Allow internet access for LibreChat backend (proxy is still set)
5.) Image generation with DALLE-E is successful, network logs show proxy bypass to dalleprodsec.blob.core.windows.net

Error in DALL-E result:
Error processing tool: request to https://dalleprodsec.blob.core.windows.net/private/images/guid/generated_00.png?URL_parameters failed, reason: getaddrinfo EAI_AGAIN dalleprodsec.blob.core.windows.net