Loading...

My deployed app URL is still not active, disappointing service for a paid hobby plan.

snootypebbles

HOBBYOP

20 days ago

I’ve been trying to get my project running for over a day and it’s extremely frustrating.

The deployment shows as successful, but the public URL still doesn’t work:

Plan: Hobby

I’ve checked everything on my end — ports, environment variables, logs — it’s all fine.

At this point, it really feels like something is wrong on Railway’s side.

You reached the start of the range

Oct 27, 2025, 4:19 PM

Starting Container

npm warn config production Use --omit=dev instead.

> server@1.0.0 start

> node server.js

Server + WebSocket running at http://localhost:8080

Environment: production

Please fix this or let me know what’s blocking activation. I’ve been stuck with no response and it’s honestly disappointing for a paid plan

$10 Bounty

2 Replies

Railway

BOT

20 days 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!

20 days ago

The issue you have isn't related to Railway, it's a routing issue within your own app. I know this because:

That is not a Railway error screen
I can see from the headers that an Express server is returning the error
I can see your healthcheck endpoint is being routed correctly: https://fairsprint-server-production.up.railway.app/health

Have you tested your app locally? Also is your GitHub repo public? I'd need to be able to see your code to be able to help you myself