You made this public but didnt explain how to fix it!

is there any error on your deployment logs?

Hey there!

This error usually means the Railway proxy can't communicate with your application.

Here are the quickest ways to fix it:

1. Check your Port ConfigurationRailway automatically assigns a port. Make sure your code is listening on the host 0.0.0.0 and using the environment variable PORT rather than a hardcoded number (like 3000 or 8080).

2. Review the Deploy Logs Click on the deploy logs link shown in your screenshot. Look for any crash messages, missing environment variables, or syntax errors that might be stopping your application from fully starting up.

3. Verify Healthcheck Settings If you have a custom healthcheck path configured in your railway.json or service settings, ensure your application actually has that route open and returns a 200 OK status.

If there is an extra error you can share to make the assistance more direct you can share

no error in deploy log

No

that's mean the request didn't even reach the service, try solution given by dev-charles254, because it is probably the generated domain is not set to the right port or your app is not listening to host 0.0.0.0