Fastly Serves Wrong Content or Denies Requests From Origin (Override Host)

How to fix it

Try these in order — the most common fix is first.

1. 1. Override the host per origin

   Copy steps
   1. Clone the service to edit and click Origins
   2. Open the three dots next to the host, click Edit host
   3. Enter the hostname your origin expects in Override host
   4. Click Update and activate on Production
   Did this fix it? Yes No

2. 2. Global override (single origin only)

   Copy steps
   1. Settings, then Override hosts, switch Override host on
   2. Enter the Override host header value and save, then activate
   3. Per-origin overrides take precedence over the global one
   Did this fix it? Yes No

Symptoms

Origin such as S3 or Google Cloud Storage denies requests or returns the wrong site only when going through Fastly.

Why it happens

• The Host header sent to the origin differs from the one the origin expects
• Several domains on one service share one origin
• A global override host conflicts with multiple origins, forced TLS/HSTS or shielding

This guide also covers

• fastly override host
• fastly s3 access denied
• fastly origin wrong host header

Other Fastly errors

• Fastly Error: Unknown Domain
• Fastly 503 Backend Read Error / Connection Timeout
• Fastly Purge Not Working (Old Content Still Served)
• Fastly TLS Certificate Stuck Pending or Not Provisioning
• Fastly Origin TLS Errors: Hostname Mismatch, Unable to Verify Certificate
• Fastly Not Caching: Always X-Cache MISS
• How to Cancel Fastly Account