Nginx 444 No Response

Plain-English meaning

Nginx intentionally closes connection without an HTTP response body.

Why it happens

Used to drop unwanted traffic, but can also block legitimate traffic when misconfigured.

Common causes

  • Server block returns 444 for unknown hosts
  • WAF-style deny rule over-matches
  • Host/SNI mismatch routes to deny block
  • Location rule catches valid application paths

What to check first

Search configs for return 444 directives and confirm Host/SNI values for affected requests.

How to fix it

Narrow blocking rules, add explicit allow rules for valid hosts, and isolate security drop logic from app routes.

Example signal

server { if ($host !~* ^api\.example\.com$) { return 444; } }

Related links

404 · 429 · 500 · 502 · 503 · 504 · Cloudflare 522 · Nginx 499 · ERR_CONNECTION_REFUSED

Client errors hub · Server errors hub · Comparison pages · Homepage