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…
ReadMeFeed / Community knowledge
#port-binding
Real questions. Useful conversations. Find the people who know your stack.
scalingoShould I bind my Heroku app to process.env.PORT or a fixed port for local development?
When developing a Heroku‑deployed application, I want the server to start successfully both on my local machine and when pushed to Heroku’s dynos. The platform assigns a dynamic TCP port through the $PORT environment variable, while local runs often lack this variable, leading developers to either hardcode a port (e.g., 3000) or add a fallback. What is the r
herokuKtor server port precedence between application.conf and PORT env var
Diagnosing a Ktor deployment that fails health checks often requires knowing which port the embedded server actually bound at startup. Configuration is loaded from application.conf HOCON, environment variables, and command-line arguments, with programmatic configure blocks also available via embeddedServer factories. The documented merging of these sources i
ktor