Description:

I'm trying to deploy my Spring Boot 3.3.5 application on Railway, but after every successful deployment, when I access the public URL, I get a 502 Bad Gateway error. Locally, everything works perfectly (Swagger loads, endpoints respond normally), but on Railway, it never passes the health check.

Here's what I've tried so far:

• Set my profile to prd and added SPRING_PROFILES_ACTIVE=prd in Railway environment variables.
• Configured application-prd.yml like this:

yaml

CopiarEditar

server: port: ${PORT:8080} spring: datasource: url: jdbc:postgresql://${PGHOST}:${PGPORT}/${PGDATABASE}?sslmode=require username: ${PGUSER} password: ${PGPASSWORD} jpa: open-in-view: false hibernate: ddl-auto: validate springdoc: swagger-ui: path: /swagger-ui.html api-docs: path: /v3/api-docs

• Added a simple health controller:

java

CopiarEditar

@RestController public class HealthController { @GetMapping("/") public String home() { return "Application online!"; } }

• Confirmed that PostgreSQL is reachable, tables already exist, and Hibernate connects successfully (HikariPool-1 - Start completed appears in logs).
• Tested locally with PORT=9090 and SPRING_PROFILES_ACTIVE=prd → works fine on that port.

However, on Railway:

• The logs show the app starting fine on port 8080.
• GET / returns status 499 or 502.
• Railway dashboard keeps showing Port 8080, as if the ${PORT} variable is not being picked up by Spring Boot.

I’ve already forced redeploys (clean builds, rebuild from scratch) and the same issue persists.

Railway error reference:Application failed to respond

Support code:Zg5wU9DHRS-qSmA0g4a9AQ

Question:

• Why is my Spring Boot app ignoring the ${PORT} environment variable on Railway?
• How can I make Railway recognize my app and stop returning 502 even though deploy logs show no errors?