Compose app started but did not respond on its published ports
Warning recorded 55 times in PanelAlpha Engine deploys on Docker Compose, Dockerfile, Java and more. The deploy log below is the recorded failure output.
TypeWarningAn issue PanelAlpha Engine catches around a deploy that does not break it. It tells you, before or after, that you may need to do something.
Seen55 times · 11 variants
WhereDocker Compose, Dockerfile, Java +5 moreDocker Compose, Dockerfile, Java, Laravel, Nextjs, Php, Python, Rust
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The containers started, but health checks received no response on ports 3366, 4200, or 4202. The application may be listening on a different port or only on localhost inside the container. Compose also reported several unset environment variables, which may prevent the services from starting correctly. If this is a worker or queue-only deployment, it may not expose an HTTP port by design.
What the log looks like
Deploy log
Detected application port: 3366Starting application (docker compose up -d)The "ONPATIENT_CLIENT_ID" variable is not set. Defaulting to a blank string.The "EPIC_CLIENT_ID" variable is not set. Defaulting to a blank string.The "PUBLIC_URL" variable is not set. Defaulting to a blank string.The application started but did not answer on any port it publishes.