This question appears to be about your application code rather than the Railway platform, which is outside the scope of what we can help with.

Railway team, if you can't provide any support here, I will have to cancel my subscription and move to Render.

Try setting a PORT variable in your service to an arbitrary number (eg, 9000), and map your URL to that port.

Make sure to redeploy after configuring your service.

Thanks for tip... just tried it, no luck though. Any other ideas?

Have you tried hardcoding the 3000 instead of using ${PORT:-3000}?

Hello vicramon, can you share your deploy logs?

Just tried that, no luck

Yeah, no obvious issues. Attached build and deploy logs.

okay so the build is clean and migrations ran fine, i think the issue is that your app is using thruster (i can see thruster 0.1.19 was installed), which is a proxy that wraps puma , it handles the port itself so your start command bin/rails s -p ${PORT:-3000} is likely conflicting with how thruster expects to manage the port

try changing your start command to:

bundle exec thrust bin/rails server

and make sure your target port in railway matches the PORT variable, thruster will handle binding to it automatically

Hope this help you :)

Good catch, yes I am using thruster 0.1.19.

Ok, I tried that but still getting the same error. Let me know if you have any other suggestions.

can you share your deploy logs after trying that command?

the logs got cut off right after the db step?

i can't see if thruster/puma actually started or what error happened after, can you scroll down and share the rest of the deploy logs after those database lines?

?

Ok, I got it working, the fact that the logs stopped was the clue, something was off with the Dockerfile. Some of the logs showed "Stopping Container" but that wasn't included with the export or visible in the summary, I had to go into the log screen to see it.

I removed the start command, so then it uses CMD from dockerfile, which was already correct by default from rails generate:

CMD ["./bin/thrust", "./bin/rails", "server"]

I believe the issue was the default bin/docker-entrypont file.

Before:

#!/bin/bash -e

# If running the rails server then create or migrate existing database
if [ "${@: -2:1}" == "./bin/rails" ] && [ "${@: -1:1}" == "server" ]; then
  ./bin/rails db:prepare
fi

exec "${@}"

After:

#!/bin/bash
set -e

# This check looks for "rails server" anywhere in the command arguments
if [[ "$*" == *"rails server"* ]]; then
  echo "docker-entrypoint: Running database setup..."

  # Try to create the database (fails silently if it exists)
  ./bin/rails db:create || echo "Database already exists, skipping create."

  # Run migrations
  ./bin/rails db:migrate

  echo "Database setup complete."
fi

exec "${@}"

Now it's working. No PORT variable needed, and I set the connection port to 80 (3000 also works but I assume 80 is the better one to use here).

@domehane (cc @railwaysupport) you should get the bounty since your help led to the fix, but my comment should be marked as the solution. Thanks again :)