The error you're encountering means that Railway's Edge Proxy cannot communicate with your application, causing your request to fail with a 502 (Bad Gateway) status code. In all likelihood, it's caused by a code or configuration issue.

Please see Application Failed to Respond in the Docs for more on what the error means, common causes for it, and possible solutions to help you resolve it.

My Railway Edge Proxy is right i followed the solution in application Failed to Respond

is not resolving the error i've configure it out?

Please elaborate on the issue you're experiencing. We are not able to support based on the information available here.

Hello,

You had some things misconfigured, incorrect build and start commands, missing pre-deploy command, incorrect variables, etc.

I've fixed all this for you on your behalf, and your site is now online and accessible.

You can see all the changes I've made in the Activity view, a little trial-and-error was needed to find what worked best for your application but I got there in the end.

Best,

Brody

Hello @brody , i have trouble on my next js deployment about this

That's a configuration issue on your end that we will not be able to help with, sorry.