Same issue as **Project:** enigin-portal (d6930c1b-140c-41f7-b0b9-b14ad308ae75) **URL:** **Problem:** * 10+ successful deployments * Server running correctly (timestamp 2025-10-06T23:21:38) * Railway edge permanently serving stale index.html: * `last-modified: Fri, 03 Oct 2025 05:24:59 GMT` * `content-length: 2160` (should be 8551) * `etag: W/"870-199a887d7f8"` (never changes) **Tried:** * Multiple deployments * Cache-Control: no-store headers added * Different browsers/incognito * Renaming files **Request:** Manual CDN cache purge for this project

Railway Edge Cache Serving Stale index.html from October 3rd

cce110

HOBBYOP

10 months ago

Same issue as https://station.railway.com/questions/urgent-deployments-successful-but-railw-8358a6a5

Project: enigin-portal (d6930c1b-140c-41f7-b0b9-b14ad308ae75) URL:https://enigin-portal-production.up.railway.app

Problem:

10+ successful deployments
Server running correctly (timestamp 2025-10-06T23:21:38)
Railway edge permanently serving stale index.html:
- last-modified: Fri, 03 Oct 2025 05:24:59 GMT
- content-length: 2160 (should be 8551)
- etag: W/"870-199a887d7f8" (never changes)

Tried:

Multiple deployments
Cache-Control: no-store headers added
Different browsers/incognito
Renaming files

Request: Manual CDN cache purge for this project

$10 Bounty

5 Replies

Railway

BOT

10 months 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!

Railway

Hey there! We've found the following might help you get unblocked faster: - [📚 Public Networking](https://docs.railway.com/guides/public-networking) - [🧵 URGENT: Deployments successful but Railway CDN serving cached frontend files](https://station.railway.com/questions/urgent-deployments-successful-but-railw-8358a6a5) - [📚 Production Readiness Checklist](https://docs.railway.com/reference/production-readiness-checklist) If you find the answer from one of these, please let us know by solving the thread!

cce110

HOBBYOP

10 months ago

thanks i can see someone else had this issue which was resolved - can we have access to the solution?

brody

EMPLOYEE

10 months ago

Hello,

We do not do any caching of network calls or static assets whatsoever; this is instead an issue with your application, project, or configuration.

I will open this thread up to the community so that they can help you debug your issue.

Status changed to Awaiting User Response Railway • 11 months ago

crisog

PRO

10 months ago

Hey there!

A couple questions to see if I can help:

1. Are you building with a Dockerfile?

2. What tooling are you using? node/php/python?

3. What's your build directory?

cce110

HOBBYOP

10 months ago

@brody Thanks for clarifying Railway doesn't cache static assets. I believe the issue is my project configuration.

My railway.json has "rootDirectory": "backend" which may be excluding my frontend/ folder from deployment. My Express server tries to serve static files from ../../frontend relative to backend/src/, but those files might not exist in the Railway container.

Questions:

Does "rootDirectory": "backend" deploy ONLY the backend folder, excluding frontend/ at the project root?
What's the correct configuration to deploy both folders?
Can you confirm what actually exists at /app in my deployed container?

Project: enigin-portal (d6930c1b-140c-41f7-b0b9-b14ad308ae75)

I suspect my frontend files simply aren't being deployed due to the rootDirectory setting.

Welcome!