AWS ALB 463 X-Forwarded-For header has too many IP addresses
The ALB received a request whose X-Forwarded-For header lists more than 30 IP addresses.
ALB 463 X-Forwarded-For463 The load balancer received an X-Forwarded-For request header with more than 30 IP addresses Meaning
Each proxy appends an IP; a chain of more than 30 is rejected. Reduce proxy hops, strip or reset X-Forwarded-For at the edge, and look for forwarding loops.
Common causes
- Too many proxy hops
- Forwarding loop between proxies
- Client sending forged long XFF
- CDN chained to CDN
- Header never reset at the edge
⚡ Quick fix
- Remove unnecessary proxy hops
- Reset XFF at the first trusted proxy
- Find and fix a request loop
Detailed fix by platform
cURL
curl -sI -H "X-Forwarded-For: 1.1.1.1, 2.2.2.2" https://alb.example.com/
How to diagnose
- XFF entries — More than 30?
- Hops — Needed?
- Loop — Present?
🔧 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