Tag
This error means your Laravel app could not reach the database at all. It is almost always one of two causes: a wrong DB_HOST, or your app starting before MySQL is actually ready inside Docker. Here is how to tell which one you have, and the real fix for each.
Caddy showing 502 Bad Gateway for a containerized app? Diagnose it in the right order — Docker networking, bind addresses, port mismatches, and startup races — instead of guessing.
Docker doesn't restart a container just because it's marked unhealthy — that's the single most common misconception in self-hosted Docker setups. Here's how healthchecks and restart policies actually relate, and the exact setup that makes a self-hosted app genuinely recover on its own.
How to run several apps on a single cheap VPS using Docker and Caddy — shared network setup, working Caddyfile examples, free auto-renewing HTTPS per subdomain, and when label-based routing is worth the switch.
