WordPress on App Service deployments are failing in West US 2 following event GHRP-84G

John Joyner 66 Reputation points
2026-05-30T03:37:28.48+00:00

Attempting to deploy a fresh default WordPress on App Service deployment (to Premium tier, all new resources) in West US fails at the step deploying Azure Database for MySQL flexible server with error "An unexpected error occured while processing the request. Tracking ID: '32afd1de-f8ea-40e2-89c6-0b88d42ad7d8' (Code: InternalServerError)." Have reproduced this several times.

Probably for the same reason, my WordPress on App Service web site has been unavailable since Tue 9/23/2025 11:30 PM CDT perhaps at the onset of the issues covered in the Multi Service degradation event in West US 2: https://app.azure.com/h/GHRP-84G/07339d. When attempting to start site, swap site, or restore site, the site never completes the start, and a review of the platform log stream shows this error: "ContainerTimeout" starting WordPress on App Service in West US 2 following Multi Service degradation.

PSSticket

Azure Database for MySQL
Answer accepted by question author
John Joyner 80 Reputation points MVP
2026-06-01T02:39:46.96+00:00

I can report after resolution of the service issue, and a cold start of the MySQL and WebApp services, my site is up. Thank you

Was this answer helpful?

1 person found this answer helpful.
0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-05-30T03:37:49.05+00:00

    The behavior matches a regional platform issue rather than a problem with the WordPress template itself.

    For the failed new deployments:

    • The WordPress on App Service template provisions Azure Database for MySQL flexible server as a managed component of the architecture.
    • An InternalServerError at the MySQL flexible server step in a single region, with a tracking ID and no validation errors, indicates a backend service problem in that region.
    • Because the template depends on successful creation of Azure Database for MySQL, the overall deployment fails when the database resource cannot be provisioned.

    For the existing WordPress site stuck with ContainerTimeout:

    • WordPress on App Service uses a containerized runtime; the app must successfully connect to Azure Database for MySQL during startup.
    • If the underlying MySQL flexible server is unavailable or degraded in the region, the container can fail to complete initialization, leading to ContainerTimeout (Container did not start within expected time limit of 1800s) and repeated warm‑up failures.

    Recommended actions based on the documented architecture and troubleshooting guidance:

    1. Validate that the issue is regional
      • Attempt a fresh “WordPress on App Service” deployment in a different region (for example, a nearby region that is not part of the incident) using the same template and Premium tier.
      • If the deployment succeeds in the alternate region, this confirms the failure is specific to West US 2 platform services (particularly Azure Database for MySQL flexible server) rather than the template or configuration.
    2. Use the architecture pattern to plan a temporary workaround
      • The reference architecture for WordPress on App Service is region‑agnostic: App Service hosts WordPress, and Azure Database for MySQL flexible server stores WordPress data.
      • As a mitigation while West US 2 is impacted, consider:
        • Deploying a new WordPress on App Service instance in a healthy region using the same template.
        • Restoring WordPress data into a new Azure Database for MySQL flexible server in that region (for example, from backups or exports), then pointing the WordPress instance to that database.
    3. Focus troubleshooting on the database layer
      • Because the error is raised at the MySQL flexible server step, and the running site’s container cannot complete startup, troubleshooting should concentrate on Azure Database for MySQL availability in West US 2 rather than on PHP/WordPress code.
      • For existing WordPress apps that show “Error establishing a database connection,” enable WordPress error logs and inspect for connection‑limit or connectivity errors as described in the open‑source troubleshooting guidance. This helps confirm that the app is blocked on database connectivity, not on application logic.
    4. After the regional incident is resolved
      • Retry the WordPress on App Service deployment in West US 2 once the multi‑service degradation event is closed.
      • For the existing site, attempt a normal restart once Azure Database for MySQL in West US 2 is healthy; the container should then pass warm‑up without ContainerTimeout.
      • If the site is no longer needed or has been fully moved to another region, delete the associated resource group to clean up App Service, Azure Database for MySQL, and related resources.

    These steps align with the documented WordPress on App Service architecture, which relies on Azure Database for MySQL flexible server and other managed services that can be redeployed to alternate regions when a specific region experiences platform issues.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.