AWS ALB 460 Client Closed Connection
The client closed the connection before the Application Load Balancer sent its response.
ALB 460 client closed connection460 Client closed the connection with the load balancer before the idle timeout period elapsed Meaning
ALB returns 460 when the client disconnects, often because its timeout is shorter than the idle timeout or the backend is slow. Increase the client timeout, speed up the backend, or raise the ALB idle timeout (default 60 s).
Common causes
- Client timeout shorter than ALB idle timeout
- Slow backend response
- Mobile client dropping connections
- User closed the page
- Long request without keepalive
⚡ Quick fix
- Raise the client timeout above the ALB idle timeout
- Speed up the slow endpoint
- Check
HTTPCode_ELB_4XX_Countand access logs
Detailed fix by platform
AWS CLI
aws elbv2 modify-load-balancer-attributes --load-balancer-arn ARN --attributes Key=idle_timeout.timeout_seconds,Value=120
How to diagnose
- Client timeout — Shorter?
- Backend latency — High?
- ALB idle timeout — Default 60 s?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in HTTP
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026