It says http://deb.debian.org/debian is unreachable but I'm able to download packages from it

Can you try again?

Seems to be a mise issue https://github.com/jdx/mise/discussions/7499

Workaround would be using your own Dockerfile

Debugging it further I was able to download libatomic1 just fine in a Node 25 project 🤔

install apt packages: libatomic1

Get:1 http://deb.debian.org/debian bookworm InRelease [151 kB]

Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]

Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]

Get:4 http://deb.debian.org/debian bookworm/main amd64 Packages [8791 kB]

Get:5 http://deb.debian.org/debian bookworm-updates/main amd64 Packages [6924 B]

Get:6 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages [290 kB]

Fetched 9343 kB in 1s (8668 kB/s)
Reading package lists...


Reading package lists...


Building dependency tree...

Reading state information...


The following NEW packages will be installed:

  libatomic1

0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 9376 B of archives.
After this operation, 46.1 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bookworm/main amd64 libatomic1 amd64 12.2.0-14+deb12u1 [9376 B]

debconf: delaying package configuration, since apt-utils is not installed

Fetched 9376 B in 0s (451 kB/s)

Selecting previously unselected package libatomic1:amd64.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 6622 files and directories currently installed.)

Preparing to unpack .../libatomic1_12.2.0-14+deb12u1_amd64.deb ...

Unpacking libatomic1:amd64 (12.2.0-14+deb12u1) ...

Setting up libatomic1:amd64 (12.2.0-14+deb12u1) ...

Processing triggers for libc-bin (2.36-9+deb12u13) ...

It worked rn

Will let u know if something fucks up again

Railway is too sensetive ngl you just gotta make it like hostinger vps what the fuck is this shit ong

Maybe it was just some temporary instability from the debian registry

Maybe

If you think that "Railway is too sensitive" I suggest you use your own Dockerfile, that way you have full control of your builds

Nah i will use Hostinger

Railway aint even BP infact with this sensitivity.

me and my dev waste more time on fixing code errors than coding

At this point just update it to so its business standard like hostinger and hetzner.

Unfortunately, we cannot control the availability of 3rd party services, and believe it or not, despite how critical the Debian archive is, it's quite flaky, we would like to have our own cache layer for it at some point, but until then, we are at the mercy of their transient issues.

I will keep this thread open for some time. If you have any further questions/issues, I will be happy to help you! <:salute:1137099685417451530>

@Medim still fails after 20-22min building

2026-01-08T15:04:41.910304451Z [inf] scheduling build on Metal builder "builder-libyha"
2026-01-08T15:04:43.316420583Z [inf] [snapshot] received sha256:c004afdc50a8a6b30f0a9b0d71847191a9cd766e9c7633d5c139c36bf88c681d md5:f58c6c2b14c16fe920848ec929553ffc
2026-01-08T15:04:43.316519271Z [inf] receiving snapshot
2026-01-08T15:04:43.331869251Z [inf] analyzing snapshot
2026-01-08T15:04:43.369288045Z [inf] uploading snapshot
2026-01-08T15:04:46.698969891Z [inf] scheduling build on Metal builder "builder-libyha"
2026-01-08T15:04:48.220111969Z [inf] fetched snapshot sha256:c004afdc50a8a6b30f0a9b0d71847191a9cd766e9c7633d5c139c36bf88c681d (1.9 MB bytes)
2026-01-08T15:04:48.220222915Z [inf] fetching snapshot
2026-01-08T15:04:48.596363895Z [inf] unpacking archive
2026-01-08T15:04:48.950955231Z [inf] using build driver railpack-v0.15.4
2026-01-08T15:04:49.373153705Z [inf]
2026-01-08T15:04:49.373178813Z [inf] ╭─────────────────╮
2026-01-08T15:04:49.373180165Z [inf] │ Railpack 0.15.4 │
2026-01-08T15:04:49.373180696Z [inf] ╰─────────────────╯
2026-01-08T15:04:49.373181196Z [inf]
2026-01-08T15:04:49.373184221Z [inf] ↳ Detected Node
2026-01-08T15:04:49.373186564Z [inf] ↳ Using npm package manager
2026-01-08T15:04:49.373188928Z [inf]
2026-01-08T15:04:49.373189659Z [inf] Packages
2026-01-08T15:04:49.373190240Z [inf] ──────────
2026-01-08T15:04:49.373192744Z [inf] node │ 18.20.8 │ package.json > engines > node (>=18.0.0)
2026-01-08T15:04:49.373193285Z [inf]
2026-01-08T15:04:49.373193815Z [inf] Steps
2026-01-08T15:04:49.373194266Z [inf] ──────────
2026-01-08T15:04:49.373194877Z [inf] ▸ install
2026-01-08T15:04:49.373195358Z [inf] $ npm ci
2026-01-08T15:04:49.373195838Z [inf]
2026-01-08T15:04:49.373196289Z [inf] ▸ build
2026-01-08T15:04:49.373196760Z [inf] $ npm run build
2026-01-08T15:04:49.373197280Z [inf]
2026-01-08T15:04:49.373197791Z [inf] Deploy
2026-01-08T15:04:49.373198192Z [inf] ──────────
2026-01-08T15:04:49.373198693Z [inf] $ npm run start
2026-01-08T15:04:49.373199183Z [inf]
2026-01-08T15:04:49.692821012Z [inf] resolve image config for docker-image://ghcr.io/railwayapp/railpack-frontend:v0.15.4
2026-01-08T15:24:52.636671355Z [err] Build Failed: build daemon returned an error < failed to run Build function: Canceled: context canceled >

this shit too annoying bro

Turn off the metal builder in the service settings.

@Medim 15 hours building…

@Brody

This shit is insane

Cancel it.

And i turned off metal build

cancelled

Its deploying another commit from the github repo no.

now*

Alright it successfully deployed

I thought its some error with my CDN provider lmao.

Its all because of the M.B.E

Bro i am afraid to migrate to wasabi buckets this railway fucks my deployments and fails

Tigris*

wasabi better

for large sized buckets like 5tb

How so?