If you’ve detected, or been notified that requests to your site are resulting in an error you can utilize the Traffic Analytics dashboard when investigating.
Note: Always adjust the Dashboard Date – Time range depending on the timeframe you are investigating. By default the dashboard will always show the "last 1 hour".
From the Analytics Dashboard:
1. Locate the Response Codes category filter
2. Filter the 500 errors by clicking on 5xx:
You should now see all 5xx errors that were generated.
Common 5xx Server Errors
Below is a list of 5xx errors that you can see within the Yottaa portal. These errors are response codes generated by Yottaa and will display a Yottaa error page.
500 Internal Server Error:
Catch all error that reports unexpected conditions that prevented the request to be fulfilled.
503 Service Unavailable (Application Timeout):
Occurs when the server is unable to handle the current request. This can be due to scheduled maintenance or temporary overload.
504 Gateway Time-out:
Yottaa server was unable to receive a timely response from origin. This results in a network timeout.
Below is a list of other common 5xx errors that you may encounter. It is important to note that these errors will not generate a Yottaa error page, and will be handled client side, or logged via origin logs.
501 Not Implemented:
Occurs when the server does not recognize the request, or is unable to fulfill the request.
502 Bad Gateway:
The server is acting as a gateway or proxy, and received an invalid response from the inbound server while attempting to fulfill a request.
508 Loop Detected:
The server detected an infinite loop while processing the request
3. Use the graph to identify 5xx occurrences:
When did this occur?
Is this still an active concern?
4. Identify the impact of these response codes:
Who is affected?
Is it isolated?
5. Identify the URLs that are requested that result in the error:
What is affected?
What is calling the affected URL?
6. Identify the source of the error using the “Served From” Category filter:
Where is the response code served?
Note: Match up, or filter, by either Yottaa or the origin to get a view of what content is responded with an error from each environment.
7. Diagnosing these types of issues may take a collaborative effort involving Yottaa support. However investigating logs on the origin server may give the best results of what response is sent to Yottaa during the time of incident.