8 months ago
28b65aa8-8552-4971-b628-ddc18ac2cb6d
I deployed a simple nextjs app which just calls my database and displays some data.
I deployed it last night and the public url provided by railway was working great (I just used port 8080 as was recommended). It worked all the way up until this morning.
Then, the url started timing out.
I re-deployed the entire project in a new railway project. I generated a new url and this solved the issue… for about 3 minutes. I could go to the url and load everything. But after a few minutes, it stopped working again.
I am on the Hobby plan and don't believe I am close to any usage limits. Why would this happen?
21 Replies
8 months ago
the url works for me?
8 months ago
Check if you have “serverless” enabled for any of the services in the project. If so, disable them. It’s usually the cause when I face the same issue.
Serverless is not enabled.
The url does not work for me, including in incognito mode.
8 months ago
url still works for me, can you define not working?
When I go to it, it loads about:blank, white screen, and eventually times out. Logs don't show much either. My most recent request was at 2:40, logs show from 2:25


8 months ago
Can confirm that I also can access it totally fine. Cleared all your cache? Tried a different browser?
8 months ago
Is it possible that a page past this is having an issue?

8 months ago
Oh. Cool.
How can I make it so the coworking space does not block the connection? It wasn't doing this yesterday.
8 months ago
Use proxy maybe.
8 months ago
That would be a question for your ISP
8 months ago
You can try that
8 months ago
But that would be a question for your ISP
8 months ago
Your ISP must've flagged the Ip or something, depends on your ISP as @loudbook said. But a quick solution is to spin up a small proxy and route your traffic through that, so your static IP doesn't get blocked or anything.
I think public wifi generally does block some IP addresses and websites, this happens rarely. I usually use a proxy or vpn or you can internally use a proxy to re-route the traffic and solve the issue. If you are on mac, maybe try turning on rotating ip address for your machine and see if that fixes the issue.
8 months ago
Happy to help! :)
Status changed to Solved brody • 8 months ago