421 Misdirected Request
4xx client error
The connection is reused but the domain in the request does not match the certificate or virtual host it was opened for, so another connection is needed.
Common causes
- An HTTP/2 connection coalesces hosts with no matching certificate SAN.
- A client sends a Host the current TLS session does not cover.
- A reverse proxy routes a coalesced request to the wrong virtual host.
How to fix it
- Ensure the certificate covers every hostname served on a coalesced connection.
- Configure per-host connection pools or disable coalescing.
- Return Alt-Svc or Connection-Close hints so the client reconnects.
What it means for redirects and SEO
Connection reuse mismatches mostly hit HTTP/2 and logged-out bots. The URL is normally fine once a fresh connection is made. Check certificate SAN coverage for every hostname served.