Hello Railway Support Team,

I'm experiencing persistent 502 errors with a deployment that I've stripped down to the absolute minimum to isolate the issue. I would appreciate your help in identifying what's causing this problem.

Details of the Issue:

1. All requests to my application return 502 Bad Gateway

2. This occurs even with a minimal test deployment

3. The issue persists across multiple deployment attempts and configuration changes

Steps I've Taken to Isolate the Problem:

1. Created a minimal Python HTTP server with just a /liveness endpoint

2. Removed all dependencies except Python's built-in http.server

3. Explicitly configured port binding

4. Set up proper health checks

The server binds to 0.0.0.0 and uses the PORT environment variable

1. The configuration follows Railway's deployment guidelines
2. The Dockerfile and railway.toml are properly configured
3. The application works locally

Questions:

1. Are there any logs you can share that might show why the 502 errors are occurring?
2. Is there something specific about port configuration that I might be missing?
3. Are there any known issues with Python's built-in HTTP server on Railway?
4. Would you recommend any specific changes to my configuration? Thanks, Gonen