Common Errors
This document provides a detailed list of all possible error codes that the Image API may return, along with their associated reasons and troubleshooting tips.
Image API Error Codes
| Code | Name | Description |
|---|---|---|
| 400 | Bad Request | This error occurs when the request is invalid. Possible causes include: - Malformed original image. - Incorrect URL parameters. - The image backend is returning a 400 response.- Issues with the imageParamValidations configuration. |
| 401 | Unauthorized | The request is blocked due to insufficient permissions or misconfiguration. Common causes include: - Using origin= with allowDynamicOrigin disabled.- Misconfigured allowOriginalImageRequest. - Restrictions in hostsAllowed or bucketsAllowed. - Invalid imageParamsAllowed. Alternatively, the image backend may also return a 401 response. |
| 403 | Forbidden | Indicates a permission issue. Potential causes include: - The image backend is returning a 403 response.- Insufficient permissions to access the image via Imagizer. If the error occurs during uploads, review the upload configuration. |
| 404 | Not Found | The requested image is missing from the backend, or the backend configuration is incorrect. |
| 499 | Client Closed Request | The client closed the connection before the request was completed. To resolve this issue, consider increasing client timeouts or reducing the size of the source image to lower processing time. |
| 500 | Internal Server Error | Indicates an unexpected issue with the Imagizer server or the image backend. Check logs for further details and contact Nventify support if needed. |
| 502 | Bad Gateway | Similar to a 500 error, this indicates an unexpected error with Imagizer or the image backend. |
| 503 | Service Unavailable | Occurs when Imagizer cannot process the request due to high load or insufficient memory. The error may also originate from the image backend. |
| 504 | Gateway Timeout | The image fetch and processing exceeded the time allowed by the backendTimeout configuration. This error may also originate from the image backend. |