[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"problem-detail-error-bundled-mysql-never-passes-its-health-check-so":3},{"stack":4,"error":5,"seoName":6,"seoStack":7,"seo":8,"breadcrumb":10,"titlePrefix":17,"titleAccent":6,"lead":18,"facts":21,"why":36,"log":46,"fix":55,"engine":59,"related":66,"pitch":69},"compose","bundled-mysql-never-passes-its-health-check-so","Bundled MySQL never passes its health check, so WordPress is not started","Docker Compose",{"description":9},"Learn what causes Bundled MySQL never passes its health check, so WordPress is not started, how PanelAlpha Engine responds to it during deployment.",[11,14,16],{"label":12,"href":13},"App Installations","\u002Fapps",{"label":7,"href":15},"\u002Fapps\u002Fstacks\u002Fcompose",{"label":6},"",[19],{"text":20},"Error recorded 1 times in PanelAlpha Engine deploys on Docker Compose. The deploy log below is the recorded failure output.",[22,27,30,32],{"label":23,"value":24,"tone":25,"tooltip":26},"Type","Error","err","An 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.",{"label":28,"value":29},"Seen","1 times",{"label":31,"value":7},"Where",{"label":33,"value":34,"tooltip":35},"Status","In Analysis","Our team will look into this soon, verify the cause and try to fix it in an upcoming release.",{"heading":37,"body":38},"Why it happens",[39,41,44],{"text":40},"The WordPress stack's MySQL service started, but its health check, a login as the ",{"text":42,"code":43},"wordpress",true,{"text":45}," 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.",{"heading":47,"block":48},"What the log looks like",{"header":49,"lines":50},"Deploy log",[51],{"segments":52},[53],{"text":54},"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.",{"heading":17,"steps":56,"block":57},[],{"header":17,"lines":58},[],{"heading":60,"body":61,"block":64},"How PanelAlpha Engine solves it",[62],{"text":63},"Not reproduced on current develop, on a host with ample memory or with the account capped at 1 GB: a fresh deploy of github.com\u002FWordPress\u002FWordPress initialises MySQL in about 10 s and becomes healthy (0.5 CPU cap on the db service). The identical failure text is reproduced when the database volume holds a different password than ~\u002F.panelalpha\u002Fwordpress\u002Fdb.env: the probe then answers ERROR 1045 Access denied, and MySQL's output is exactly the startup lines in this report. Credentials are written once and kept on 2.1.0+, so the mismatch needs the volume and the stored file to diverge (an earlier database in the same project, or the stored file removed). The engine now quotes the failing health probe in the failure (\"Its health check said: ...\"), so the next occurrence names the cause; change in engine MR 555.",{"header":17,"lines":65},[],{"heading":67,"items":68},"Apps affected",[],{"heading":70,"body":71,"footNote":72,"docsLabel":73,"docsHref":74},"Try PanelAlpha Engine yourself.","The easiest way to turn your server into a safe, controlled environment for your AI agent. Deploy, manage and maintain any project from Claude Code, Cursor, Codex or any other MCP client. Open source under Apache 2.0, free to run.","Requires Ubuntu 24.04 or 26.04 · 2 GB RAM · 1 CPU","Read the documentation","https:\u002F\u002Fpanelalpha.com\u002Fdocs"]