GOAWAY HTTP Origin: Network OSI layer 7 · Application Last updated 18 Nov 2026

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.

Exact message you may see GOAWAY receivedHTTP/2 GOAWAY framehttp2: server sent GOAWAY and closed the connectionhttp2: Transport received GOAWAY
Seen on: HTTP Go Node.js

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

  1. Retry the request on a new connection
  2. Raise http2_max_requests / keepalive limits
  3. Read the GOAWAY error code and last stream ID in the logs

Detailed fix by platform

cURL

  1. curl -v --http2 https://example.com/ 2>&1 | grep -iE "goaway|stream|connection"

How to diagnose

  1. Error code — NO_ERROR or other?
  2. Server — Restarting?
  3. 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:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

100 — HTTP 100 Continue (HTTP)100103 — HTTP 103 Early Hints (HTTP)103505 — HTTP 505 HTTP Version Not Supported (HTTP)505ALPN — tlsv1 alert no application protocol — ALPN negotiation failed (h2/http/1.1) (SSL / TLS)ALPNAlt-Svc / QUIC — HTTP/3 (QUIC) not used or failing — Alt-Svc fallback to HTTP/2 (HTTP)Alt-Svc / QUICENHANCE_YOUR_CALM — HTTP/2 ENHANCE_YOUR_CALM (too many streams / rapid reset) (HTTP)ENHANCE_YOUR_CALMERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY — Chrome: ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY — HTTP/2 requires a modern TLS cipher (SSL / TLS)ERR_HTTP2_INADEQUATE_…ERR_HTTP2_PROTOCOL_ERROR — Chrome: This page isn’t working — example.com is unable to handle this request. ERR_HTTP2_PROTOCOL_ERROR (Browser)ERR_HTTP2_PROTOCOL_ER…GOAWAY

Explore the map of this error Full error map →

🧠 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.