Cloud Platform
HTTP 5xx status codes on Cloud Platform
If your server experiences slow queries, use the provided documentation to identify and resolve these issues. Tools and guides are available to help parse slow query logs and understand how to improve query performance. To request help for severely-impacted production sites, create a Support ticket with critical urgency for immediate assistance or to terminate problematic queries on your behalf.
Cloud Platform replaces all HTTP 500, 501, 502, 503 and 504 status code responses served to visitors of your production environments with a generic 503 Service Unavailable response. Displaying the following common response prevents the production environment from leaking error message information:
Cloud PlatformTemporarily Unavailable
The website that you're trying to reach is having technical difficulties
and is currently unavailable. We are aware of the issue and are working
hard to fix it. Thank you for your patience.To assist with troubleshooting during development, non-production environments pass all HTTP 5xx status codes through the load balancers back to the requesting client without any replacement. You can review these error messages in your log files, which you can access using the following methods:
For production environments, use logs and log streaming to determine the root cause. Access logs display the real HTTP status code at the back end. To find corresponding logs from other sources, such as PHP errors and Drupal Watchdog, use the X-Request-Id value, which matches all logged items for the same request.
Common causes of Temporarily Unavailable pages on production environments include but are not limited to:
To resolve this, do one or more of the following:
To assist with troubleshooting during development, non-production environments pass all HTTP 5xx status codes through the load balancers back to the requesting client without any replacement. You can review these error messages in your log files, which you can access using the following methods:
For production environments, use logs and log streaming to determine the root cause. Access logs display the real HTTP status code at the back end. To find corresponding logs from other sources, such as PHP errors and Drupal Watchdog, use the X-Request-Id value, which matches all logged items for the same request.
Common causes of Temporarily Unavailable pages on production environments include but are not limited to:
To resolve this, do one or more of the following:
To learn more about how your infrastructure allocates resources, visit Tuning your infrastructure configuration.
To learn more about how your infrastructure allocates resources, visit Tuning your infrastructure configuration.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.