You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Agent Canvas with a Cloud backend on Windows, requests can fail with a LiteLLM internal server error that wraps an HTML downtime page from down.app.all-hands.dev.
This suggests the request path is sometimes receiving an HTML "Service Temporarily Unavailable" page instead of the expected API/LLM response.
Steps to Reproduce
Run Agent Canvas on a Windows machine.
Connect/use the Cloud backend.
Send a prompt that triggers an LLM request.
Observe that the request can fail with a litellm.InternalServerError / Litellm_proxyException containing HTML from down.app.all-hands.dev.
Actual Behavior
Instead of a normal model response or a cleaner backend error, the conversation fails with a LiteLLM internal server error whose payload includes a full HTML downtime page (Service Temporarily Unavailable).
Expected Behavior
Cloud-backed requests should not surface a raw HTML downtime page inside the LiteLLM exception.
If the upstream service is unavailable, Agent Canvas should show a clearer cloud-backend outage/error state.
If this is Windows-specific, that platform-specific trigger should be identified and fixed.
Reported specifically when using the Agent Canvas Cloud backend on Windows.
I searched for existing issues using terms including litellm, Litellm_proxyException, down.app.all-hands.dev, cloud backend, InternalServerError, and windows, but did not find an existing issue matching this exact failure mode.
Operating System
Windows
Installation Method
Other: Agent Canvas using a Cloud backend
Agent Canvas Version
Unknown / not provided
Bug Description
When using Agent Canvas with a Cloud backend on Windows, requests can fail with a LiteLLM internal server error that wraps an HTML downtime page from
down.app.all-hands.dev.The reported error begins like this:
This suggests the request path is sometimes receiving an HTML "Service Temporarily Unavailable" page instead of the expected API/LLM response.
Steps to Reproduce
litellm.InternalServerError/Litellm_proxyExceptioncontaining HTML fromdown.app.all-hands.dev.Actual Behavior
Instead of a normal model response or a cleaner backend error, the conversation fails with a LiteLLM internal server error whose payload includes a full HTML downtime page (
Service Temporarily Unavailable).Expected Behavior
Relevant Logs
Additional Context
litellm,Litellm_proxyException,down.app.all-hands.dev,cloud backend,InternalServerError, andwindows, but did not find an existing issue matching this exact failure mode.This issue was created by an AI agent (OpenHands) on behalf of the user.