If you receive an error code for an image request, you can find the meaning and possible causes below.
List of errors
400 Bad Request
- The image is requested from a Web Proxy Source, and the URL that is proxied is not an absolute URL or has an invalid hostname.
- The image is requested from a Source with the Secure URL option turned on, but the
ssignature is either missing or invalid.
- The origin is configured to know the presence of the object, but the object is missing.
- Any permissions that the Source needs to access images from the origin are incorrect.
404 Not Found
- The image cannot be accessed from the origin. Please check that:
- The file path to the image is correct in your imgix source settings
- If you are using an S3 source, check that the the S3 Access Key and Access Key ID credentials entered in imgix are valid, and that IAM user has sufficient permissions to access the object
- The image can be accessed by imgix and is not being blacklisted
- The HTTPS certificates on the origin are valid and working
- The image is requested from a non-existent Source, or a Source that is not deployed or that is disabled.
- Check to see that the Source is actually deployed
- Check for a typo.
412 Precondition Failed
- A parameter in the query string contains an invalid value, e.g.
413 Request Entity Too Large
- The requested image is too large. Our current input limit is 500MB.
414 URI Too Long
- The image path is too long. Our current limit is 3072 characters (3KB).
- The requested image has failed internal verification. This is usually caused by a corrupt image.
- For PNGs, you can try checking the image with pngcheck.
500 Internal Server Error
- An error occurred while processing the image.
- Origin SSL issues, such as certificate and handshake errors
502 Bad Gateway
- Bad redirect
- There is a chain of redirects, with more hops than we support.
- The origin request redirects to the root of a webserver, with no URI.
503 Service Unavailable
- Temporary unavailability due to processing requirements, i.e. a requested GIF is too large.
- A timeout occurred while attempting to connect to the origin.
- RFC violations, such as invalid characters in HTTP header response or possibly due to bot detection on the origin provider.
- The DNS entry for the origin could not be resolved.
504 Gateway Timeout
- A timeout occurred while attempting to fetch the object from the origin
508 Loop Detected
- The request from the origin redirects to itself.
Other Status Codes
- The origin returned an unusual status code and we passed it through.