HTTP/2 GOAWAY received (connection closed by server)
The server sent an HTTP/2 GOAWAY frame, telling the client to stop opening new streams on this connection.
GOAWAY receivedHTTP/2 GOAWAY framehttp2: server sent GOAWAY and closed the connectionhttp2: Transport received GOAWAY Meaning
Servers send GOAWAY on graceful shutdown, after too many requests on one connection (http2_max_requests), on protocol errors, or when a proxy recycles connections. Clients should open a new connection and retry idempotent requests; a flood of GOAWAYs points to restarts or a limit that is too low.
Common causes
- Server or proxy restarting or reloading
- Max requests per connection reached
- Protocol error (ENHANCE_YOUR_CALM, PROTOCOL_ERROR)
- Idle timeout on the load balancer
- Client library not retrying
⚡ Quick fix
- Retry the request on a new connection
- Raise
http2_max_requests/ keepalive limits - Read the GOAWAY error code and last stream ID in the logs
Detailed fix by platform
cURL
curl -v --http2 https://example.com/ 2>&1 | grep -iE "goaway|stream|connection"
How to diagnose
- Error code — NO_ERROR or other?
- Server — Restarting?
- Client — Retries?
🔧 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