2a8e227d-1f96-4975-8e42-86c2778d2a20

please check out our docs on this topic -

Okay, I checked, but before I haven't this issue

yes you do 🙂

I've pushed a change with app.listen(port, "0.0.0.0", function () {

I will see if it's working

please see this section specifically -

railway will inject the PORT? that means I need to remove the port variable from .env?

I had my working branch which is now merged in main on the development env and I didn't had this issue.

I'm using same env vars like what I used before for development, just the db url it's updated

you should not be commiting your .env file to GitHub at all

I don't commit my .env to github

I don't understand why was working on development and doesn't work on prod with same updates

you just mentioned your .env file?

I mean the railway environment, I've got production and development

My build working on development but not on production https://fsega-development.up.railway.app/

please follow the instructions here

@Brody are you a real user or robot?

i am a bot

Can a real person from support help me?

i'm sorry but at this time Hobby users are limited to automated support

Hello, can I get some help with this issue?

Brody is not a bot, lol

I will side with Brody though, this is a code issue you’ll have to fix after reading the docs. It’s not a problem we can help you with easily

@Adam why I can't see the error if it's a code issue, first of wall I see the railway screen and I can't debug my error if that exists, and on the other side why the code works in my development environment? I run the same branch for development and it's working

You’re asking me the same questions you asked Brody, so I’m going to tell you the same answer. Read these docs and you’ll find your answer

I read the docs

I run the same setup on both development and production environment both on railway

did you take any action to solve your problem after reading the docs?

that’s the next step

Saying that you have the same setup on dev and production isn’t helpful as there’s clearly a difference between the two.

I'm renaming now the PORT env variable as well

What do you mean? It's the same build

Okay, can be close, on production railway wants the env variable for port to be named PORT, but on the development the port variable works if it's named REMIX_PORT🤯

!s