My Express app is deployed with a single replica, single active deployment. A request to a path (e.g. /reset-passcode) returns 200 with the correct HTML when tested from inside the container (fetch('http://localhost:8080/...')), but the exact same path on the public domain returns 404 with Express's default "Cannot GET" message. This persists after: restarting the service, triggering a fresh redeploy, and fully regenerating the public domain (old one deleted, new one issued). Verified from multiple browsers/incognito sessions with cache-busting query params, so it's not client-side or edge caching. x-powered-by: Express is present on the 404 response, and server: railway-hikari / x-railway-edge headers are present. Service: acountability-app, project remarkable-abundance.