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

• 🧵 How do I limit access to my Postgres db's public url?

• 🧵 Unable to access live URL for Railway Deployment

• 🧵 Not able to access my server url

• 🧵 Missing nodejs app URL

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

What kind of app is this? Web, Rest APIs ?
which framework did you use? Node/Express.js, Python etc?

If there are no build/deploy errors, then most probably, a wrong port has been mapped to the public-networking URL. Make sure that the target port is the same as what you defined in your server file

Also, can you please check the HTTP logs?


Moreover, the best thing to solve this issue is to use "healthcheckup" to see whether the routing of the server is okay or not, and if it fails, it give you the build error. You can check out my post on the same issue: https://station.railway.com/questions/node-js-service-failing-to-deploy-with-s-dc58e402#mk2w

I hope that helps, & if not, please provide more context for the issue

And also, if you are using your defined port number, then remember to expose it in the Dockerfile (if you are using one)

# Expose the port the app runs on
EXPOSE 7890

Change it with your port number

Any update, Bryant?

Is there any other roadblock, mrbryant2761

I've followed all of the advice here and am still having intermittent issues with deployment. Have posted a new request with much more information provided.

Thank you for providing these ideas. Another observation is that twice now I have revisited the issue in the morning after deploying the previous evening and it is suddenly working. However, deploying an update brought it down again and the update was actually no code change - just checking the deployment process.

Hi mrbryant2761, it seems that the issue with your deployment is that you have not configured the public networking for it. Select the desired service, go to Settings -> Public Networking -> Public. If this does not contain an already-existing link, then click on GENERATE DOMAIN so that you can get a public-facing URL that you can use to visit your server.

The link has already been generated. I couldn't attempt to view it from a browser if there was no link. But thanks for your thoughts.

Oh, I thought you were trying to use the internal URL itself.

Btw, what sort of a server/app is this, and can you please provide the initial configuration of the server/app as screenshots?

And if it is a server, then does it serve a default route "/"?

You can find that information in this thread: https://station.railway.com/questions/railway-load-balancer-dns-routing-issue-9409710a. I should have kept this thread running rather than to start a new one - just didn't think of it.

Taht was the issue for sure! Thanks a bunch for the assist. This has been showing progress for a few days now.