Diagnosing 502 Bad Gateway and Crash Loops in Scalingo Deployments
Resolve 502 Bad Gateway errors and crash loops in Scalingo by correctly configuring PORT binding and Procfile start commands.
Loading…
scalingoReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Resolve 502 Bad Gateway errors and crash loops in Scalingo by correctly configuring PORT binding and Procfile start commands.
Goal Capture container logs in Portainer when a deployment fails immediately and the container is configured with --rm or a restart policy that removes it on failure. Constraints Portainer retrieves logs through the container engine's logging driver. If a non-standard driver (e.g., fluentd , gelf ) is used, the UI may show no output. When auto-remove is enab