Hey there! We've found the following might help you get unblocked faster:

• 📚 Application Failed to Respond

• 🧵 CommandError: "0.0.0.0:$PORT" is not a valid port number or address:port pair.

• 🧵 Error: '$PORT' is not a valid port number.

• 🧵 Docker command

If you find the answer from one of these, please let us know by solving the thread!

can you please try port 8080?

It deployed after a minute but still won't load when opening the test site.

Stopping Container

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/3e6477bc-dfd3-4027-b81c-2314cf828f1e/vol_lr4hfkrzeaoyhqv7

Starting Container

Stopping Container

> sillytavern@1.13.3 start

> node server.js

Node version: v22.19.0. Running in production environment. Server directory: /home/node/app

Using config path: ./config.yaml

Warning: config.yaml not found at ./config.yaml. Creating a new one with default values.

Using data root: ./data

Preferring IPv4 for DNS resolution

SillyTavern 1.13.3

Compiling frontend libraries...

webpack 5.98.0 compiled successfully in 822 ms

Launching in a browser: default...

]2;SillyTavern WebServer\SillyTavern is listening on IPv4: 127.0.0.1:8000

=================================================

Go to: http://127.0.0.1:8000/ to open SillyTavern

=================================================

]2;node\

This is still with the port 8000, if you want to keep this port you probably need to update the port in railway

maybe I'm missing something, but I thought I did set everything to 8080? Here are screenshots

the logs says 8000

```
]2;SillyTavern WebServer\SillyTavern is listening on IPv4: 127.0.0.1:8000

=================================================

Go to: http://127.0.0.1:8000/ to open SillyTavern
```

When I try to open that URL this happens.

change the domain to point to 8000, not 8080

I did, same thing. Won't connect.

redeploy and send the deploy logs

Stopping Container

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/02d880a4-09f0-4671-b737-699b75094254/vol_lr4hfkrzeaoyhqv7

Starting Container

Stopping Container

> sillytavern@1.13.3 start

> node server.js

Node version: v22.19.0. Running in production environment. Server directory: /home/node/app

Using config path: ./config.yaml

Warning: config.yaml not found at ./config.yaml. Creating a new one with default values.

Using data root: ./data

Preferring IPv4 for DNS resolution

SillyTavern 1.13.3

Compiling frontend libraries...

webpack 5.98.0 compiled successfully in 779 ms

Launching in a browser: default...

]2;SillyTavern WebServer\SillyTavern is listening on IPv4: 127.0.0.1:8000

=================================================

Go to: http://127.0.0.1:8000/ to open SillyTavern

=================================================

]2;node\

is it still 8080 here? send a screenshot

^

are you building with nixpacks or railpack?

try pointing the domain to 8080, maybe the deploy logs are wrong somehow

I'm not sure how to check

go into here and select railpack then redeploy

this is all I see

ah you have a dockerfile, mind sharing its contents?

https://docs.docker.com/reference/dockerfile/ is all I could find

… the dockerfile in your project, the GitHub repository

https://github.com/Arvinxx1/ctest-sillytavern

Change this to railpack

change the port here to be 8080:
https://github.com/Arvinxx1/ctest-sillytavern/blob/release/Dockerfile#L46

or change the port in the env & in railway to be 8000.

The point is, the port use to serve the app should match the one in railway, usually railway is on the 8080, so you can keep this 8080 & update all your references to be 8080, or you can just change the railway port to be 8000...up to you, probably is quicker to set 8000 in the env + in railway

sorry is this just as simple as pressing a button or does it include more steps. I can't find a simple answer

try to get all the port references with the same value, if you don't want to update the dockerfile try to set 8000 in both the PORT env & the railway port...actually, you can even just delete the PORT env and just use the railway port

@arvinxx1 it seems like you are really close to having this working, try what @fra is suggesting here. Update the EXPOSE number in your repo's Dockerfile then save the change in your repo. Then redeploy. It sounds like Railway is expecting your app to be reachable at port 8080, but the Dockerfile is configured to expose it at port 8000, so Railway can't connect to it. You could also tell Railway to find the app running at port 8000 if you'd prefer.

I went into my dockerfile and changed the expose number. It was set to 8000. I changed it to 8080. And did the same on railway (variable: PORT = 8000 and when generating a domain). It deployed , then crashed. Her are the logs:

That's an application issue, so you might need to do some research, as the log says you probably need to add 0.0.0.0 in the ip whitelist

arvinxx1, go to: https://railway.com/deploy/YuyzZp and click "Deploy now".

oh wow, this one works. So I just copy this?

Yes, this is a template from Railway. Warning(!): highly recommend you to change the password of default user, as stated in the description.

can you please mark my answer about the port as the solution? as that is the solution of the initial problem...