Your "Hostel-Management-Full-stack" service shows a successful build but is producing no runtime logs at all, which means the application process is likely crashing immediately on startup or not starting a web server. For the 502 error to resolve, your app needs to bind an HTTP server to 0.0.0.0 on the port defined by the PORT environment variable that we inject automatically. You can check your deploy logs in the service dashboard to see if there's a startup error, and refer to our troubleshooting guide for framework-specific examples.