Waw

Try setting the PORT variable to 8080 explicitly, and make your app listen on it instead of hardcoding it.

If that doesn't work, try changing the port to 3000 both in your app and in the target port.

Ohhh

Update: I confirmed the app is working perfectly from inside the container. Using Railway's Console feature, I ran:

wget -qO- http://localhost:8080/api/branches

This returned valid JSON data successfully:

[{"id":1,"name":"BOW Kelapa Gading",...},{"id":2,"name":"BOW Sunter",...}]

So the app IS listening on 0.0.0.0:8080 and responding correctly internally. The issue must be with Railway's edge proxy/routing not reaching the container, since the public domain still returns "Application failed to respond" (502).

Could someone from the team check the routing for this deployment specifically?

Since Railway reports the deployment as successful and Tomcat starts correctly, the most likely causes of the 502 are that the application is not actually binding to Railway's injected $PORT, a startup dependency (database, Redis, external API, etc.) is hanging or failing after Tomcat starts, Spring Security or a filter is blocking requests, or there is no valid endpoint at /. Set server.port=${PORT} (without the :8080 fallback) and server.address=0.0.0.0, add a simple test controller such as @GetMapping("/") returning "OK", temporarily disable security and database initialization, redeploy, and check whether the startup log shows the exact port Railway injected rather than a fixed 8080. If the root endpoint still returns a 502 despite a successful deployment and no runtime errors in the logs, the issue is likely in the container configuration (Dockerfile, exposed port, or process startup command) rather than the Spring Boot application itself.

Try redeploying from the dashboard.