3 months ago
Hi,
Our website deployment is showing 404 Not Found Railway errors every now and then, to different people, in different browsers. (On different deployments too!)
It first happened to one colleague on Google Chrome, I checked our Railway deployment and it was live at the time and everyone else in the team could access the URL.
Then it happened to me, again on Google Chrome, I checked again on Railway and it was Online, receiving requests, and others could access it on Google Chrome.
Then our CTO tried to access the deployment (which we verified was Online), first he tried on Google Chrome and it worked but then we immediately tried Brave and got the 404 Not Found error from Railway for some reason.
The only explanation I could find was that it must be an issue with Railway's proxy or something.
Could you please help us?
Attachments
7 Replies
3 months ago
We have already tried clearing cache and local storage, and redeploying on Railway...
3 months ago
Could you share the domain where you're seeing this 404 error? Specifically, whether it's a Railway-generated domain (*.up.railway.app) or a custom domain, and if custom, whether you're using Cloudflare with proxy enabled.
Also, could you link us to the service on Railway so we can take a look at the routing configuration?
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Yeah, it has a custom domain: listoai.co and these is the Railway domain: maglev.proxy.rlwy.net:54565
It does have Cloudflare proxy enabled.
Here is what I see in my Network tab:
Attachments
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Awaiting User Response Railway • 3 months ago
brody
You don't have [www.listoai.co](http://www.listoai.co) registered on the Railway service.
2 months ago
Hi brody, what do you mean I don't have it registered on the Railway service? It is. And, this seems to be a Railway issue. Right now if I go to listoai.co on Safari my landing page opens fine, if I try listoai.co on Chrome I get the Railway error still. Multiple colleagues have mentioned this now and again.
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
When I typed that 7 days ago, you did not have the www subdomain added to the service, I see it is there now though.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
I added it but, is that what causes the error? In modern browsers domains I think domains do not need it? Also, the deployment and URL / DNS worked well without it for certain people in certain browsers, so I doubt that was it. e.g. It worked on Chrome for 2/4 of the employees at the company and for the other 2 it worked well on every other browser, and this would change randomly. Suddenly someone who was not able to open it up on Chrome, was able to. Without the www subdomain anyway.
Status changed to Awaiting Railway Response Railway • 2 months ago
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 1 month ago