Bundled MySQL never passes its health check, so WordPress is not started
Error recorded 1 times in PanelAlpha Engine deploys on Docker Compose. The deploy log below is the recorded failure output.
TypeErrorAn error that occurred in the deployed application. It is not necessarily a PanelAlpha Engine error, but we keep working on improvements so you run into fewer of them.
Seen1 times
WhereDocker Compose
StatusIn AnalysisOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The WordPress stack's MySQL service started, but its health check, a login as the wordpress user over TCP, kept failing until Docker marked the service unhealthy. The application waits for a healthy database, so it was never started. MySQL's own output shows only a normal startup, so the report does not say why the login failed.
What the log looks like
Deploy log
Failed to start app: The service project-db-1 did not start (unhealthy), so the application was not started either. It printed: 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended. 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed. 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel. 0 [Warning] [MY-011810] [Server] Insecure config… The full output is in the deploy log.