HTTP 5xx status codes on Cloud Platform

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.

HTTP 5xx status codes on Cloud Platform

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.

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:

• Downloading active log files
• Downloading historical logs
• Streaming log entries in real time
• Log forwarding in Cloud Platform

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.
• Adjust PHP memory limits.
• Block traffic through a Web
  Application
  Firewall (WAF) with or other methods.

To learn more about how your infrastructure allocates resources, visit Tuning your infrastructure configuration.

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:

• Downloading active log files
• Downloading historical logs
• Streaming log entries in real time
• Log forwarding in Cloud Platform

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.
• Adjust PHP memory limits.
• Block traffic through a Web
  Application
  Firewall (WAF) with or other methods.

To learn more about how your infrastructure allocates resources, visit Tuning your infrastructure configuration.