HTTP Status Code used in case of error on Fasterize

TABLE OF CONTENTS

• Presentation
  • Error information to provide to your hosting provider
• Error 500: internal server error
• Error 502 bad gateway or 504 gateway timeout
  • 502/504 from your origin web server
  • 502/504 from our CDN layer
• Error 503: service temporarily unavailable
• Erreur 542: Connection to the origin web server failed
• Error 544: Timeout response from the origin server
• Error 521: configuration not found
• Error 524: redirection loop detected
• Error 53x, 59x: Internal Fasterize Error

Presentation

To troubleshoot most 5xx errors, you must first contact your hosting provider or site administrator to troubleshoot and collect data.

Error information to provide to your hosting provider

1. Code and specific 5xx error message
2. The time (with the time zone) at which error 5xx occurred.
3. The URL that generated the HTTP 5xx error (for example: https://www.example.com/images/icons/image1.png)
4. The IP address of the browser

Error 500: internal server error

A 500 error indicates a problem with your origin web server. For instance, Error establishing database connection is a current HTTP 500 error message generated by your origin web server.

In this case, Fasterize was able to connect to the origin server but received a 500 error in return. The X-Fstrz HTTP response header added by Fasterize has the value 'stc, Z, p'.

Note: To simplify troubleshooting, Fasterize does not use error code 500 internally.

Resolution: 

Provide detailed information to your hosting provider to help you resolve the problem. This is usually an application error.

Error 502 bad gateway or 504 gateway timeout

An HTTP 502 or 504 error can occur in one of two ways:

• when the error is issued by your origin web server
• when our CDN is unable to establish contact with the optimization engine
  
  

502/504 from your origin web server

In this case, Fasterize was able to establish the connection to the origin server, but the origin returned a response with error code 502 or 504.

The returned page then does not mention either Fasterize or CDN (e.g. Cloudfront). As for error 500, the HTTP response header X-Fstrz added by Fasterize then takes the value 'stc, Z, p'.

Resolution

Contact your hosting provider to find the cause of these problems on your origin web server:

• Verify that the origin server responds to requests for the host name and domain in the URL of the user that generated error 502 or 504.
• Check for excessive server loads, crashes, or network failures.
• Identify applications or services that have expired or have been blocked.
  
  

502/504 from our CDN layer

A 502 or 504 error from our CDN layer usually looks like this:

In this case, our CDN (Cloudfront in that specific case) failed to connect to our optimization engine. Please visit https://status.fasterize.com to check the status of the service.

Resolution

To speed up the processing of your request, please provide this information to Fasterize support:

1. the time (with the time zone) when the problem occurred
2. the URL that generated the HTTP 502 or 504 response (for example: https://www.example.com/images/icons/image1.png
3. the Request ID number given on the error page
4. the IP address of the browser

Error 503: service temporarily unavailable

The HTTP 503 error occurs when your original web server is overloaded. The error message can indicate two possible causes.

This status code is never issued by Fasterize. As with error 500, the X-Fstrz HTTP response header added by Fasterize is set to 'stc, Z, p'.

Resolution

Contact your hosting provider to check if they are limiting the throughput of requests to your origin web server or if your origin has been switched to maintenance.

Erreur 542: Connection to the origin web server failed

A 542 error is generated by Fasterize when Fasterize fails to access the origin web servers. There are several possible reasons for this:

• the origin server specified in the configuration is no longer correct
• the origin server is down / unreachable
• the origin server blocks Fasterize connections (TCP connection in error, WAF, anti-DDOS, etc ...)
• the TLS certificate of the origin server is incorrect and Fasterize is configured to check its validity
• TLS negotiation failed (the list of supported TLS standards and ciphers is not compatible)
• the DNS resolution of the origin fails

Resolution

Contact your site administrator or your hosting provider to eliminate these common causes:

• check the responsiveness of your origin web server
• check the logs of the origin web server to identify crashes or application failures of the web server
• check that Fasterize IP addresses are not blocked or rate-limited
• check the origin entered in the configuration
• whitelist all Fasterize IP ranges in the firewall in front of your origin web server or any other security software

Error 544: Timeout response from the origin server

A 544 error is generated by Fasterize if it fails to connect to the origin server within 20 seconds or when Fasterize connected to the origin web server, but the origin server did not provide an HTTP response within 175 seconds.

Resolution

Contact your hosting provider to exclude the following common causes on your origin web server:

• a long process is running on the origin web server (catalog export, data aggregation, etc.).
• overloaded origin web server

Note: Recording the response time of requests on your origin web server helps identify the reason for slow resources. Contact your hosting provider or site administrator to help you set up logging formats, or look for associated logging documentation corresponding to your web server brand, such as Apache or Nginx.

If you regularly run HTTP requests that end with a 544 error code before they are completed (such as large data exports), move these processes behind a subdomain that is not proxyfied by Fasterize or call the origin web server directly.

Error 521: configuration not found

The Fasterize platform did not find a configuration that matches the domain name of the website.

Resolution

Contact Fasterize support

To speed up the processing of your request, please provide this information to Fasterize support:

1. the time (including the time zone) at which the problem occurred
2. the URL that generated the HTTP 521 response (for example: https://www.example.com/images/icons/image1.png)
3. the HTTP header X-unique-id
4. the IP address of the browser

Error 524: redirection loop detected

The configuration that matches the domain name is incorrect. The configuration origin points to Fasterize instead of the origin server.

Resolution

Contact Fasterize support

To speed up the processing of your request, please provide this information to Fasterize support:

1. the time (including the time zone) at which the problem occurred
2. the URL that generated the HTTP 524 response (for example: https://www.example.com/images/icons/image1.png)
3. the HTTP header X-unique-id
4. the IP address of the browser

Error 53x, 59x: Internal Fasterize Error

An internal Fasterize platform error has occurred.

Résolution :

Check https://status.fasterize.com to see if an incident has been reported.

If not, contact Fasterize support.

To speed up the processing of your request, please provide this information to Fasterize support:

1. the time (including the time zone) at which the problem occurred
2. the URL that generated the HTTP 53x or 59x response (for example: https://www.example.com/images/icons/image1.png)
3. the HTTP header X-unique-id
4. the IP address of the browser