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 503ServiceUnavailable response. Displaying the following common response prevents the production environment from leaking error message information:
Temporarily 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.
Important
Normally, you cannot change the preceding message. However, if you use a WAF, you can replace the message with other content. For more information, refer to the documentation for the specific WAF. For example, Cloudflare Error Pages.
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:
Transitory resource limits such as insufficient CPU or DB resources, which occur due to high traffic, application complexity, or both. This high traffic can be expected or caused by unusual robot crawls or DDoS attacks.
Code changes, data changes, or bugs that trigger PHP exceptions or errors.
To resolve this, do one or more of the following:
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 503ServiceUnavailable response. Displaying the following common response prevents the production environment from leaking error message information:
Temporarily 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.
Important
Normally, you cannot change the preceding message. However, if you use a WAF, you can replace the message with other content. For more information, refer to the documentation for the specific WAF. For example, Cloudflare Error Pages.
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:
Transitory resource limits such as insufficient CPU or DB resources, which occur due to high traffic, application complexity, or both. This high traffic can be expected or caused by unusual robot crawls or DDoS attacks.
Code changes, data changes, or bugs that trigger PHP exceptions or errors.
To resolve this, do one or more of the following:
Roll back changes to a site by restoring older configuration, code, or a database backup.
Cloud Platform