2 months ago
I'm experiencing what appears to be a Railway platform issue.
This issue began immediately after initiating the Live Resize from 500 MB to 5 GB.
error creating app:
directory
.../snapshot-target-unpack/web
does not exist
Project
beneficial-consideration
Environment
production
Service
blackswan-scanner
Issue #1 - Volume Resize
My persistent volume was nearly full (500 MB).
I initiated a Live Resize from 500 MB to 5 GB.
The storage now reports 5 GB, but the service has remained in:
"Resizing volume..."
for more than 2 hours.
The service never comes back online.
Issue #2 - Deployments
While the volume is stuck resizing, every deployment fails before the application build begins.
The build error is:
error creating app:
directory
.../snapshot-target-unpack/web
does not exist
Repository Information
GitHub repository:
rayvasquez1977/BlackSwanScanner
Branch:
main
Root Directory:
/
Repository root contains:
app/
components/
lib/
public/
services/
package.json
next.config.ts
There is NO "web" directory.
I also verified:
- Config-as-code is not configured.
- Root Directory is "/".
- No railway.json
- No railway.toml
- No nixpacks.toml
- No Dockerfile
- No railpack.json
Questions
- Can the stuck volume resize be completed or cleared?
- Is the deployment using stale build metadata?
- Why is Railway trying to unpack a "web" directory that doesn't exist?
- Is the deployment failure related to the unfinished volume resize?
I would appreciate guidance before taking any destructive actions because this volume contains production data.
5 Replies
2 months ago
Your volume resize has completed and the volume is in a ready state at 5 GB with your data intact (~496 MB used). Your deployments are failing because a recent scaling change attempted to deploy this service to multiple regions, which is not supported for services with attached volumes. In your service settings, ensure only a single region is selected, then redeploy.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Thanks for the quick response. I checked the Scale settings, and only a single region (US West) is selected with one replica. I've attached a screenshot. Could you please check whether my service is still flagged internally for a multi-region deployment or whether there's stale deployment metadata? What should I do next to clear that state?
Attachments
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Thanks. The volume resize has now completed and the UI reflects the 5 GB volume correctly. However, my service is already configured for a single region (US West) with one replica. I've attached screenshots of the Scale settings and the attached volume. Since the deployment still failed with snapshot-target-unpack/web does not exist, could you check whether the service has stale deployment metadata or an internal multi-region flag? What is the recommended next step before I redeploy?
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
I verified the repository and service configuration:
Repository root contains app/, services/, package.json, etc.
There is no web directory.
Source settings show Root Directory = /.
Volume resize completed successfully.
Service is single-region (US West).
However, the build still fails with:
error creating app: directory ... snapshot-target-unpack/web does not exist
Could you please check why the builder is still attempting to use a web directory that does not exist?
2 months ago
I redeployed and received the same failure immediately.
New deployment ID:
05a29de3
The deployment Details page shows the GitHub source as:
rayvasquez1977/BlackSwanScanner
main
/web
However, the current service Source settings show Root Directory = "/",
and the repository has no web directory.
The deployment configuration JSON does not contain a root-directory field.
It does contain:
"multiRegionConfig": {
"sfo": {
"numReplicas": 1}
}
Please check whether the service has stale GitHub source-path metadata for
"/web" and whether the stored "sfo" region configuration needs to be cleared
or migrated.
Attachments
Status changed to Solved rayvasquez1977 • 2 months ago