Help
arvinxx1
HOBBYOP

5 months ago

I'm trying to figure out how to set up a custom chatbot on my website.

I can't get the test website on Railway to open, it deploys but gives me an error upon opening.

I'm using SillyTavern from github, which is a chatbot software, I'm trying to get it up and running on Railway. I got an api key from openrouter.

I set my variables:
OPENROUTER_API_KEY = (the api key)

PORT = 8000

HOST = 0.0.0.0

NODE_ENV = production

Setting a volume (5gb) seems to have removed all the errors. But despite no errors now, the site won't open.

"Error seems to be caused by the application" is what I get when I try to open the website.

ChatGPT says this:

"Look at the logs:

SillyTavern WebServer\SillyTavern is listening on IPv4: 127.0.0.1:8000

That means the app is live, but only inside the container right now (localhost = 127.0.0.1). Railway can’t serve it publicly unless the server is told to bind to 0.0.0.0 instead of 127.0.0.1."

Admittedly, I set this whole thing up using ChatGPT because I'm a beginner.

ChatGPT has given me some start commands to try to force it to bind to 0.0.0.0 but none of that stuff seems to work. Right now I'm just using "npm run start"

$10 Bounty

5 Replies

Railway
BOT

5 months ago

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

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

case
PRO

5 months ago

@arvinxx1 can you share your Dockerfile? That is usually where port mapping happens

arvinxx1
HOBBYOP

5 months ago

Thanks for all of that info.

I started by adding the variables SILLYTAVERN_LISTEN=true: and SILLYTAVERN_WHITELISTMODE=false:

It deployed (still no working link though), but then crashed a few seconds later.

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/e2ca6de5-e62d-4c54-9e3e-b2dc82f17bb9/vol_lr4hfkrzeaoyhqv7

> 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

Using data root: ./data

Preferring IPv4 for DNS resolution

Your current SillyTavern configuration is insecure (listening to non-localhost). Enable whitelisting, basic authentication or user accounts.

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/e2ca6de5-e62d-4c54-9e3e-b2dc82f17bb9/vol_lr4hfkrzeaoyhqv7

> 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

Using data root: ./data

Preferring IPv4 for DNS resolution

Your current SillyTavern configuration is insecure (listening to non-localhost). Enable whitelisting, basic authentication or user accounts.

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/e2ca6de5-e62d-4c54-9e3e-b2dc82f17bb9/vol_lr4hfkrzeaoyhqv7

> sillytavern@1.13.3 start

> node server.js

case
PRO

5 months ago

@arvinxx1 can you use Markdown formatting when you reply in here, to make your logs and code snippets easier to read?

I think we'll need to see your Dockerfile, and the logs from when the app appears to be crashing, in order to debug this further.

fra
HOBBYTop 5% Contributor

5 months ago

I think this post is a duplication of this other post:
https://station.railway.com/questions/no-errors-but-website-won-t-load-57f843f7#7x30

please check all your port are set correctly as I wrote in the other thread, also I think opening the same thread multiple time it creates only confusion

Loading...