Duplicated railway repo not working
tnep4
HOBBYOP

10 months ago

I duplicated a github repo deployed on railway (so I duplicated the railway service) in order to create a "staging" environement.

When going to the deployment url, I get the following message:
Application failed to respond

This error appears to be caused by the application.

If this is your project, check out your deploy logs to see what went wrong. Refer to our docs on Fixing Common Errors for help, or reach out over our Help Station.

If you are a visitor, please contact the application owner or try again later.

Request ID:
W0IbJnJbSOy1UFbpN-1keg_2823689937

-> I have no deploy or build logs that indicate the error (and the repo it's duplicated from works perfectly).

Could you please help me?

Solved

5 Replies

unicodeveloper
PRO

10 months ago

Did you set the PORT it should listen on? From what I see in the logs, it says 1:23:56 PM [express] serving on port 5000

So did you set the PORT to listen on 5000 for the staging environment?

I can see your production service listens on 5000. So the staging should be set to listen on PORT 5000 as well.


Status changed to Awaiting User Response Railway 10 months ago


tnep4
HOBBYOP

10 months ago

What I do not understand is that I didn't change anything at all - just duplicated the Railway service.
So everything should be set the exact the same way - I didn't change any of the code or variables!


Status changed to Awaiting Railway Response Railway 10 months ago


unicodeveloper
PRO

10 months ago

I understand. But from what I see here, you need to set the PORT just as you have it set in production.


Status changed to Awaiting User Response Railway 10 months ago


tnep4
HOBBYOP

10 months ago

Okay - so I couldn't do it when renaming the Public Networking field.
But I could effectively set it when adding a custom domain!

Thanks for your help.
I attached screenshots so you can see what I mean.


Status changed to Awaiting Railway Response Railway 10 months ago


unicodeveloper
PRO

10 months ago

Awesome


Status changed to Awaiting User Response Railway 10 months ago


Status changed to Solved unicodeveloper 10 months ago


Loading...